Interviews
The STAR Method for Interview Answers
STAR is a simple order for telling an interviewer about something you did: the situation, your task, the action you took and the result. This guide explains what belongs in each part, works through a complete answer and shows how to prepare stories without learning them by heart.
Key points
- Give the situation and the task in two or three sentences, then spend more than half of the answer on what you did.
- Say "I" for your own actions and credit the team separately, so the interviewer can tell what your part was.
- End every story with a result: a figure if you have one, otherwise what changed or what someone said.
- Write each story as four short lines of notes and practise it aloud instead of memorising sentences.
STAR stands for Situation, Task, Action, Result. It is an order for answering questions that begin "Tell me about a time when..." or "Give me an example of...". Those questions invite long, wandering stories, and the four parts keep yours short and make sure it reaches an ending.
It is a structure and not a recital. In a good answer the interviewer hears a clear story and never hears the four labels.
What each part is for
| Part | What it covers | How much of the answer |
|---|---|---|
| Situation | Where and when, with only as much background as a stranger needs | One or two sentences |
| Task | What you were responsible for, or the problem you had to solve | One sentence |
| Action | What you did, step by step, and why you chose to do it that way | More than half |
| Result | What changed, with a figure if there is one, and what you learned | Two or three sentences |
The usual imbalance is too much situation and too little action. Background feels safe to talk about, but the question was about what you did. If your story needs more than two sentences of scene-setting, look for a simpler story.
You may meet the same idea under other names, such as CAR (Context, Action, Result). The parts do the same work.
A worked example
The question is "Tell me about a time you improved a process." The candidate is Laila Haddad, a fictional accounts assistant. The labels are shown so that you can see the joins; she would not say them aloud.
Situation: Last year at Marrowby Building Supplies, supplier invoices were arriving by post, by email and through two site managers' inboxes, and about one in six was being paid late.
Task: I looked after the purchase ledger, so the late payments were mine to fix, and two suppliers had already put our account on stop.
Action: I started by logging every invoice for a month in a spreadsheet to see where the delays were. Most were sitting with site managers, waiting for approval. I set up one shared inbox for invoices and asked our six largest suppliers to send to it. I agreed with the operations manager that I could approve anything under 500 against the purchase order. For the rest, I sent each manager a single list every Tuesday instead of forwarding invoices one at a time.
Result: Within three months, late payments fell from about one in six to about one in forty. Both accounts came off stop, and we started taking an early settlement discount from one supplier. I now measure where a delay is before changing anything, because my first guess had been that the problem was the post.
Spoken at a normal pace, this takes about a minute and a half. The action section names four things she did and why, and the result includes a figure, a consequence and a lesson.
The same story, weak and strong
Weaker
We had a lot of problems with late invoices, so we changed the process and things got much better. It was a real team effort and everyone was happy with how it turned out.
Stronger
One in six supplier invoices was being paid late, and two suppliers had stopped our account. I logged a month of invoices, found that most were waiting for site managers to approve them, and set up one shared inbox and a weekly approval list. Three months later, late payments were down to about one in forty.
Why: The strong version says how big the problem was, uses "I" for what the speaker did and ends on a result that could be checked. The weak version could describe almost any workplace, and it never says what the speaker contributed.
Choose the right story
A story works when it is recent, when your own part in it is clear, when it has an ending, and when it shows something the job needs. Check the advert for the qualities the employer names, and pick stories that match them.
Not every result is a number. If you have no figure, use other evidence that something changed:
- What happened next: the method was adopted by another team, or is still in use.
- What someone said: a customer's email, or a manager's comment in a review.
- What stopped happening: complaints, rework, repeat calls.
- A before and after that you can describe, even roughly: "from most of a day to about an hour".
If you want help finding figures in your own work, the guide on how to quantify achievements lists places to look.
Say "I" for what you did
Most work is done in teams, and it is honest to say so. Give the team its credit in the situation ("I was one of four analysts on the project"), then use "I" for your own actions. An answer told entirely as "we" leaves the interviewer unable to tell whether you led the work or watched it.
The opposite fault is claiming everything. If a colleague had the idea and you carried it out, say that. Follow-up questions tend to find the edges of a story, and an accurate account holds up under them.
When the result was poor
Questions about mistakes and failures fit the same order. The result is then what went wrong, what you did to limit the damage and what you do differently now, and that last part is what makes the answer worth giving. The guide to behavioural interviews covers these questions, and questions about conflict, in more depth.
Prepare notes, not a script
For each story, write four short lines, one per part, in note form. Then tell it aloud two or three times, in different words each time. You are learning the facts and the order, not the sentences.
S: 2025, Marrowby. Invoices arriving three ways, 1 in 6 paid late.
T: Purchase ledger was mine. Two suppliers had stopped the account.
A: Logged a month of invoices. Delay was approvals. Shared inbox, approval limit of 500, one weekly list per manager.
R: Late payments down to 1 in 40 in three months. Accounts reopened. Settlement discount. Lesson: measure first.
The same action-and-result thinking produces good resume bullets, so a story prepared for an interview can be reused: the bullet point builder assembles a bullet from an action, a task and a result.
Expect follow-up questions
A STAR answer is often the start of a conversation. Be ready for "Why did you choose that approach?", "What did your manager think?" and "What would you do differently?". Keep some detail in reserve for these instead of putting everything into the first answer.
If you realise halfway through that you have chosen the wrong story, it is fine to say "A better example might be..." and switch. For the wider range of questions an interview can include, see common interview questions.
Common mistakes
- Spending most of the answer on background, so the time runs out before you reach what you did; keep the situation to a sentence or two.
- Saying "we" throughout, which hides your own contribution; describe your actions in the first person.
- Stopping at the action and never giving a result, which leaves the story without a point.
- Reciting the four labels aloud or delivering a memorised script, when the structure is meant to be invisible.
- Using a hypothetical ("I would usually...") when the question asked for a real occasion.
Questions and answers
How long should a STAR answer be?
About one and a half to two minutes is a sensible target. That is enough for a couple of sentences of context, a clear account of what you did and a result. Longer answers lose the listener, and the interviewer can always ask for more.
What if my example has no measurable result?
Use the evidence you do have: what changed, what someone said, or what happened afterwards. "The checklist is still used by the team two years later" is a result. Do not invent a figure, because you may be asked how it was measured.
Can I use examples from outside work?
Yes, especially early in a career. Study projects, volunteering, sport and caring responsibilities all produce real situations with real outcomes. Choose the example that best shows the quality being asked about, and prefer recent ones.
Is the STAR method only for behavioural questions?
It suits any question that asks for an example. For questions about opinions, motivation or technical knowledge it is less useful, although the habit of ending on a concrete result still helps.