How should a 2-3 minute STAR answer split airtime across its four beats?

## The split, and why it exists A well-shaped answer to a "Tell me about a time you..." prompt runs two to three minutes and allocates its airtime roughly **10/10/60/20** across Situation, Task, Action and Result. Laid on a clock, for an answer that lands at 140 seconds: | Beat | Share | Clock | What has to be delivered in that time | |---|---|---|---| | Situation | ~10% | 0:00-0:14 | The system, the stakes, the moment it started to matter | | Task | ~10% | 0:14-0:28 | What you owned, and the constraint you were working against | | Action | ~60% | 0:28-1:52 | Options, the choice, the steps, in the first person | | Result | ~20% | 1:52-2:20 | What changed, how you knew, what you took from it | Treat these as proportions rather than targets to hit exactly. The load-bearing claim is only this: **Action is the majority of the answer, and the two setup beats together are a small opening slice.** A candidate who internalises that one relationship has most of the benefit; the specific percentages are a memory aid for it. The reason is what the beats do. Situation and Task are scaffolding - they exist so the Action beat can be understood and attributed. Result is a closing argument, short by nature because it is mostly one or two facts. Action is the only beat that contains evidence about how you think and work, which is the thing the conversation exists to find out. ## Why answers drift the other way Left alone, the split inverts. Context is the easiest thing to talk about: you know it cold, it requires no self-assessment, and it feels productive. Action requires you to make claims about your own judgment, which is uncomfortable, so people hurry it. The characteristic failure is a Situation that runs seventy seconds - half the answer - followed by an Action beat compressed into a single sentence, and then an apologetic Result. That shape is not just unbalanced; it is actively misread. A listener who has heard seventy seconds of system description and one sentence of "so I fixed the reconciliation step" cannot tell whether you did the interesting part or watched someone else do it. The interruption that follows is the one this material exists to prevent: **"So what did YOU actually do?"** ## The drill that fixes it Self-perception of time while speaking is unreliable, so measure instead of estimating. Record one answer, transcribe it with timestamps, and bracket each beat in the margin - [S], [T], [A], [R]. Then do the arithmetic: seconds per bracket, divided by total. The first transcript is usually startling. A typical first pass on an invented data-platform story: sixty-eight seconds bracketed [S], eleven seconds [T], thirty-one seconds [A], nine seconds [R]. That is an Action share of about a quarter when it should be around three-fifths, and no amount of resolving to "be more concise" fixes it, because the problem is not speed. The fix is deletion in a specific place: cut the architecture background that no later step depends on, and spend the recovered airtime naming decisions. Re-record, re-bracket, compare. Two or three iterations on one story is usually enough to recalibrate your internal clock for every story after it, because what you are learning is not the story - it is what fourteen seconds of context feels like from the inside. ## Pacing signals you can use live You cannot run a stopwatch mid-interview, so use landmarks instead. - **The forty-second check.** If you have not yet said what you personally did, you are over budget on setup. Land the responsibility sentence and move. - **The one-decision rule.** By the halfway point of your intended length, at least one decision of yours - with the alternative you rejected - should already be spoken. - **The exit line.** Have a prepared one-sentence Result so the ending does not sprawl. Ending cleanly at two minutes reads as control; trailing off at four reads as the opposite, whatever the content was. ## Where the split legitimately bends Proportions, not law. A few honest deviations: - **The prompt supplies the situation.** Shrink Situation to a sentence and give the time to Action. - **The story is about ambiguity, not execution.** Then framing *is* the action: the airtime moves into how you defined the problem, and that still counts as Action, not Situation. - **A short-form answer is requested.** Asked for the quick version, hold the ratio and shorten everything - roughly seven, seven, forty-two and fourteen seconds inside a seventy-second answer. Holding the ratio while shrinking is the skill; dropping beats is not. - **The interviewer interrupts.** Answer what was asked, then return to the beat you left. Interruptions eat setup time, not Action time - if you are pushed for time after one, compress the remaining context, not the evidence. What does not bend: Action being the majority, and the whole answer landing near two to three minutes unless you were asked for something else.