The STAR method, explained with two worked examples
Situation, Task, Action, Result: a simple frame for behavioural questions. What each part is for, where answers go wrong, and what a strong one sounds like.
Answers
STAR
In this article
Behavioural questions (“Tell me about a time when…”) ask for evidence of how you actually work, not for a description of how you would like to work. The difficulty is rarely the lack of experience. It is that a real story, told off the cuff, wanders: too much background, an unclear role, and no ending. STAR gives the story a spine, so the listener can follow it and you know where you are in it.
What each letter is for
Situation
Set the scene in one or two sentences: where, when, and what was at stake. Only include what the listener needs to understand the rest.
Task
Say what was your responsibility. A team can have a goal, but the interviewer is hiring one person, so name the part that was yours.
Action
Describe what you did, step by step, in the first person. This is the longest part and the one that is actually being assessed. Include the decisions and the reasons for them.
Result
Say what changed, how you know, and what you would do differently or keep doing. A result can be modest, and it can be mixed, as long as it is honest.
TipMind the proportions
Situation and Task together should take a fifth of the answer at most. Most of the time belongs to Action. An answer of about two minutes spoken is usually enough; if you need longer, the story probably holds two stories.
Example 1: delivering under pressure
Both examples in this article are invented for illustration. Use them to see the shape, not to borrow the content: an answer works only when it is about something that really happened to you.
Worked example (invented for illustration)
A report with a late data source
The question: Tell me about a time you had to deliver something under pressure.
Situation
In my previous role our team was preparing a customer-facing report due on Friday. On Wednesday the data supplier told us that one of the three sources would arrive two days late.
Task
I owned the analysis section, so it was my job to keep the Friday date without publishing figures we could not stand behind.
Action
I split the section into the parts that depended on the late source and the parts that did not, and finished the second group first. The same day I told my manager what was at risk and proposed two options: send the report on Friday with that section marked as preliminary, or move the whole report to Monday. We chose the first. I wrote a short note for the client explaining which figures were preliminary and why, and on Monday morning I replaced them with the final numbers.
Result
The client received the report on the agreed day, and the note meant the small change in one chart was expected rather than a surprise. The client asked us to keep the preliminary and final format for later reports. What I took from it: raise a risk the day you see it, and arrive with options rather than only the problem.
Notice what makes this work. The role is clear (“I owned”), there is a decision with a trade-off, and the result includes a lesson, not only an outcome.
Example 2: a mistake you made
Questions about mistakes are not traps. The interviewer wants to see whether you notice problems, own them and fix the cause. A story with no real mistake in it, or one that quietly blames someone else, tells them the opposite.
Worked example (invented for illustration)
An invoice batch with the wrong tax rate
The question: Tell me about a mistake you made at work and what you did about it.
Situation
Three months into a finance assistant job, I took over the monthly invoicing run. In my second run I applied the wrong tax rate to one category of customers.
Task
A client emailed to ask about their invoice, and I realised that the error was mine and that it might not be limited to that one client.
Action
I stopped what I was doing and checked the whole batch against the price list. I found a handful of other affected invoices, all in the same category. I told my manager before she heard it from anyone else, sent corrected invoices the same day with a short, plain apology, and asked the clients to discard the originals. Then I looked for the cause: the rate came from a template I had copied from an older file. I replaced it with a lookup and added a final check against the price list before sending.
Result
Every client had a correct invoice within a day and none of them disputed the correction. The check is still part of the process, and it has since caught errors that were not mine. I now treat anything I copy from an older file as unverified until I have checked it.
A good STAR answer is not a performance. It is a small, true story told in the order the listener needs it.
Common mistakes
- Too much Situation. Three minutes of background and thirty seconds of what you did. Start closer to the action.
- “We” all the way through. If the listener cannot tell what you personally did, they cannot assess you. Say “we” for the team’s goal and “I” for your steps.
- No Result. The story simply stops. Always land it: what happened, and what you learned.
- A result with nothing behind it. “It went really well” is a feeling. A reaction, a decision, a change in how the team worked is evidence.
- A story chosen to flatter rather than fit. Pick the story that answers the question asked, even if another one sounds more impressive.
- Reciting. A memorised script falls apart at the first interruption. Remember the beats, not the sentences.
Build your own bank of stories
- List five or six real situations from the last few years: a deadline, a disagreement, something that went wrong, something you improved, a time you helped someone else.
- For each one, write four short lines, one per letter. Bullet points, not sentences.
- Mark the themes it can serve: pressure, conflict, initiative, mistake, learning something new. One strong story often answers several different questions if you change the emphasis.
- Check each for concrete detail: a name of the tool, the order you did things in, what you said. Detail is what makes a story believable.
- Say each one out loud, once, with a timer. Cut whatever you stumble over.
NoteEarly in your career?
A situation does not have to come from a job. Study projects, volunteering, a part-time job, a club you ran or a problem you solved for family all count, as long as they are real and you can describe your own part in them.
STAR is a tool for remembering, not a form to fill in. Once the four parts are second nature, you can let the answer sound like a conversation. The structure is still there; the listener just never has to notice it.