Answer interview questions with the STAR method

The most decisive interview questions usually start like this: "Give me an example of...", "Tell me about a time when...". These are behavioural questions: they measure what you actually did, not what you claim you would do. Caught unprepared, answers either stay vague ("I'd solve it with communication") or drown in detail.

STAR is a simple skeleton that builds the answer in four steps:

• S — Situation: Set the context in one or two sentences. Where, when, what was going on?
• T — Task: What was your responsibility? What was the goal or the difficulty?
• A — Action: What did you do? This is the heart of the answer — say "I", not "we".
• R — Result: What changed? Quantify if you can; if not, name an observable outcome. Adding what you learned earns bonus points.

Worked example: "How did you prioritise during a crunch?"

Situation: "At the end of last year, two major client deliveries landed in the same week and one person on the team was on leave." Task: "It was my job to get both deliveries out on time without burning out the team." Action: "I broke both projects down and isolated only what was strictly required for delivery. I called one client and agreed to push the secondary items by a week; I started a 15-minute daily check-in and took two work items on myself." Result: "Both deliveries shipped on time, and the postponed items were completed on the promised date. We kept the daily check-in afterwards because it visibly cut coordination overhead."

That answer takes 60–90 seconds and leaves a mark: clear context, actions that are yours, a real outcome.

Prepare stories, not answers

Instead of memorising a reply for every possible question, prepare five or six strong stories. Well-chosen stories adapt to many questions:

1. A hard problem you solved
2. A conflict or difficult stakeholder you managed
3. A mistake you made and what it taught you
4. A moment you prioritised under pressure
5. Something you built or improved from scratch
6. A time you led or helped someone

Sketch each story in STAR form in a few lines. Don't memorise word for word — sounding natural beats sounding fluent.

Common mistakes

• Drowning in the situation: Keep context to two sentences; the interviewer wants your decision, not the company's history.
• Telling "we" stories: Team wins are great, but the question was asked to you. Separate your own contribution.
• Skipping the result: An answer that ends at the action is half an answer. State the outcome, even a small one.
• Inventing: A polished true story always beats a perfect invented one; an experienced interviewer finds the seam with one detail question.

On the day

If the question isn't behavioural, don't force STAR — it's the skeleton for "give me an example", not a template for everything. A short closing link works well: "That experience maps directly onto the X responsibility in this role."

Before the interview, revisit our CV guide — that document is what the interviewer is holding, and stories consistent with it build trust.