InterviewKata
Behavioural interviews · Module 02 of 12 · Level 1: How it works

The STAR method

STAR is the shape almost every interviewer expects: situation, task, action, result. It isn't magic. It just puts your actions and their result where the interviewer is listening for them, and stops the context from eating the clock.

1. The idea

A good news report answers the same questions in the same order: what happened, to whom, what was done, and what came of it. Readers find what they need because the shape never changes. STAR does that for an interviewer: they know where to look for your actions and your result, so none of it gets lost.
  1. Situation: the context, in one or two sentences. Where, when, what was at stake.
  2. Task: what you were responsible for, and what made it hard.
  3. Action: what you did, step by step, with the reason for each choice. This is most of the answer.
  4. Result: what happened because of it, measured where you can, and why it mattered.

Many interviewers also listen for a fifth part, sometimes written STAR-L or STARR: the Learning, what you'd keep or change. It's a sentence or two, and it's where judgement shows.

PartShare of a 2-minute answerRoughly
Situation + Taskabout 20%25 seconds
Actionabout 60%70 seconds
Result + Learningabout 20%25 seconds

The split is a guide, not a law. What matters is that the action gets the most time and the result is never skipped. Amazon's own interview prep page tells candidates to use the STAR method (see Go deeper).

2. How it works

The same story told twice, against a two-minute clock. Watch where the seconds go, and what the interviewer is left with when time runs out.

3. Try it yourself

The STAR builder

Write one of your own stories in the four boxes (bullet points are fine). The meters show how long each part takes to say at a normal pace, and the checks flag the usual problems. Saved in this browser only.

    4. What interviewers look for

    STAR is a delivery skill, so the signals are about structure and balance. A strong answer could be transcribed straight into an interviewer's notes.

    SignalWeakGoodStrong
    StructureJumps around in time; the interviewer has to piece it togetherAll four parts, in orderAll four parts, with clear hand-offs ("So what I did was…", "The result was…")
    BalanceA minute of situation, ten seconds of actionAction is the longest partAction is about 60%, and each action has its reason
    ResultMissing, or "it went well"A result in wordsA number, plus what it meant for users or the business
    LengthOver 4 minutes, or under 45 seconds2–3 minutesAbout 2 minutes, leaving room for follow-ups
    LearningNoneA general lessonA specific change you made, or would make, next time

    5. A model answer

    "Tell me about a time you had to deliver something on a tight deadline." An invented answer, shown part by part. Read it for the shape, then build your own from a true story.

    SituationTwo weeks before a trade show, our sales team learned that the demo would need offline mode, which our field-inspection app didn't have.

    TaskI was the only mobile engineer free, and I had ten working days to make the three demo flows work without a network.

    ActionOn day one I listed every network call in those flows: 23 of them. Instead of building general offline support, I cached the read-only data the demo needed and queued the two write calls locally, because that covered all three flows in about a third of the work. I agreed with the sales lead which flows were in scope, in writing, so the target couldn't grow. I demoed progress every second day, which caught a sync bug on day six instead of at the show.

    ResultThe demo ran fully offline at the show, and sales credited it in two of the four deals that came out of it. The queue code became the starting point for real offline support the next quarter.

    LearningI'd write the scope agreement on day one rather than day two: one extra flow crept in during the first day.

    Why it scoresThe action is about 60% of the answer and every step carries a reason (why cache, why only two writes, why demo every second day). The result is concrete and ties back to the business. The learning is specific, not "communication is important".

    6. Remember it

    Memory hook: "Set the scene, then spend the time on what you did"A sentence or two of context, most of the answer on your actions and reasons, and never skip the result.
    How this hook works: what “Set the scene, then spend the time on what you did” means

    What the slogan means, phrase by phrase

    “Set the scene”
    Situation and task together in about 25 seconds: enough for the interviewer to follow, no more.
    “spend the time on what you did”
    The action is what gets scored. Give it about 60% of the answer, with a reason for each choice.
    “(and the result)”
    Close with what changed and, briefly, what you learned.

    Why this picture fits: A film trailer sets up the world in a few seconds and spends the rest on what the hero does. Nobody wants five minutes of establishing shots.

    The story → the concept

    The trailerYour answer
    Opening shot of the citySituation
    "One woman must…"Task
    The action sequencesAction, with reasons
    The final sceneResult
    The taglineLearning

    Watch it on an example

    1. A first draft spends 70 seconds on the project's history. The clock is at 1:10 and you haven't acted yet.
    2. Cut the history to two sentences: 20 seconds. The action now gets a minute, with three steps and their reasons.
    3. Add the result with a number, and one line of learning. Total: about two minutes.

    The trap it saves you from

    Running out of time before you reach the part that gets scored.

    It still works when…

    The question is unusual. Any "tell me about a time" question fits the same four parts.

    7. Common mistakes

    A minute of situationThe interviewer doesn't need the company's history. Two sentences of context, then move to your task.
    "We" in the actionThe action is where the score comes from, so it must be yours. Say "I" and give each step its reason.
    Stopping at the action"…and then we launched it." Always say what changed, with a number if you can find one.
    Reciting the lettersSaying "The situation was… the task was…" sounds rehearsed. Use the shape, with natural transitions.
    A ten-minute epicLong answers crowd out follow-ups, which is where strong candidates score most. Aim for about two minutes.

    8. Practice exercise (25 minutes)

    1. Pick a story (3 min). Choose a project from the last two years where you did something hard.
    2. Write it in the builder (10 min). Use the tool above. Bullets only. Get the action meter to be the longest one.
    3. Say it, timed (5 min). Record yourself. Stop the clock at two minutes and see where you were.
    4. Cut and repeat (7 min). Remove context until the action and result both fit inside two minutes. Say it again.

    9. Self-check quiz

    Which part of a STAR answer should take the most time?

    The action is what you did, so it's where the interviewer finds most of the evidence.

    Your result is "the launch went well". What's the best improvement?

    A measured result is easy to write down and shows impact.

    About how long should a STAR answer be before follow-ups?

    Long enough for all four parts, short enough to leave time for follow-ups.

    What does the L in STAR-L stand for?

    What you'd keep or change: a sentence or two that shows judgement.

    10. Go deeper

    ResourceTimeWhy
    SDE II interview prep (Amazon)10 minAmazon's own advice, including "Use the STAR method to frame your responses".
    Module 03: Building your story bankNextTurn one STAR story into answers for many questions.
    The question bankPracticeRun your STAR story against three different questions.