The STAR Method, With Examples

STAR is not a script. It is a check that a story about the past contains the four things an interviewer needs to credit it: where you were, what you owned, what you did and what changed.

The STAR method, sometimes called the STAR interview technique, is a way to answer any question that asks about something you have done: "tell me about a time", "give me an example of", "describe a situation where". Situation, Task, Action and Result are the four parts, told in that order.

Knowing the letters is the easy bit, and our guide to behavioural interview questions covers them. The hard bit is turning a real, messy experience into an answer that sounds like you rather than a template. That is what this page is for: three worked examples taken apart line by line, opening phrases for each part, a method for building an answer from scratch, and the questions where STAR is the wrong tool.

STAR method examples

Three answers to common questions, from three different stages of a career. Each takes under two minutes to say aloud.

Tell me about a time you disagreed with someone you were working with.

A graduate applicant, using a university project.

Situation: In my final year, four of us had six weeks to build a model predicting demand for a local bike-share scheme, worth a third of the module mark.
Task: I was responsible for the data cleaning, and another team member, Sam, owned the model. Two weeks in, we disagreed about whether to drop the winter months, which had a lot of missing readings.
Action: Rather than argue it in the group chat, I suggested we each run our version on the same test week and compare. I built both datasets that evening so neither of us had to wait. When mine came out slightly worse on accuracy but far better on the cold-weather weeks, I wrote up the trade-off in one paragraph and asked the others to decide, since it was Sam’s model.
Result: The group kept the winter data with a flag for missing readings. We scored 72, the highest in the cohort, and the tutor singled out the section explaining that choice. I have used the same "run both and compare" approach on every group project since.

Why it works: The disagreement is real but the story is about how it was settled. The action has three distinct steps, each with a reason, and the result gives a number, an outside judgement and a habit carried forward.

Describe a time you made a mistake at work.

An experienced hire, three years into a finance role.

Situation: Last spring I was preparing the monthly cost report that goes to our regional directors.
Task: The report was mine end to end, including checking the figures before it went out.
Action: An hour after sending it, I noticed one region’s travel costs were double-counted because a source file had been exported twice. I emailed the directors straight away with the corrected figure and a one-line explanation, before anyone had acted on it. Then I traced why my checks had missed it: I was reconciling totals, and the duplicate was inside a total that still looked plausible. I added a row-count check against the source system and wrote it into the team’s report checklist.
Result: Nobody made a decision on the wrong number, and the director of the affected region thanked me for flagging it so quickly. The row-count check has since caught two duplicate exports, one of them in a colleague’s report.

Why it works: It owns the mistake in the task line rather than burying it. The action covers detection, disclosure and the fix to the process, and the result shows the fix working beyond the original error.

Give me an example of dealing with a difficult customer.

An hourly retail applicant, using a weekend job.

Situation: On a busy Saturday at the garden centre where I work, a customer came to the till with a lawnmower he had bought the week before, which would not start, and no receipt.
Task: I was on the till alone for twenty minutes, and refunds without a receipt need a manager, who was on her break.
Action: He was raising his voice, so I moved him to the end of the counter so the queue could keep moving, and told him exactly what I could do: find the sale on our system with his card, and get the manager to him the moment she was back. I found the transaction in about two minutes using the last four digits of his card, printed it, and wrote a note for the manager with the fault he described so he would not have to explain it twice.
Result: The manager approved an exchange as soon as she returned, and he left with a working mower. The queue never stalled, and afterwards my manager asked me to show the others how to look up a sale by card.

Why it works: The constraint in the task line, no authority to refund, is what makes the action interesting. Each action solves a specific problem, and the result covers the customer, the queue and what the employer took from it.

Phrases that open each part

Situation: one or two sentences

"Last spring, in my role at...". "In my final year, I was...". "On a busy Saturday at...". Give a time, a place and the stakes, then stop. If you need a third sentence, the next part is probably starting.

Task: what was yours

"I was responsible for...". "My job was to...". "The part I owned was...". If you cannot finish one of these sentences, the story may not have enough of you in it.

Action: verbs, in order, with reasons

"The first thing I did was...". "I decided to... because...". "Then I...". The word "because" is where judgement shows, and judgement is usually what the question is after.

Result: what changed, and for whom

