Answer guide
The STAR method for behavioral interviews
Behavioral questions ask about something you have actually done: “Tell me about a time when…”. The STAR method is the simplest way to answer them: Situation, Task, Action, Result. It keeps the story short, puts the weight on what you did, and ends on proof.
By Nikhil Utane · Updated
The four parts
A good answer runs about two minutes. Here is roughly how to spend them.
Situation
About 15%
Set the scene in two or three sentences: where you were, when, and what was at stake. Give the panel just enough to follow the story. Company history, org charts and project code names can go.
Task
About 10%
Say what you were responsible for and what made it hard. This is where you show the bar you had to clear: a deadline, a target, a conflict that had to be resolved, a decision only you could make.
Action
About 60%
The steps you took yourself, in order. This is the part interviewers score, so make it the longest. Say "I", name the conversations you had and the choices you made, and explain why you made them.
Result
About 15%
What happened because of what you did, with numbers if you have them: time saved, revenue, defects, retention, a promotion. Finish with what you learned or would do differently next time.
A worked example
Question: “How do you handle a project that is falling behind schedule?”
- Situation
- Last year I led a four-person team moving our billing system to a new payment provider. The old contract ended on 31 March, so the date could not move.
- Task
- Six weeks out, our burndown showed us three weeks behind. I had to get us live on time without cutting the reconciliation checks finance relied on.
- Action
- I went through the remaining work with the team and found that almost half of it was migrating rarely used plan types. I took that to the product owner with numbers: those plans covered 2% of customers. We agreed to move them by hand after launch. I also asked finance to review reconciliation reports weekly instead of at the end, so problems surfaced early, and I took the vendor calls myself so the engineers could keep building.
- Result
- We went live four days before the deadline with no billing errors in the first month, and moved the remaining plans by hand in the following two weeks. Since then I scope the long tail of any migration in the first week, not the last.
Notice that the Action is the longest part, every step is something “I” did, and the Result has a date, a quality measure and a lesson.
Mistakes that cost the most
- Saying "we" throughout. The panel cannot score a team. Say what the team did in one line, then what you did.
- A long Situation. If the setup takes more than 30 seconds, the interviewer has stopped listening before the part that counts.
- No result. A story that ends at "and then we shipped it" leaves the panel guessing. Say what changed, ideally with a number.
- A hypothetical instead of a story. "I would…" is not evidence. Behavioral questions ask what you did, so pick a real time.
- The same story for every question. Prepare six to eight stories that cover leadership, conflict, failure, a hard decision and an achievement, then map each question to one.
How to prepare
- List six to eight real stories from the last few years: a success, a failure, a conflict, a hard decision, leading people, and learning something fast.
- Write each one as STAR notes, a few lines per part, not a script.
- Match the job description's requirements to your stories, so each one has evidence behind it.
- Say each answer out loud and time it. Most first attempts run long, and the Action is usually too short.