Behavioral Interview Questions: 40 Examples, and Why Your Story Sets the Score

Behavioral interview questions look like the easy part of an interview, because every candidate knows the format: describe a time when something happened, then say what you did. That familiarity is the trap. Most people prepare the delivery and neglect the one choice that actually moves the score.

In a structured interview, your answer goes onto a rating scale. The US Office of Personnel Management's model runs from Level 1, applying a skill "in the simplest situations", to Level 5, applying it "in exceptionally difficult situations". The question stays the same for every candidate. The situation you choose to describe does not — and that choice caps your rating before you say a word about what you did.

So this guide gives you 40 questions grouped by the competency each one tests, a note on what a strong answer contains, and a method for choosing stories that score at the top of the scale rather than The opener that comes before them works differently, and how to answer the tell-me-about-yourself question covers that separately.

What do behavioral interview questions actually score?

Each behavioural question starts as a competency from a job analysis and exists to draw out a past example of it. OPM's Structured Interview Guide states the premise directly: the best predictor of future behaviour is past behaviour under similar circumstances.

Here is OPM's five-level scale, with its own examples for interpersonal skills:

Nothing in the right-hand column concerns how well the candidate told the story. The anchors describe what kind of situation it was, so a flawless answer about greeting applicants still sits at Level 1. Private employers vary in formality, but structured behavioral interview questions mostly work this way: a question, standard probes, and a score per competency.

Why does structure matter so much to your score?

Schmidt and Hunter's 1998 meta-analysis put structured interviews at a validity of 0.51. Sackett and colleagues revisited the estimates in 2022, fixing an overcorrection in the older method. Their revised figures came in at 0.42 for structured interviews against 0.19 for unstructured ones — roughly twice the predictive power.

SIOP's summary of the study reports that they had the highest mean operational validity of any predictor examined, ahead of cognitive ability at 0.31.

Two consequences follow. The questions are fixed: you cannot steer the conversation towards your strengths, because every candidate hears the same behavioral interview questions in the same order. And the notes matter more than the mood: a warm conversation that left thin notes scores below a stiff one that produced a clear situation, action and result.

Which behavioral interview questions come up most?

Each line gives the question and the element that separates a high score from a middling one. Answer in the STAR structure — the STAR method interview guide covers the mechanics, so this list concentrates on story choice.

Teamwork and collaboration

1. Tell me about a time you worked on a team that wasn't getting along. Show what you changed, not how the team eventually settled.
2. Describe a project where you relied on someone else's work. Name the dependency and how you managed the risk of it.
3. Give an example of helping a colleague who was struggling. Pick one where helping cost you something, such as time on your own deadline.
4. Tell me about a time you had to share credit. A strong answer shows you credited others without erasing your own contribution.
5. Describe working with someone whose style was very different from yours. Land on a specific adjustment you made, not on mutual respect.

Conflict and difficult people

1. Tell me about a disagreement with your manager. Choose one where you held your position with evidence, whichever way it ended.
2. Describe a time you dealt with an upset customer or stakeholder. State what was at risk; the difficulty of the situation drives the score.
3. Give an example of a conflict between two colleagues you helped resolve. Show the mechanism you used, such as a shared metric or a joint meeting.
4. Tell me about receiving criticism you thought was unfair. Separate what you accepted from what you pushed back on.
5. Describe a time you had to say no to someone senior. The result should include how the relationship held up afterwards.

Leadership and influence

1. Tell me about a time you led without formal authority. Name the lever you used: data, a prototype, or an ally.
2. Describe persuading someone who initially disagreed with you. Show that you understood their objection before you answered it.
3. Give an example of delegating something important. Include how you checked progress without taking it back.
4. Tell me about motivating a team through a difficult period. Concrete actions beat descriptions of your attitude.
5. Describe a decision you made that was unpopular. Show your reasoning, and whether it proved right.

Problem-solving and judgement

1. Tell me about a complex problem you solved. Spend more time on how you diagnosed it than on the fix.
2. Describe a decision you made with incomplete information. Say what you knew, what you assumed, and how you limited the downside.
3. Give an example of spotting a problem before others did. The signal you noticed is the most interesting part.
4. Tell me about a time you used data to change a plan. Give the number that changed your mind.
5. Describe choosing between two good options. Name the criteria you weighed and what you gave up.

Failure, mistakes and accountability

