Behavioral interview questions ask you to describe what you actually did in a past situation — "Tell me about a time when…" — because how you handled something before is the best available evidence of how you'll handle it again. The strongest way to answer is the STAR method: the Situation, the Task you owned, the Action you took, and the Result, ideally with a number.
Below are the 30 behavioral questions that come up most often, grouped by what they're really testing, with full example answers for the ten you're most likely to get.
How to answer any behavioral question: the STAR method
| Step | What to say | How long |
|---|---|---|
| S — Situation | Where and when. Just enough context to follow the story. | 1–2 sentences |
| T — Task | What you were responsible for, and why it mattered. | 1 sentence |
| A — Action | The specific steps you took. Say "I", not "we". This is the heart of the answer. | 3–5 sentences |
| R — Result | What changed, with a number if you have one — and what you learned. | 1–2 sentences |
Three rules make the difference between an average and a great answer:
- Spend most of your time on the Action. Interviewers aren't scoring the story's drama; they're listening for your judgement.
- Say "I". "We launched the campaign" tells them what your team did. "I rewrote the targeting after the first week" tells them what you did.
- End with a result and a lesson. Numbers are best ("cut response time from 9 hours to 2"), but an honest lesson is better than a vague success.
Aim for 90 seconds to two minutes per answer. If they want more, they'll ask.
The 30 most common behavioral interview questions
Teamwork and conflict
- Tell me about a time you disagreed with a colleague. How did you handle it? (example below)
- Describe a time you had to work with someone difficult.
- Tell me about a time you helped a teammate who was struggling.
- Give an example of a time you had to rely on others to finish a project.
- Tell me about a time you received criticism from a colleague.
Problem-solving and judgement
- Tell me about a time you solved a difficult problem. (example below)
- Describe a decision you made without all the information you wanted.
- Tell me about a time you spotted a problem before anyone else did.
- Give an example of a time you used data to make a decision. (example below)
- Tell me about a time you had to choose between two good options.
Pressure, deadlines and priorities
- Tell me about a time you had too much to do. How did you prioritise? (example below)
- Describe a time you missed a deadline, or nearly did.
- Tell me about the most stressful situation you've faced at work.
- Give an example of a time you had to change plans at short notice.
Failure and learning
- Tell me about a time you failed. (example below)
- Describe a mistake you made and how you fixed it.
- Tell me about a time you had to learn something new quickly.
- What's a piece of feedback that changed how you work?
Leadership and initiative
- Tell me about a time you took the lead without being asked. (example below)
- Describe a time you persuaded someone to change their mind.
- Tell me about something you improved that wasn't your job.
- Give an example of a goal you set and achieved.
Customers and stakeholders
- Tell me about a time you dealt with an unhappy customer. (example below)
- Describe a time you had to say no to a stakeholder.
- Tell me about a time you went beyond what a customer expected.
Communication
- Tell me about a time you explained something complex to a non-expert. (example below)
- Describe a time you had to deliver bad news.
- Tell me about a time a misunderstanding caused a problem.
Motivation and values
- Tell me about a time you were proud of your work. (example below)
- Describe a time you had to do something you disagreed with. (example below)
10 example answers using STAR
These examples come from different kinds of jobs on purpose. Don't memorise them — borrow the structure and swap in your own story.
1. "Tell me about a time you disagreed with a colleague."
What they're testing: whether you can disagree without damaging the relationship, and whether you care more about the outcome than about being right.
S: In my last role as a marketing coordinator, a senior designer and I disagreed about a landing page — she wanted a long, image-heavy page; I thought it would load too slowly on mobile. T: I owned the campaign's sign-up numbers, so I needed us to agree before launch, which was ten days away. A: Instead of arguing in the meeting, I asked if we could test both. I set up a simple A/B test, agreed the success metric with her in advance — sign-ups per 100 visitors — and suggested we let the data decide after a week. R: Her version actually won on desktop and mine won on mobile, so we shipped a responsive mix of both, and sign-ups were 18% above target. I learned to turn opinions into tests early; it takes the ego out of it.
2. "Tell me about a time you solved a difficult problem."
What they're testing: how you break a messy problem down.
S: As a support specialist, I noticed tickets about failed password resets had doubled in a month. T: Nobody owned the issue — engineering thought it was user error, and support kept closing tickets one at a time. A: I tagged every related ticket for two weeks, then grouped them by email provider. 70% came from one provider that was delaying our reset emails past their 15-minute expiry. I wrote this up with ticket examples and took it to the engineering lead. R: They extended the expiry to an hour, and reset tickets fell by about 60% the following month. Now I always look for a pattern before treating tickets as one-offs.
3. "Give an example of a time you used data to make a decision."
What they're testing: whether you use evidence, not just instinct — and whether you can tell a story with numbers.
S: At a small online shop, I was asked to decide which of three product lines to discount for a holiday sale. T: Our budget allowed a discount on only one line. A: I pulled twelve months of orders into a spreadsheet and looked at repeat-purchase rates, not just revenue. The line with the lowest revenue had the highest share of customers who came back within 60 days. R: We discounted that line; the sale brought in 340 new customers, and 29% bought again within two months — nearly double our usual rate. It taught me that the biggest number isn't always the right one to optimise.
4. "Tell me about a time you had too much to do. How did you prioritise?"
What they're testing: judgement under pressure, and whether you communicate before things go wrong.
S: In my first month as a project coordinator, two project managers each asked me for a report due the same afternoon, on top of a client meeting I was organising. T: I couldn't do all three well by 4 pm. A: I listed what each task was for and what would happen if it was a day late. The client meeting couldn't move; one report fed a board deck, the other a weekly internal update. I messaged both managers within the hour with a proposed order and asked the internal-update owner if Thursday morning worked. R: She said yes, both urgent items went out on time, and the second report went out the next morning. Since then I raise conflicts the moment I see them instead of hoping I'll fit it all in.
5. "Tell me about a time you failed."
What they're testing: honesty and self-awareness. Pick a real failure — not a disguised boast — and spend most of the answer on what changed afterwards.
S: In my first sales role, I lost a deal I'd been working on for three months. T: It was my largest opportunity that quarter. A: When I asked the customer for feedback, they said we never spoke to the person who controlled the budget. I'd been talking to an enthusiastic user and assumed they could sign. I rebuilt my discovery questions to include "Who else needs to agree to this, and what matters to them?" R: I used that question on every deal the next quarter, and my win rate on opportunities over $10,000 went from 1 in 6 to 1 in 3. The loss still stings, but it made me a better seller.
6. "Tell me about a time you took the lead without being asked."
What they're testing: initiative, and whether you bring others with you.
S: Our team's onboarding for new hires was a 40-page document that nobody finished. T: It wasn't my job, but I'd been the newest hire and knew where people got lost. A: I asked my manager for two hours a week for a month, interviewed the three most recent hires, and turned the document into a one-week checklist with a buddy assigned for each day. I asked two senior colleagues to review it before sharing. R: The next two new hires were handling tickets on their own in week two instead of week four. My manager asked me to own onboarding from then on.
7. "Tell me about a time you dealt with an unhappy customer."
What they're testing: calm, empathy, and whether you solve the problem as well as the emotion.
S: A restaurant customer's anniversary dinner was served 40 minutes late because the kitchen lost their order. T: As the shift supervisor, I needed to rescue the evening, not just apologise. A: I went to the table myself, told them plainly what had gone wrong without blaming the kitchen, and asked what would make it right. They mainly wanted their evening back, so I had their mains fast-tracked, comped dessert, and checked on them twice more. R: They left a five-star review that mentioned how the problem was handled, and I used the incident to add a ticket check that stopped lost orders on busy nights.
8. "Tell me about a time you explained something complex to a non-expert."
What they're testing: whether you adapt to your audience.
S: As a data analyst, I found that our "active users" number was counting some people twice. T: I had to explain to the marketing director why her headline number was about to drop by 12%. A: I skipped the SQL. I used an example of one real (anonymised) customer who logged in on a phone and a laptop and was counted as two people, showed the corrected number next to the old one, and explained what the new number meant for her campaign targets. R: She understood immediately, asked me to present it to her team, and we reset the targets before the quarterly review rather than after.
9. "Tell me about a time you were proud of your work."
What they're testing: what you value. Choose something that matters for the job you're applying for.
S: I volunteered to redesign the sign-up form for a community charity where 60% of people abandoned it halfway through. T: I had no budget and two weekends. A: I watched five people use the form, cut it from 14 fields to 6, and moved optional questions to after sign-up. R: Completion went from 40% to 71% in the first month. I'm proud of it because I tested with real people instead of guessing.
10. "Describe a time you had to do something you disagreed with."
What they're testing: whether you can disagree and still commit — without complaining.
S: My manager decided to move our team's weekly reports from written documents to live calls. T: I thought written reports were more efficient and said so, but the decision was made. A: I committed to making the calls work: I proposed a fixed 20-minute agenda, and sent a three-bullet written summary after each call so nothing got lost. R: Six weeks later the team agreed the calls were better for surfacing problems early, and the written summary stayed. I learned that I can disagree, say so once, and then help the decision succeed.
How to prepare in one evening
- Pick 6–8 stories from your work, studies or volunteering: a conflict, a failure, a success you're proud of, a time you led, a difficult customer or stakeholder, a data-driven decision, a time you learned fast.
- Write each one in STAR form — a few bullet points, not a script.
- Map your stories to the 30 questions above. Most stories answer three or four questions; you don't need 30 stories.
- Say them out loud with a timer. If a story takes more than two minutes, cut the Situation, never the Action.
- Practise with questions you haven't seen, so you get used to choosing the right story on the spot.
Common mistakes
- Answering hypothetically. "I would…" is not an answer to "Tell me about a time…". If you truly have no example, say so, and describe the closest real situation.
- The "we" answer. Credit your team, but make your own actions clear.
- No result. "And then it was fine" leaves the interviewer to guess whether you succeeded.
- The humble-brag failure. "I work too hard" is not a failure, and interviewers have heard it thousands of times.
- Rambling Situations. If the setup takes a minute, the interviewer has stopped listening before you get to the good part.
Frequently asked questions
How many behavioral questions will I get in an interview?
In a typical 45–60 minute interview, expect four to eight. Some companies run fully behavioral interviews; others mix them with technical or situational questions.
What's the difference between behavioral and situational questions?
Behavioral questions ask what you did ("Tell me about a time…"). Situational questions ask what you would do in a hypothetical ("What would you do if…"). For situational questions, a real past example still makes your answer more convincing.
Can I use examples from outside work?
Yes — especially early in your career. University projects, volunteering, sports teams and side projects all count, as long as the story shows the skill the question is about.
Is it OK to use the same story twice?
Within one interview, try not to. Across different interviewers at the same company, it's fine — they rarely compare notes that closely, and a strong story is a strong story.