"As a result...". "The outcome was...". "Since then...". A number helps, but so does an outside judgement, a decision someone made because of you, or something you now do differently.

Building a STAR answer from scratch

1
Start from the result
Pick an outcome you can say in one sentence. If you cannot, the story is not finished enough to use yet. Working backwards from the result keeps the rest of the answer pointed at it.
2
Name what you owned
Write the task as your responsibility, not the team’s goal. "We had to launch on time" is a situation. "I had to get sign-off from legal by Friday" is a task.
3
List the actions as verbs
Three to five things you did, in order, each with the reason you did it. Cut anything someone else did unless your action was a response to it.
4
Trim the situation to what the actions need
Keep only the context a stranger needs to follow the actions. Internal team names, acronyms and the history of the project almost always go.
5
Say it aloud and record it
A written answer always reads shorter than it sounds. Recording yourself once shows where you hesitate, which part runs long, and whether the result actually lands before you trail off.

CAR, SOAR, PAR and STARL

Variants on the same idea. None is better than STAR in general; each suits a particular kind of question or time limit.

CAR: Context, Action, Result

Merges situation and task into a single opening. Useful when the question is narrow and the setting is obvious, or when a recorded interview gives you little time.

SOAR: Situation, Obstacle, Action, Result

Replaces the task with the obstacle. Works well for questions about difficulty, conflict or setbacks, where the problem is the point of the story.

PAR: Problem, Action, Result

The most compressed version. Good for a quick example inside a longer answer, such as backing up a claim in "tell me about yourself".

STARL: adding what you learned

A closing line on what you took from it. The competency interview guide explains where that line picks up marks.

For how a reflection line is credited, see competency-based interviews.

When STAR is the wrong shape

STAR answers one kind of question: what have you done. Interviews ask several other kinds.

"What would you do if..."

A hypothetical asks for your approach, not a story. Answer with the steps you would take and why, then, if you have one, add "I did something similar when..." as a short anchor.

"What energises you?"

Strengths questions are scored on how naturally you answer, and a rehearsed four-part story can read as the opposite. A short, specific, honest answer works better.

"Why do you want to work here?"

Motivation questions want reasons about the employer and the role. A STAR story about your past is an answer to a different question.

"Tell me about yourself"

This is a summary of where you are and where you are going. A single STAR story is too narrow, though a one-line result can back up a claim inside it.

Each has its own guide: strengths-based interviews, why do you want to work here and tell me about yourself.

STAR mistakes that are easy to miss

A task that repeats the situation

"The situation was a late project, and my task was to deal with the late project." If the task line adds nothing, you have lost the clearest statement of what was yours.

A story with no tension

If nothing could have gone wrong, there is nothing to credit. Choose examples with a constraint, a disagreement, a deadline or a risk, even if the stakes were small.

Stopping at the action

Candidates run out of steam after describing what they did and never say how it ended. If time is short, cut the situation, not the result.

Every story from the same setting

Five examples from one project make your experience look narrow and invite the question "anything else?". Spread your stories across study, work, volunteering and anything else you do.

Try a STAR answer on camera

Record answers to behavioural questions with a preparation window, and get AI feedback on structure, relevance and clarity before the real one.

See interview practice Sign up free

Frequently asked questions

What does STAR stand for?

Situation, Task, Action and Result: the setting, what you were responsible for, what you did, and what happened as a result.

How long should a STAR answer be?

Long enough for the result to land and short enough for follow-up questions. In a live interview that leaves room for probing; in a recorded one, plan to finish before the clock does, because nobody will ask you to continue.

Can a STAR example come from university or outside work?

Yes. Graduate and apprenticeship interviewers expect examples from study, part-time jobs, volunteering, sport and societies. What matters is that the story shows the behaviour, not where it happened.

What if I cannot think of an example in the interview?

Ask for a moment to think; a short pause reads better than a weak story. If nothing fits exactly, say so and offer the closest example you have, then explain how it relates.

Should every interview answer use STAR?

No. Use it for questions about something you have done. Hypothetical, motivational and strengths questions want a different shape, covered above.

Is the STAR method used in US interviews?

Yes. Behavioral interviews in the US use the same structure, and some employers name it outright: our Amazon interview guide covers one that does.

Preparing for Amazon? Read the Amazon interview preparation guide.