The STAR method: build an interview answer, then say it out loud
STAR is a four-part shape for answering "tell me about a time when…": the Situation, your Task, the Action you took, and the Result. Build your story in the four boxes below, see how long it runs at your pace, and open it in a free teleprompter to practise it.
The four parts, and how much of the answer each one gets
- Situation (about 15%): where and when, just enough that the rest makes sense. One or two sentences.
- Task (about 10%): what you personally had to do, and why it was hard. One sentence is often enough.
- Action (about 50%): what you did, in order, in the first person. This is the part the interviewer is actually scoring.
- Result (about 25%): what changed, with a number where you have one, and what you took from it.
The proportions are our guidance, not a rule. The common mistake is the reverse: a long Situation, a vague Action and no Result. If your answer runs long, cut the Situation first.
Story builder
Fill in the four boxes in your own words. The answer assembles itself below, with its length at the pace you choose.
Where and when, in one or two sentences. "Last spring, our support queue doubled after a product launch."
What you, personally, had to do. "I was asked to get the backlog under control within a month."
What you did, step by step, in the first person. This is most of the answer.
What changed, with a number if you have one, and what you learned.
Your answer, assembled
Fill in the four boxes and your answer appears here.
Opens your answer in the free teleprompter. The text travels in the link and is never uploaded.
Three worked examples
The people and companies are made up; the shape is what to copy. Each opens in our free teleprompter, which follows your voice as you read.
"Tell me about a time you dealt with a conflict": support team lead
Situation: last year two people on my support team stopped speaking to each other after a disagreement about who had dropped a customer's case. Tickets between them started bouncing, and a customer complained about being passed around. Task: as the team lead, I had to get the two of them working together again within the week, without taking sides, because both were good at the job. Action: I spoke to each of them separately first, and asked what had actually happened rather than who was to blame. It turned out the case had no owner because our handover form had no owner field. I put that in front of both of them together, we agreed a one-line handover rule, and I added the field to the form that afternoon. Result: the bounced tickets stopped that week. Three months later the two of them ran the new-starter training together. The thing I took from it is that most people-conflicts in a team start as a process gap, and fixing the gap is quicker than refereeing.Practise this out loud →
"Tell me about a time you missed a deadline": junior developer
Situation: in my first year as a developer I was given a reporting feature to build in two weeks, for a client demo. Task: I had to deliver the feature on time, and I was the only person on it. Action: I underestimated it. By day eight I knew I was going to be late, but I kept quiet and worked evenings, hoping to catch up. On day eleven I told my lead. She pulled in a colleague for two days, and we cut the feature to the two reports the client would actually see in the demo. Result: we shipped a smaller version a day late, and the demo went fine. What I changed afterwards was the part that was my fault: I now flag a slipping estimate on the day I notice it, not the week after. On my current team I'm the one who asks "what would we cut?" early, and we haven't missed a client date in the year since.Practise this out loud →
"Tell me about a time you led a project": retail store manager
Situation: the store I manage was losing sales every Saturday afternoon because the queue at the tills got so long that people put things back and left. Head office had no budget for more staff. Task: I needed to cut queue times at peak without adding hours. Action: I spent two Saturdays standing by the tills with a notepad. Most of the delay came from returns and age checks being done at the same tills as ordinary sales. I moved returns to the customer-service desk on Saturdays, trained two more people on age checks so any till could do them, and changed the rota so breaks fell before the peak rather than during it. Result: average queue time at peak dropped from about twelve minutes to under five, measured with the same notepad method, and Saturday afternoon sales went up around eight percent over the next quarter. Two other stores in the region copied the rota change.Practise this out loud →
Questions that are asking for a STAR answer
- Tell me about a time you disagreed with your manager.
- Give me an example of a goal you reached, and how you got there.
- Describe a situation where you had to learn something quickly.
- Tell me about a time you made a mistake. What did you do?
- Tell me about a time you had to persuade someone.
- Describe a project where you had too little time or too few resources.
Prepare four or five stories that each answer two or three of these, rather than one story per question. Most interviews draw on the same few.
Five mistakes to avoid
- A Situation that never ends. If the interviewer could not say what you did after thirty seconds, start the Action sooner.
- "We" all the way through. The team sets the scene; "I" does the Action.
- No Result. "And it went well" is not a result. A number, a change, or a lesson is.
- A story with nothing at stake. If nothing could have gone wrong, pick a different story.
- Reciting. Practise it out loud until you can tell it slightly differently each time.
How to practise it
- Build the story in the four boxes, in the words you would say.
- Open it in the teleprompter and tell it out loud three times. Watch where the Situation drags.
- Time it with the speech timer; aim for 90 seconds to two minutes.
- Close the script and tell it from the four headings alone: Situation, Task, Action, Result.
Frequently asked questions
How long should a STAR answer be?
Our advice: 90 seconds to two minutes, which is about 210 to 280 words at a conversational 140 words per minute. Spend most of it on the Action and the Result; the Situation and Task together should fit in three or four sentences.
Which questions are STAR for?
Behavioural questions: anything that starts "tell me about a time", "give me an example of" or "describe a situation where". It is not for "tell me about yourself" or "why should we hire you", which have their own shapes.
Can I use "we" in a STAR answer?
Describe the team in the Situation, then switch to "I" for the Task and the Action. The interviewer is trying to find out what you did; an answer that stays in "we" tells them nothing about you.
What if my result was not a success?
Say what happened, then what you changed afterwards and what has been different since. Interviewers ask about failures on purpose; the Result they are listening for is the lesson and the evidence you applied it.