The STAR method
Four beats, in order. Most answers collapse because the last one is missing, and the second one is the one people skip without noticing.
Reference material, not a script. Read the part you are stuck on and skip the rest — the sections are independent, and nothing here needs to be read in order.
The four beats.
Ninety seconds spoken, roughly 180 to 220 words. The proportions matter more than the total: about a fifth on context, a fifth on what was yours, half on what you did, and a short landing.
Situation
- Length
- 2 sentences
- Share
- About 20%
Where you were, when, and what was going wrong. The interviewer needs enough to judge the difficulty and nothing else. Every extra sentence here is stolen from Action.
Our support queue was 400 tickets deep and first response averaged two days. It had been getting worse for a quarter and two people had left.
So I joined this company in 2021, it is a mid-size firm, quite fast-moving, and the support function reported into operations at the time, which was unusual, and there had been a reorganisation the year before…
The weak version has spent forty seconds and has not yet said what was wrong.
A worked answer, end to end.
The question: "Tell me about a time you improved something nobody asked you to improve." Read the strong version aloud — it takes about ninety seconds.
Our support queue was 400 tickets deep and first response averaged two days. It had been getting worse for a quarter and two people had left.
Situation
I owned triage. Nobody asked me to fix the backlog — response time was mine, and the backlog was the reason it was bad.
Task
I grouped a week of tickets by root cause rather than by product area, which showed three causes making up 60 percent of the volume. I wrote a triage guide so anyone could route those three without asking me. I moved the top cause to a self-serve page — and I got that wrong first time, because the page assumed people knew the error code, so I rewrote it around symptoms. Then I took the rewrite to engineering with the numbers, and they fixed the underlying bug in a fortnight.
Action
First response went from two days to four hours inside a quarter. The triage guide is still the onboarding document two years later, which I did not expect.
Result
I joined in 2021 and support was quite chaotic at the time. We decided as a team that something had to change, so we all agreed to look at the process. I worked with the team to improve it and put better documentation in place. It went really well and everyone was much happier — it was a great learning experience for me.
What is missing
- No difficulty."Quite chaotic" gives the interviewer nothing to judge against.
- No ownership.Every sentence says "we". Nothing here is yours.
- No specific action."Improve the process" could describe any job anywhere.
- No result."It went well" is an opinion, not an outcome. The interviewer cannot repeat it to anyone.
Five ways it goes wrong.
Announcing the structure
Saying "so, the situation was…" makes an answer sound rehearsed and moves the interviewer's attention onto your technique. STAR is the order you think in, not a script you read out.
Front-loading the Situation
Half the answer spent on background, then thirty seconds on what you actually did. It is the single most common shape, and it is why interviewers start interrupting.
Saying "we" the whole way through
Modesty reads as evasion in an interview. Credit the team once, then describe your own work in the first person. If everything was collective, pick a different example.
Stopping at the Action
The answer ends when the work ends, and the interviewer is left holding effort with no outcome. Even "it did not work, and here is what I changed" is a Result.
A number nobody can check
"Improved efficiency by 300 percent" invites one question you cannot answer. An approximate figure you can defend beats an impressive one you cannot.
Practise one.
Pick a question, write one beat at a time, and read it back. The three things worth checking are the three the beats are about: is the situation short, is the task in the first person, and does the result carry a number or a change. Nothing here is uploaded, and nothing you write is kept.
Situation — two sentences, no more
Where you were, when, and what was going wrong. The interviewer needs enough to judge the difficulty and nothing else. If it runs past three sentences you are describing the company rather than the problem.
Task — the beat people skip
What was actually yours. Say "I". Skipping this makes a team achievement sound like a personal one, which is exactly what a good interviewer is listening for — and being caught at it costs more than the example was worth.
Action — half the answer, in order
Three or four steps, first person, in the order they happened. If you cannot say "I" without it sounding wrong, you are describing someone else’s work and should pick a different example.
Result — a number, or what stopped happening
If you have no number, say what stopped: the escalations, the weekend pages, the repeated question. An answer with no result is a description of effort.
- Tell me about a time you improved something nobody asked you to improve.
- The initiative question. The Task beat carries it: nobody assigned this, so say plainly what made it yours.
- Tell me about a time you disagreed with someone.
- The interviewer is listening for how the disagreement ended, not who was right. The Result beat is the working relationship afterwards.
- Tell me about a time you missed a deadline.
- A failure question wearing different clothes. The result is what you changed afterwards, and an honest one lands better than a rescued deadline.
- Tell me about a difficult person you had to work with.
- Describe the behaviour and not the character. "He was impossible" tells the interviewer about you; "reviews came back three days late and I needed them on Monday" tells them about the problem.
Tell me about a time you improved something nobody asked you to improve.
Two sentences. Where, when, and what was wrong.
What was yours. Say I.
Three or four steps, in order, in the first person. Half the answer.
A number, or what stopped happening.
Nothing here is uploaded. Closing the tab discards it — sign in if you want to keep an answer.
Nothing to check yet
Write at least the Situation and the Action, then press Check my answer. Each beat gets read separately.
Your saved answers
Answers are kept on your account. Sign in and the four beats you have written above can be saved and picked up before the interview.
Removing an answer is undoable for a few seconds.
When STAR does not fit.
It is for questions about something that happened. Forced onto one that is not behavioural, it answers the wrong question at length.
It cannot make an example you do not have
This is a way of ordering an answer, not a way of producing one. Rehearsing the order word for word is audible, and an interviewer who hears a script stops listening to the content.
Some interviewers do not ask behavioural questions at all
It is a tool for one common format, not a theory of interviews. Walking into a technical or case interview with four polished STAR answers is preparation for a different conversation.
| The question | STAR? | Use instead |
|---|---|---|
| "Tell me about a time when…" | Yes | This is exactly what it is for. |
| "How would you handle…" | Partly | Hypothetical. Answer the approach, then offer one real example as evidence. |
| "Why do you want this job?" | No | Motivation, not evidence. Two honest reasons, one about the work and one about you. |
| "Explain how X works" | No | Technical. Define it, give one example, name one trade-off. |
| "What is your greatest weakness?" | Partly | Name the real one, then use a short STAR to show what you have changed about it. |
Questions.
The five that come up every time this method is explained.
- Do I have to say the words Situation, Task, Action, Result?
- No, and it is better if you do not. Announcing the structure makes an answer sound rehearsed. STAR is the order you think in, not a script you read out.
- What if the result was bad?
- Say so, and say what you changed afterwards. An honest failure with a clear lesson interviews better than a vague success, and most candidates are not prepared to give one — which is exactly why it lands.
- How many examples should I prepare?
- Four or five that you can bend. One about fixing something, one about a disagreement, one about pressure, one about a mistake. Most behavioural questions are one of those wearing a different hat.
- Can I use an example from outside work?
- Yes, if the work part is thin — a volunteer role, a side project, a course group. Say plainly where it comes from. An interviewer minds an invented work example far more than an honest non-work one.
- Does ClearHire verify anything I say here?
- No. This page is a guide and the practice space is yours alone. What ClearHire can verify is separate: a named company countersigning a role you listed, which is a confirmation of employment and not a background check.
Keep going.
Verify the role
Ask the company in your example to countersign that you worked there.