The STAR method, with a worked answer

What the STAR method is

STAR is a way to answer behavioural questions, the ones that start with “Tell me about a time…” or “Give an example of…”. The interviewer wants evidence of how you actually work, and STAR gives that evidence a shape:

• Situation: where you were and what was going on, in one or two sentences.
• Task: what you were responsible for, or the problem you had to solve.
• Action: what you did, step by step. This is the part that gets you hired.
• Result: what changed because of it, and what you learned.

The order matters less than the balance. Most weak answers spend a minute on the situation and ten seconds on what the candidate did.

Spend most of your answer on the action

A good rule of thumb: a sentence or two for the situation and task, most of the answer on your actions, and a clear finish on the result. Two minutes is plenty for one answer.

A worked answer, start to finish

Question: “Tell me about a time you used data to change a decision.”

Situation. At my last internship, the operations team believed late deliveries were spread evenly across the city.

Task. I was asked to look at a month of delivery-time data and say where the problem really was.

Action. I cleaned the order data in SQL, grouped late orders by zone and hour, and found that a handful of zones accounted for most of the delays, mostly in the evening. I checked the pattern held across all four weeks so it wasn’t a one-off, then built a simple dashboard so the team could see it for themselves.

Result. The team moved two evening riders into those zones for a trial. I learned that a clear chart persuaded people faster than a long report.

Notice what it doesn’t do: it doesn’t claim a big number it can’t back up. If you have a real figure, use it. If you don’t, describe the change honestly. An interviewer will ask follow-up questions, and an invented number falls apart under the first one.

Build a small bank of stories

You don’t need a new story for every question. Five or six good ones, each told flexibly, cover most behavioural interviews:

• A time you solved a hard problem, technical or not.
• A time you disagreed with someone and how it was resolved.
• A time something went wrong and what you did about it.
• A time you learned something quickly.
• A time you led or influenced others without being in charge.
• Your proudest piece of work, with the result.

Draw them from your resume. Every bullet that describes something you did is a STAR story waiting to be told, and the interviewer may ask about any of them.

Common mistakes

Choosing a story with no result. If the project was cancelled, say what you learned and what you would do differently. That still counts as a result.

Making it a team story. Interviewers are hiring you, not your team. Credit others, then be specific about your own part.

Memorising a script. Know the four beats of each story, not the exact words. A recited answer sounds recited, and it breaks when the question is worded differently.

Picking the wrong example. Read the question for what it’s really testing, such as conflict, ownership or learning, and choose the story that shows that quality best.