Rehearse is launching soon. Sign-ups open shortly.
Rehearse

The STAR method: how to answer interview questions, with examples

The STAR method is the simplest way to answer "Tell me about a time when…" questions clearly. Here's what each part means, how long to spend on it, and three full example answers you can adapt.

Updated 26 October 2026 · 6 min read

What is the STAR method?

STAR stands for Situation, Task, Action, Result. It's a structure for behavioural and competency-based questions, where the interviewer wants evidence of how you've behaved in the past, because that's the best predictor of how you'll behave in the job.

Without a structure, most people either ramble through the background or jump straight to the outcome. STAR keeps your answer in a logical order and makes sure you spend most of your time on the part interviewers score: what you did.

When to use the STAR method

Use STAR whenever a question asks for a real example. Listen for openings like:

  • "Tell me about a time when…"
  • "Give me an example of…"
  • "Describe a situation where…"
  • "Have you ever had to…?"
  • "What did you do when…?"

These questions are the core of competency-based interviews, graduate schemes, NHS interviews and Civil Service behaviour questions. Questions like "Why do you want this role?" or "Tell me about yourself" don't need STAR.

The four parts of a STAR answer

PartWhat to sayRough share
SituationThe context: where you were, what was going on and why it mattered. Just enough for a stranger to follow.About 15%
TaskWhat you personally were responsible for, or the goal you set out to achieve.About 10%
ActionThe specific steps you took, in order, using "I". Explain your choices and how you handled obstacles.About 60%
ResultWhat happened because of your actions, with a number if you have one, plus what you learned.About 15%

The Action is where you win or lose the question. If your Situation takes longer to tell than your Action, cut the background.

How long should a STAR answer be?

Aim for around two minutes, which is roughly 250 to 300 words when spoken. Under a minute usually means you've skipped the detail of your actions. Over three minutes and you'll lose the interviewer, who also has to take notes and score you.

STAR method examples

Three example answers to common questions. Notice how short the Situation is and how specific the Action is.

"Tell me about a time you solved a difficult problem."
SituationIn my last role, our weekly sales report took two analysts most of Monday to build by hand, and it often went out with errors that the regional managers then had to query.
TaskMy manager asked me to find a way to make the report reliable and free up the team's time.
ActionI started by mapping every step of the process and timing each one, which showed that most of the time went on copying data between three spreadsheets. I spoke to the regional managers to find out which figures they actually used, and cut the report from twelve tabs to four. Then I built an automated pull from our sales database with checks that flagged missing stores before the report was sent. I ran the old and new versions side by side for three weeks so the managers could trust the numbers before we switched over.
ResultPreparation time dropped from about a day and a half to under an hour, and queries from managers fell to almost none. The team used the time saved to start a monthly customer analysis, and I learned how much adoption depends on bringing people along, not just building the tool.
"Describe a time you worked under pressure."
SituationTwo weeks before a product launch, a key engineer on our team left unexpectedly, and the data migration they owned was only half finished.
TaskI was asked to take over the migration and make sure it was ready for launch day.
ActionOn my first day I went through their notes and listed every remaining task with an estimate, which showed we were about four days short. I took that to my manager straight away with two options: cut two low-value data sources, or bring in a contractor. We agreed to cut the sources and move them to a second phase. I then ran a fifteen-minute check-in each morning with the two people supporting me, so blockers surfaced the same day, and I tested each part of the migration as it finished rather than leaving testing to the end.
ResultThe migration was ready a day before launch with no data loss, and the two deferred sources were added three weeks later.
"Give an example of when you led without formal authority."
SituationOur marketing and finance teams were reporting different revenue figures to the leadership team, because each used its own definition of a sale.
TaskI wasn't senior to either team, but I offered to get everyone onto one agreed definition.
ActionI met each team separately first to understand why their definition mattered to them, rather than starting with a big meeting where people would defend their position. I then wrote a one-page comparison showing where the numbers differed and by how much, and proposed a single definition with a short list of exceptions. I brought both leads together to review it, made two changes they asked for, and agreed a date to switch over.
ResultBoth teams adopted the single definition the following quarter, and the leadership team now gets one revenue figure. Finance later asked me to run the same process for customer counts.

Common STAR mistakes to avoid

  • Too much Situation. The interviewer doesn't need the history of the company. Two or three sentences is enough.
  • Saying "we" all the way through. Teamwork is fine, but the interviewer is assessing you. Say "I" for the things you did.
  • No Result. Many answers just stop. Always finish with what changed, and a number if you can.
  • A vague, general answer. "I always communicate well" isn't an example. Pick one specific occasion.
  • The wrong example. Make sure the story actually shows what the question asks for. A leadership question needs you leading.
  • Reciting a script. Know your stories well, but say them naturally. A memorised answer sounds memorised.

STAR, STARR and CAR

You may see variations. STARR adds a final R for Reflection: what you learned or would do differently. It's a good habit, especially for questions about failure or mistakes. CAR (Challenge, Action, Result) is the same idea with the Situation and Task combined. They all lead to the same place: a clear, specific example where your actions are the focus.

How to prepare your STAR stories

  1. Go through your CV and list every project, achievement or tricky situation you can remember in detail.
  2. Pick your strongest five to eight that are recent, specific and show different strengths.
  3. Map them to themes such as leadership, problem solving, teamwork, delivering under pressure, influencing and handling conflict. One good story can often cover two themes.
  4. Write each one in STAR form in note form, not a script, and find a number for the Result where you can.
  5. Practise out loud. Time yourself, record it and listen back. It's the only way to know if it lands in two minutes.

Frequently asked questions

What does STAR stand for?

STAR stands for Situation, Task, Action and Result. You describe the situation, explain your task or responsibility, walk through the actions you personally took, and finish with the result.

How long should a STAR answer be?

Around two minutes, or roughly 250 to 300 words spoken. Spend most of that time on the Action, about 60 per cent, and keep the Situation and Task short.

Can I use the same STAR example twice in one interview?

Try not to. Interviewers want to see a range of evidence. Prepare five to eight different stories so you have a fresh one for each question, and only reuse one if it genuinely fits a different angle.

What if I don't have a work example?

Use an example from university, volunteering, a part-time job, a club or society, or a personal project. What matters is that it shows the skill being asked about and that you can describe your own actions in detail.

What is the STARR method?

STARR adds Reflection to the end of a STAR answer: what you learned, or what you'd do differently next time. It works especially well for questions about mistakes, failure or feedback.