The STAR method: how to answer behavioral interview questions
By Emre Hanaz · Updated October 2026 · 6 min read
"Tell me about a time you…" is the most common way interviewers test how you actually work. They want evidence, not opinions, and the STAR method is the simplest way to give it. It keeps your answer short, in order, and tied to a result.
What STAR stands for
- Situation — the context in one or two sentences. Where were you, and what was going on?
- Task — your specific responsibility or goal. What were you on the hook for?
- Action — what you personally did, step by step. This is the core of the answer.
- Result — what changed because of what you did, ideally with a number, and what you learned.
How long should each part be?
A good spoken answer runs about 90 seconds to two minutes. As a rough split: Situation and Task together take about a fifth of the time, Action takes more than half, and Result takes the rest. The most common mistake is the reverse: a long, detailed setup and a rushed, vague ending.
A worked example
Question: Tell me about a time you had to deliver under a tight deadline.
Situation: When I joined my last team, our release process took two full days and had caused two late launches that quarter.
Task: I was asked to cut that down without adding risk before the next launch, three weeks away.
Action: I mapped every manual step, automated the three slowest ones, and wrote a checklist for the rest. I ran the new process on two low-risk releases first and fixed what broke.
Result: We shipped the next launch in four hours, on time, and on-call pages dropped by about forty percent over the following quarter.
Notice what makes it work: one story, "I" instead of "we" in the Action, a concrete number in the Result, and nothing the candidate couldn't back up with a follow-up question.
Mistakes that sink behavioral answers
- Saying "we" throughout. The interviewer is hiring you, not your team. Name your own part.
- No result. If you can't give a number, give an outcome: what shipped, what improved, who noticed.
- Rambling setup. If you're 45 seconds in and still describing the situation, cut it.
- Always picking a success. A story about something that went wrong, and what you changed afterward, often lands better than another win.
- Memorising word for word. Know your stories' beats, not a script, so the answer sounds like you.
Build a small story bank
You don't need fifty stories. Prepare five or six strong ones and learn to bend each to different questions: a conflict with a colleague, a project that failed, a time you led without authority, a tight deadline, a decision made with incomplete information, and something you're proud of. Write each as four short lines, one per letter.
Practice out loud
Answers that read well on paper often fall apart when spoken: they run long, loop back, or trail off. The fix is repetition out loud, with a timer, and honest feedback on structure and specifics.
Practice this with Rehearse. It gives you a timed question, listens to your answer on your iPhone, and scores it on STAR, structure, specificity, concision and delivery, then rewrites your answer using only the facts you actually said.