The STAR method, and when to use something else

Why a structure helps

When an interviewer says "Tell me about a time when...", they are asking for evidence. They have a list of what a good answer contains, and they are listening for it. A rambling story may contain all of it, but if the interviewer has to dig for the evidence, some of it will be missed.

A simple structure keeps you on track under pressure and makes the evidence easy to hear. The best known is STAR.

STAR, step by step

Spend most of your time on the action. The situation and task are there only to make the action make sense.

• Situation: set the scene in one or two sentences. Where were you, and what was going on?
• Task: what needed to be done, and what was your part in it?
• Action: what did you do, step by step? This is the heart of the answer and where most marks are.
• Result: what happened because of what you did? Use a number if you have an honest one, or describe the difference it made.

A worked example

Question: "Tell me about a time you dealt with a difficult customer."

Situation: "I was a shift supervisor in a busy café, and a regular customer complained loudly that his order had been wrong three times that week." Task: "It was my job to resolve it without holding up the queue." Action: "I asked a colleague to cover the till, took him to a quiet table and let him explain. I apologised, remade his order myself and found the cause: his usual order was being keyed under the wrong button. I fixed the till setting and told the team at the next handover." Result: "He came back the next day and thanked us, and we had no more complaints about wrong orders that month."

The mistakes that cost marks

Most weak STAR answers go wrong in the same few ways, and all of them are easy to fix with practice.

• Too much situation: two minutes of background leaves no time for what you did.
• "We" instead of "I": the panel can only credit what you did. Say "I" for your part and "we" for the team's.
• No result: the story stops at the action, and the interviewer never learns whether it worked.
• No reflection: saying what you learned, or would do differently, often earns the top mark.
• An example that is too small, or years old, when you have a better recent one.

Other shapes worth knowing

STAR is not the only structure, and for some questions a lighter one fits better.

• CAR (Challenge, Action, Result): the same idea in three steps, useful when the situation and task are really one thing.
• STARR: STAR with a final R for Reflection, which suits interviews that score learning and self-awareness.
• Present, past, future: for "Tell me about yourself". Say what you do now, how you got here and why this job is the next step.
• Point, reason, example: for opinion questions such as "What makes a good team?" State your view, explain it, then back it with a short example.

How long an answer should be

Aim for about one and a half to two minutes for a competency answer. That is long enough for a proper action and result, and short enough to keep the interviewer with you. If they want more, they will ask a follow-up question, and that is a good sign, not a bad one.

When you do not have a direct example

Say so honestly, then offer the closest thing you have: a similar situation from another job, from study, volunteering, sport or caring for a relative. Explain what you did and what carries across. If you have nothing close, describe what you would do and why. Interviewers respect a clear, honest answer far more than an invented story that falls apart under a follow-up question.

Practise out loud

Write the key points of six to eight stories, not full scripts, and say each one aloud until it takes under two minutes. Our guide to building a story bank shows how to choose stories that cover most of the questions you will be asked.