In a spoken behavioral answer, how should you budget airtime between the setup and the rest?

## The budget A spoken behavioral answer has a natural ceiling of about **two to three minutes**. Below that you sound thin; much above it and you are consuming a slot that usually has several more questions to fit. Within that ceiling the allocation matters more than the total: | Beat | Share of airtime | In practice | |---|---|---| | Setup — what was going wrong and why it mattered | about a fifth | roughly two sentences | | What you did, and the decisions inside it | the bulk | the part actually being scored | | How it ended, and what you took from it | a short close | one or two sentences | The number that does the work is the **setup cap**. Nobody rambles in the action beat; the failure is almost always front-loaded — narrating three years of org history before reaching the thing that was actually asked. ## Why the setup is the beat that overruns Setup feels free to the speaker and expensive to the listener. You lived it, so every fact seems load-bearing: the reorg that created the team, the two earlier attempts, the manager who left, the tooling that predated all of it. None of it is scored. The listener is trying to hold your context in working memory while waiting for a decision to evaluate, and each additional fact makes that harder, not easier. Setup is also where anxiety hides. Background is safe to narrate — it is factual, it needs no self-assessment, and it postpones the moment where you have to claim something. Candidates who are unsure which decision to lead with often stall in the setup without noticing. ## How to cut backstory to two sentences Apply one test to every sentence of context: **does the listener need this to understand a decision I am about to describe?** If the answer is no, it goes. That usually leaves exactly two sentences — one for the problem, one for why it mattered to someone outside the team. Worked example, platform domain, hiring manager asking: **Before (setup running past a minute):** > "So the platform group was formed when two teams merged, and the deployment tooling predated that, and there had been two earlier efforts to replace it, one before I joined and one that stalled, and ownership was split between us and the infrastructure group, which meant approvals went through a chain that..." **After (two sentences):** > "Releases on our platform could only be run by one person — me — so every team that depended on it queued behind my calendar. That was costing them days a month, and it was going to get worse as more teams onboarded." The second version drops the merger, both prior attempts and the approvals chain. If a prior attempt turns out to matter, it arrives *inside* the action beat, at the moment it explains a decision: "I knew a straight replacement had stalled before, so instead of rebuilding it I..." — one clause, doing real work, instead of a paragraph of foreshadowing. ## The elements that are almost never load-bearing - **Org structure and reporting lines**, unless the whole story is about crossing them. - **How the situation came to exist.** The listener needs the state, not the history. - **Names and team names.** "Another team" is enough; a roster costs airtime and gives no signal. - **Chronology of your own tenure.** When you joined rarely changes what the decision was worth. - **Prior attempts by other people**, unless you built on or deliberately avoided them. ## Rehearsing against the budget Time one delivery, once, with a clock — not repeatedly, because rehearsing to a script produces recitation that shatters on the first follow-up. You are checking two things: whether the total lands inside two to three minutes, and where the setup ends. If setup is still running at around forty seconds you do not have a length problem, you have a starting-point problem. Move the start later: begin at the moment the problem became yours to solve, and let anything earlier arrive only if a decision needs it. ## A budget is not a stopwatch The cap is a design constraint, not something to enforce out loud mid-answer. You never announce it and you never truncate a beat mid-sentence to hit it. A story built inside the budget lands there naturally; a story that consistently overruns is telling you it has the wrong scope, and the fix is choosing a narrower slice of the same experience rather than talking faster.