The STAR method is a four-step way to answer interview questions: Situation (the context), Task (your responsibility), Action (what you personally did) and Result (how it ended). It works for any question that starts with "Tell me about a time when…", and its real value is that it gives you an ending: you know when to stop talking.
Because that's the actual problem. The moment you hear "tell me about a time", a behavioural question has started, and it's where most candidates lose points: they ramble, drift off, and finish without ever saying what they achieved. Not from a lack of experience — from a lack of structure.
What is the STAR method?
STAR is a four-step structure for telling a work experience clearly and convincingly:
- S — Situation: the context, in one or two sentences. Where and when?
- T — Task: your specific responsibility in that situation. What did you have to achieve?
- A — Action: what you did, step by step. It is the heart of the answer: more than half of what you say goes here, in the first person ("I did", not "we did").
- R — Result: what happened thanks to your action. Quantify whenever you can (percentages, time saved, money, people).
Why does it work?
For two reasons, and neither is about impressing anyone.
The first is that an interviewer doesn't assess what you did — they assess what they manage to reconstruct of what you did, in a few minutes, without knowing you. STAR hands them the information in the order their head needs it: first where we were, then what had to happen, then what you did, then how it ended. Without that order, even telling the same story, they lose the thread.
The second reason is for you: it gives you a finish line. Most answers that run long don't run long because there's a lot to tell, but because the person talking doesn't know whether they're done. Once the result is out, you're done. You can stop talking with confidence.
How long should each part be?
A complete STAR answer runs between ninety seconds and two minutes, split roughly like this:
- Situation: 15 seconds. Only what's needed for the rest to make sense.
- Task: 15 seconds. What was at stake and what was yours to handle.
- Action: 60 seconds or more. This is where you're being evaluated.
- Result: 20 seconds. What changed, with a number if you have one.
If your answer runs four minutes, it's almost always because the situation ate the action's time.
A full example
Question: "Tell me about a time you had to meet a very tight deadline."
Situation: At my previous job, a key client moved their campaign launch up by two weeks. Task: I was responsible for delivering all the graphic material on time without losing quality. Action: I reprioritized the backlog, negotiated moving two non-critical tasks, automated format exports with a template, and ran daily 15-minute reviews with the team. Result: We delivered two days before the new deadline and the client renewed the contract for another year.
Notice two things. The action is specific — you can picture what they actually did — and the result has measurable impact. That is what an interviewer still remembers an hour later, after three more candidates.
What if the result was bad?
It's the question almost nobody asks and almost everybody needs. "Tell me about a mistake" or "a project that went wrong" is answered in STAR too, with two adjustments: state the result plainly, and add one short sentence on what you learned and what you do differently now.
Result: The launch slipped by three weeks and we missed the seasonal window. Since then I don't start a project without agreeing in writing who decides what — which is exactly what we were missing there.
Nobody expects a career without stumbles. What's being measured is whether you can look at a mistake straight on without blaming everyone around you.
Common mistakes
- Getting stuck on the situation: spending a minute on context and ten seconds on the action. Flip the ratio.
- Speaking in plural: "the team achieved…". The interviewer is evaluating what you did. You can credit the team and still say which part was yours.
- Forgetting the result: a story without an ending does not convince. Always close with the impact.
- Picking a story that's too old: if you have recent experience, use it. An example from ten years ago suggests nothing has happened since.
- Telling it like a short story: STAR isn't literary narrative. It's ordered information. No suspense.
Which questions is STAR not for?
This gets said far too rarely, and it prevents a very visible mistake: STAR is for behavioural questions, and half an interview isn't behavioural. Forcing a four-part story where it doesn't belong makes you sound like a manual.
- "Tell me about yourself." Not a story — a summary. Sixty to ninety seconds: who you are professionally, two achievements relevant to this role, and why it interests you.
- "Why do you want to work here?" Answered with what you know about the company and what you bring, not with an anecdote.
- "What would you do if…?" It's hypothetical: it hasn't happened, so there's no result to report. Explain how you'd approach it, what you'd ask first, what you'd weigh. If you have a real comparable case, use it afterwards, as backup.
- Technical questions. Answered with the knowledge, directly. Nobody wants the backstory of the time you used that tool.
- "What's your biggest weakness?" A short, honest answer plus what you're doing about it works far better here.
The tell is simple: if the question opens with "tell me about a time", "give me an example of" or "describe a situation where", it's STAR. If not, it probably isn't.
How many stories should you prepare?
Fewer than you think. Six to eight well-told ones cover most of what you'll be asked, because the questions repeat and one story serves several of them.
Prepare one of each kind: a hard problem you solved, a conflict with someone, a mistake, a time you led or pushed a change, a situation with an impossible deadline, and one where you had to learn something fast. Write each in four lines — no more — and hold on to the numbers.
One detail that saves a lot of time: the same story can be told from different angles. The tight-deadline one works for "tell me about a time you worked under pressure", for "give me an example of prioritisation", and for "tell me about a time you had to negotiate". You don't need one story per question; you need to know which part to bring forward.
How to master it
Writing STAR stories is the easy part. Saying them is the hard part: in your head they sound polished, out loud they tangle. Which is why the only rehearsal that counts is out loud, ideally on a timer.
To see where your structure breaks down, voice interview practice includes real-time STAR coaching and flags exactly which part (S, T, A, or R) was missing in each answer. Pair it with this list of common interview questions and you arrive ready. And if what worries you isn't the structure but the nerves, that has its own explanation and its own training.
One last thing
STAR is not a script to recite, and it shows badly when someone recites it. It's scaffolding: you use it while you build the answer, and once the answer comes naturally it stops being visible. The goal isn't to sound structured. It's to not forget to say how it ended.