Published · Updated
Behavioral interview questions ask what you actually did in a specific past situation, not what you would do in a hypothetical one. Each question targets one named competency, such as teamwork, resilience or adaptability, and your answer is scored against that competency rather than judged as a whole. The structure that fits how they are marked is situation, task, action, result.
This page sets out how that structure works, the ten questions that come up most often, what each one is scoring, and worked answers you can model your own on.
What is a behavioral interview?
The premise of a behavioral interview is that how you have behaved in the past is the best available guide to how you will behave in a similar situation in future. So instead of asking what you would do, the interviewer asks what you did.
The questions almost always start with the same few phrases: “tell me about a time when”, “describe a situation where”, “give me an example of”. Each one is a request for a single real episode with a beginning, a middle and an end.
Why employers use them
The practical reason is comparability. When every candidate is asked the same questions and the answers are scored against the same written criteria, an interviewer can compare candidates on evidence rather than on impression. It is also harder to prepare a generically impressive answer for a question that requires a specific event.
For the candidate that has one useful consequence: the scoring is not secret. The competencies being marked are usually the ones written in the job description, which is where your preparation should start.
What to expect
A behavioral interview is typically structured, and the components are predictable:
- Introduction. The interviewer introduces themselves and explains how the interview will run.
- Job-related questions. Your experience, skills and qualifications against the role.
- Behavioral questions. Usually four to eight, each aimed at one competency.
- Follow-up questions. Probes to establish what you personally did. Expect “what was your part in that?” and “what would you do differently?”
- Your questions. Your chance to ask about the role, the team and the company.
Interviewers take notes throughout, which is why a rambling answer is costly: what cannot be written down cannot be scored.
The STAR method: situation, task, action, result
STAR is not a script. It is the order in which an interviewer needs the information, so that they can write down what you did and score it.
Situation
Two or three sentences of context: where you were, roughly when, who else was involved, and what was at stake. The interviewer needs enough to picture it and nothing more. Company history, org charts and job titles nobody asked about all come out of the time you need later.
Task
One sentence on what you were responsible for. This is the part candidates skip most often, and it is the part that makes everything after it creditable to you rather than to your team. “I was the one who had to get the pack out by the new date.”
Action
Around half your answer. The steps you took, in the order you took them, with the reasoning behind the important ones. Say “I” wherever the action was yours. An answer delivered entirely in “we” cannot be scored, and the interviewer will interrupt to ask what you personally did.
Result
What changed, with a number wherever you have one, then one line on what you took from it. If you have no number, give a clear before and after instead of a word like “significant”.
A worked STAR answer
Question: “Give an example of a time you had to meet a tight deadline.”
Situation. “In my last role I produced the monthly client reporting pack. In November the client moved their board meeting forward by a week, which cut production time from ten working days to four.”
Task. “I owned the pack end to end, so how to make the new date without losing the parts the board relied on was my call.”
Action. “I started by asking the client which sections the board actually used, rather than assuming all nine mattered equally. It was three. I paused the other six, brought the data pull forward by two days by running it on partial month figures and refreshing only the final numbers, and put a hard cut-off on the design step so it could not absorb the time I had saved. I told the client on day one what they would get and what they would not, so nothing was a surprise on the day.”
Result. “The pack landed the day before the board meeting with the three sections they used, and a note on the six that were paused. They kept the shorter format, so from December the pack took four days rather than ten as standard.”
That answer runs to about ninety seconds spoken, names one decision the candidate made and why, and ends on a measurable change. It also passes the harder test: every sentence is something the interviewer could write in a scoring box.
Five ways STAR answers go wrong
- Answering hypothetically. “I would sit down with them and…” is not an answer to “tell me about a time”. If you genuinely have no example, say so and offer the closest real one you have.
- Never leaving the situation. Long setups are the single most common way candidates run out of time before the result.
- Saying “we” throughout. Use “we” for the context, “I” for your actions.
- Stopping before the result. An answer with no outcome reads as an activity, not an achievement.
- Choosing a safe example. If nothing was at risk and nothing could have gone wrong, there is nothing for the interviewer to score.
For a longer walkthrough of the format, see our STAR interview method guide.
Ten common behavioral interview questions
Each of these targets a specific competency. Knowing which one tells you what to put at the center of the answer.
1. Describe a time you faced a challenging situation at work and how you handled it
Competency scored: resilience and problem solving.
Choose a difficulty that came from the work itself rather than from a difficult person, unless you can describe the person without disparaging them. The interviewer is listening for what you did when your first approach did not work.
A weak answer describes a hard week. A strong one names the moment the situation turned and says what you did at it.
2. Tell me about a time you worked in a team to achieve a goal
Competency scored: collaboration.
Say what your part was, and say what you did that the others did not. Candidates worry this sounds like taking credit, so they retreat into “we”, and then score nothing.
If you can, include a moment where you deferred to someone else’s judgment. Collaboration includes losing an argument well.
3. Give an example of a time you had to meet a tight deadline
Competency scored: prioritization under pressure.
This is the question worked through in full above. The key move is showing what you dropped or deferred, because a deadline met by simply working longer hours tells the interviewer nothing about your judgment.
4. Describe a situation where you had to resolve a conflict with a colleague or customer
Competency scored: interpersonal skill and composure.
Model answer. “Situation: a colleague in operations and I disagreed about how quickly a new returns process should go live. He wanted it in before the seasonal peak; I thought the training was not ready. Task: we had one week to agree, and both teams were waiting. Action: I asked to talk it through away from the group, because we had been arguing in front of both teams. I asked him what he was most worried about, which turned out to be a backlog he had lived through the previous year. That was a fair concern and I had not understood it. We agreed a middle route: the process would go live for one product category before peak, and the rest afterwards, with the training running against the live category first. I wrote it up and sent it to both teams the same afternoon. Result: the category went live on his timetable, the training gap I was worried about never materialized, and the full rollout ran in January without a backlog.”
Note what the answer does not do: it does not make the other person the villain, and it does not claim total victory. Interviewers are wary of both.
5. Tell me about a time you took the initiative to improve a process
Competency scored: proactivity.
The test is whether you acted without being asked, and whether the change stuck. Say who else had to agree to it, since improvements that require nobody’s agreement are usually small ones.
6. Tell me about a time you received constructive feedback
Competency scored: self-awareness and coachability.
Choose real feedback about something you actually needed to change. Feedback that flatters you (“I was told I work too hard”) is transparent and wastes the question.
Include the part most candidates leave out: what you did differently afterwards, and how you knew it had worked.
7. Describe a time you had to adapt to a change in circumstances
Competency scored: adaptability.
Say what you had to give up, not just what you took on. Adapting well usually means dropping a plan you were attached to, and being able to describe that is what distinguishes the answer.
8. Tell me about a time you had to lead a team
Competency scored: leadership.
Leadership here does not require the job title. Leading a project, an incident response or a group of volunteers all count, as long as you can describe how you set direction and how you handled someone who was not delivering.
9. Give an example of a time you had to communicate complex information
Competency scored: communication.
The substance of this answer is the choice you made about the audience: what you left out, what you translated, what medium you used and why. Ending with evidence that they understood, such as the decision they were then able to make, is stronger than saying you explained it clearly.
10. Describe a time you had to learn a new skill quickly
Competency scored: learning agility.
Say how you learned, not just that you did. Who you asked, what you read, how you checked that you had it right, and what you got wrong first. The mistake is usually the most convincing part.
Behavioral assessments and situational judgement tests
Some employers run a written behavioral assessment before the interview, or alongside it. These are not the same thing as the interview, and it helps to know which you are facing.
Situational judgement tests present a realistic workplace scenario and ask you to rank or choose between plausible responses. They cover much the same ground as questions 2, 4 and 8 above, but in writing and against a scoring key set by the employer. Personality questionnaires, covered on our personality test pages, measure preferences and working style rather than right answers.
Our guide to behavioral assessments goes into what each format involves. Working through practice scenarios has a side benefit for the interview itself: it makes you fluent in describing why you would choose one response over another, which is exactly what the follow-up questions are probing.
How to prepare
Preparation for a behavioral interview is not a matter of memorizing answers, because you cannot predict the exact wording. It is a matter of building a small stock of stories you can steer.
Build a bank of six to eight stories
Most behavioral questions can be answered from a surprisingly small set of episodes. Write out six to eight, in STAR form, chosen so that between them they cover conflict, pressure, failure, leadership, change and persuasion.
One story can serve several questions if you shift the emphasis. The deadline story above answers a question about prioritization, and with a different middle section it answers one about stakeholder communication. Know which parts of each story you can move to the front.
Start from the job description
The competencies in the advert are usually the competencies on the scoring sheet. Underline every behavioral word in it, “collaborative”, “resilient”, “self-starting”, and make sure you have a story for each.
Write your results down as numbers
The result is the part people improvise, and improvised results are vague. Before the interview, find the actual figures: the time saved, the percentage, the volume, the error rate, the number of people affected. If no figure exists, write the before and after in one sentence each.
Have a failure ready
Some version of “tell me about something that went wrong” comes up in most behavioral interviews. Prepare one real failure with a genuine cause, what it cost, and what you changed. A rehearsed non-failure is obvious, and it wastes a question you could have scored on.
Practice out loud, and time it
Say your answers aloud rather than reading them. Aim for around two minutes: long enough to include a result, short enough that the interviewer is still writing. Recording yourself once is uncomfortable and unusually effective, because the padding is much easier to hear than to notice.