What is the STAR method, and how do you use it in an interview answer?
STAR is a four-part structure for behavioural interview answers: Situation, Task, Action, Result. Here is what each part must contain, the mistakes that cost candidates points, and a worked example.
- STAR stands for Situation, Task, Action, Result — four parts of one spoken answer, usually 60–120 seconds long.
- Situation and Task together should take about 20% of the answer; Action about 50%; Result about 30%.
- The Action section must describe what you personally did, not what the team did.
- A Result without a number is the most common reason a STAR answer is scored as weak.
- STAR is used by most large employers for competency-based interviews, and by Amazon (which extends it with a fifth part, the outcome learned).
What does each letter of STAR mean?
Situation is the context: where you were, what was at stake, and why it mattered. Two sentences is enough. Interviewers do not need the org chart; they need the constraint.
Task is your specific responsibility in that situation. This is where you separate yourself from the team: “I owned the migration”, not “we were migrating”.
Action is the largest part of the answer. Say what you did, in order, including the decision you made and the trade-off you rejected. One or two concrete details (the tool, the number, the person you convinced) do more than three paragraphs of generalities.
Result is the outcome, with a number attached. Revenue, time saved, error rate, users affected, adoption. If you truly cannot quantify it, describe the observable change: what a customer now can do that they could not before.
What are the most common STAR mistakes?
The fix for all five is the same: pick fewer stories, and make each one have a decision you can defend and a number you can quote.
- Spending 80% of the answer on Situation and Task, then rushing the Action — the interviewer learns nothing about you.
- Telling a team story in the first person plural throughout, so no individual contribution can be assessed.
- Ending with “and it went well” instead of a measurable result.
- Choosing a story where you had no agency, because the question mentions leadership or conflict.
- Rehearsing the words instead of the structure, so the answer collapses under one follow-up question.
A worked STAR answer
Question: “Tell me about a time you disagreed with your manager.”
Situation: “Our checkout conversion dropped 12% after a pricing change, and my manager wanted to revert the whole redesign.”
Task: “I owned the checkout flow, so I had to either prove which part caused the drop or accept the revert.”
Action: “I split the funnel by step and found the drop was concentrated in the coupon field, not the layout. I ran a two-week test that kept the new design but restored the old coupon interaction, and brought the evidence to my manager before the revert deadline.”
Result: “Conversion recovered to within 1% of the old baseline, we kept the redesign, and the same funnel-splitting method became the default for later releases.”
Questions people also ask
How long should a STAR answer be?
Aim for 60–120 seconds spoken. Long enough to include a decision and a result, short enough that the interviewer can still ask a follow-up. If you regularly pass two minutes, you are usually over-explaining the Situation.
Does every answer need STAR?
No. STAR is for questions that ask for an example from your past (“tell me about a time…”). For hypothetical questions (“how would you design…”) you need a different structure: assumptions, approach, trade-offs, result.
What if I cannot remember a number for the Result?
Estimate honestly and say it is an estimate, or describe a verifiable change instead: a process that now runs weekly, a customer who renewed, a bug class that no longer ships. Vague praise (“it went really well”) is the part that reads as weak.
Answer this in the coach, and get it scored.
Novue runs a live mock interview, scores five categories, and rewrites each of your answers in your own words. Free during the beta.
Start practising