Behavioural Interview Answers: The STAR Method, With Examples
Behavioural questions such as "Tell me about a time you disagreed with a teammate" are where well-prepared engineers still lose offers. The usual problem is not a lack of experience. It is a rambling answer that never lands on a result. The STAR method fixes that by giving every answer the same shape.
What is the STAR method?
STAR stands for four parts of a complete answer:
- Situation: the context. Where were you, and what was going on? One or two sentences.
- Task: your responsibility or the goal you were trying to reach. One sentence.
- Action: what you did, step by step. This is the longest part, and the one interviewers care about most.
- Result: what happened because of your actions, with a number or concrete outcome where you can, and what you learned.
Aim for about two minutes in total. Spend roughly 20% on situation and task, 60% on action and 20% on result.
A worked example
The question: "Tell me about a time you had to deliver under a tight deadline." The story below is an illustration of the structure, not a script to copy.
Situation: Our team had committed to launching a billing change before the end of the quarter, and two weeks out we found the payment provider's API worked differently from what we had planned for.
Task: I owned the integration, so it was my job to find a path that still met the date without risking customer charges.
Action: I listed what had to ship and what could wait, and agreed with the product manager to launch for new customers first and migrate existing ones later. I wrote a small adapter so the rest of the code did not depend on the provider's quirks, added tests for the failure cases, and ran the flow against the provider's test environment daily. I shared a short status note each morning so nobody was surprised.
Result: We launched on time for new customers with no billing errors, and migrated existing customers over the following sprint. The adapter also made the next provider change a one-day task.
Notice what it does well: it uses "I" for the actions, shows a trade-off decision, and ends with a clear outcome.
Themes to prepare for
Most behavioural questions fall into a small number of themes. Prepare at least one story for each:
- A conflict or disagreement with a colleague
- A mistake or failure, and what you changed afterwards
- Leading or influencing without formal authority
- Working with ambiguity or unclear requirements
- A tight deadline or competing priorities
- A project you are proud of and why
- Giving or receiving difficult feedback
Build a story bank
Do not write one answer per question. Write six to eight strong stories and learn to bend each to several questions. For each story, note the situation, your key actions, the result with a number, and which themes it can serve. A story about a failed launch might answer questions on failure, ambiguity and communication. Practise each aloud until it takes about two minutes and sounds natural rather than memorised.
Common mistakes
- Saying "we" throughout. Interviewers need to know what you personally did. Credit the team, but make your own actions clear.
- No result. An answer that trails off without an outcome feels unfinished. Always close the loop.
- Too much setup. If the situation takes a minute, you have left too little time for the action.
- A failure story with no lesson. The point of a failure question is what you changed afterwards.
- Making up details. Interviewers probe with follow-ups. Use real stories you can discuss comfortably in depth.
Prepare for follow-up questions
A good interviewer will ask "What would you do differently?" or "How did the other person react?" Rehearse a couple of follow-ups for each story, because the second question is where polished but shallow answers fall apart. Practising with someone who interrupts, or with an AI that asks follow-ups, helps a lot. Our 4-week prep plan puts behavioural practice in the final week.
Practise this with AI
Generate questions for your target role in one click, attempt them first, then reveal the full solution and answer AI follow-ups.
Generate your first question