1. Tell me about a time you failed. Pick a real failure with real consequences; a disguised success scores poorly.
2. Describe a mistake you made at work and how you handled it. Show that you reported it before someone else found it.
3. Give an example of missing a deadline. Explain what you changed in your process afterwards, with evidence it worked.
4. Tell me about feedback that changed how you work. The before-and-after needs to be observable, not just felt.
5. Describe a project that didn't go as planned. Own your share without blaming circumstances.

Adaptability and pressure

1. Tell me about a time priorities changed suddenly. Show how you decided what to drop.
2. Describe working under a very tight deadline. Quantify the deadline and the trade-offs you made to hit it.
3. Give an example of learning something new quickly. Name the skill, the timeframe, and what you produced with it.
4. Tell me about adapting to a major change at work. A reorganisation or new system works well; show early action rather than tolerance.
5. Describe handling several urgent tasks at once. Explain your triage rule, not just that you coped.

Communication

1. Tell me about explaining something complex to a non-expert. Include how you checked that they understood.
2. Describe a time you had to deliver bad news. Timing and framing are what the interviewer rates.
3. Give an example of a written document that made a difference. Say what it caused someone to decide or do.
4. Tell me about a misunderstanding you had to fix. Show what caused it and what you changed to prevent a repeat.
5. Describe presenting to a sceptical audience. Name the toughest question you faced and your answer.

Initiative and results

1. Tell me about a time you went beyond your role. Make sure it was needed, not just extra.
2. Describe improving a process nobody asked you to fix. Give the before and after in numbers.
3. Give an example of setting yourself a goal and hitting it. Stretch goals score higher than safe ones.
4. Tell me about your proudest achievement. Choose the most difficult one, not the most prestigious.
5. Describe a time you had to get something done with limited resources. Name exactly what was missing and how you replaced it.

How do you choose the right story for each question?

Forty questions do not need forty stories. MIT's career advising office recommends preparing three to five, and one good story often covers several competencies. A launch that went wrong can answer failure, pressure, conflict or communication questions, depending on which slice you tell.

Three checks for every story

Difficulty. Would it sit at Level 3 or above on the OPM scale? If a stranger would find the situation routine, find a harder one.

Ownership. Can you name three concrete steps you took? MIT's guidance warns that "we" statements make your skills hard to see.

Result. Is there a number, a decision or an observable change? If the honest result was mixed, say so and add what you learned.

Question: "Tell me about a time you dealt with a difficult stakeholder."
Level 2 story: "A colleague in finance kept asking for my report in a different format. I set up a quick call, agreed a template, and sent it that way from then on."
Level 4 story: "Our largest client's operations director threatened to pull a £400,000 renewal after a data migration broke their dashboards. I had 48 hours before their board meeting. I ran a call with their team to rank the eight broken reports, rebuilt the three the board used, and sent daily progress notes to the director. They renewed, and asked for me on the next project."
Both candidates speak clearly. The second story wins on difficulty, stakes and independence, which is exactly what the anchors measure.

How do you handle the follow-up probes?

OPM's guide lists probes such as "What factors led up to the situation?" and "What was the outcome?", and tells interviewers to use very similar probes for everyone. A probe does not mean you are failing; the interviewer is filling a gap in their notes.

Most gaps come from three habits:

Staying at team level. If your answer says "we", expect "what was your part?" Pre-empt it.

Skipping the result. Close every story with the outcome and one sentence on what you would repeat.

Choosing a story you can't defend in detail. Probes go deeper than a rehearsed answer. If a reference or your resume would tell the story differently, the gap shows — the same consistency test the greatest weakness interview answer guide describes.

Hypothetical questions ("what would you do if…") follow different rules. Those belong to situational interview questions, where no past example is required.

What can't preparation fix?

Story selection raises your score only as far as your real experience allows. A graduate asked about influencing senior leaders will not have a Level 5 story, and interviewers calibrate for the role. A strong Level 3 answer for a junior post beats an inflated one that collapses under the first probe.

Structure also cannot remove every bias, and plenty of employers still run loose, conversational interviews where rapport counts for more than it should. Preparing for behavioral interview questions with harder stories helps in both settings, because a specific situation with a clear result reads well Rounds that test skills rather than stories need their own preparation, which is what preparing for a technical interview is for.

To practise out loud, Rezoom's interview preparation tool generates behavioral interview questions from the job posting and lets you rehearse your story bank against them.