In a behavioral round, how do you scope a story's stakes to the seniority the role is posted at?
answer
- Bigger numbers are the wrong dial
- Reach, coordination, authority, horizon
- Who else was in that decision?
- Under-scoping is the quiet failure
- Crises constrain individual authority
basics
~20 sChoose examples whose blast radius, coordination load and decision authority match the posted rung. A story where you executed one task well underscores a senior role; a story claiming a group's decision as yours overreaches and invites probing.
solid answer
~50 sI calibrate on four dimensions rather than on how impressive the situation sounds: how far the consequences reached, how many people or teams I had to move, whether the decision was mine or escalated, and how far ahead it had to hold. For a senior infrastructure role I look for examples where I set direction across more than one team, made the call when nobody else would, and dealt with organisational resistance as well as technical difficulty. Below the rung, the listener hears a competent contributor and cannot justify the level. Above it, the follow-ups get sharp fast — 'who else was in that decision?' — and being unable to answer costs more than the modest story would have. The safer error is a true story at honest scope, told with the ownership clearly demarcated.
go deeper
Be ready to describe a choice inside your own task and to say when you escalated. Escalating at the right moment is a positive signal at this stage, so do not dress up a decision as more independent than it was.
Explain how you owned a piece of work end to end and coordinated with people outside your immediate group. Show that circumstances changed and you adjusted without waiting to be re-directed.
Demonstrate direction-setting beyond your own hands: someone disagreed, you drove a resolution, and the consequences reached other teams. Be ready to name who else was involved and what they wanted instead.
Own the trade-off between an example that shows the widest reach and one that shows the cleanest decision. Where you changed how a class of decisions gets made, be prepared to defend why that mattered more than the outcome of any single call.
## What 'stakes' actually means here Candidates hear 'match the stakes to the level' and reach for bigger numbers. That is the wrong dial. A behavioral interviewer calibrating seniority is reading four things, and none of them is the size of the incident. **Blast radius.** How far did the consequences of the decision reach — your own task, one service, a shared platform, several teams' roadmaps? **Coordination load.** How many people had to be moved, and did they report to you? Persuading peers and adjacent teams without authority is the expensive version and scores higher than directing a team that already had to comply. **Decision authority.** Was the call yours, or did you surface options and someone else chose? This is the dimension candidates most often blur, and it is the one the follow-ups probe hardest. **Time horizon.** Did the decision have to hold for the length of an incident, a quarter, or several planning cycles? ## A rough ladder Stated as what a story typically has to contain to be *sufficient* at each rung. Every rung still needs a contested decision; what changes is its reach. - **Entry level.** You owned a task or a component, made a reasoned choice within it, and escalated appropriately when the choice exceeded you. Escalating well is a positive signal here, not a gap. - **Mid level.** You owned a workstream end to end, coordinated with a small number of people outside your immediate group, and absorbed a change of circumstances without needing to be re-directed. - **Senior.** You set direction for work beyond your own hands, made the call when the group was stuck, and handled resistance that was organisational as much as technical. The story typically contains someone who disagreed and a resolution you drove. - **Principal and above.** You changed how a class of decisions gets made — a standard, an ownership boundary, a way of evaluating options — and the effect outlived your involvement. ## Under-scoping and over-scoping **Under-scoping** is the quieter failure and the more common one among strong candidates. Someone interviewing for a senior infrastructure role tells a clean, well-structured story about a decision entirely inside their own component. Nothing in it is wrong. The listener has no evidence for the rung and writes 'solid, but I saw mid-level scope' — a verdict that is very hard to reverse later in the loop, because the panel is calibrating against each other's notes as they go. **Over-scoping** is louder and more expensive when caught. A candidate describes a multi-team programme in the first person, and then a behavioral interviewer asks 'who else was in that decision?' or 'what did the other teams' leads want instead?' If the honest answer is that a director set the direction and the candidate implemented a portion, the correction lands as a credibility problem rather than a scope problem, and credibility damage generalises to the rest of the answers. The asymmetry means the safer error is honest scope with sharply demarcated ownership: say plainly what was yours, what was the group's, and what you inherited. Precise ownership at modest scope reads as senior far more reliably than vague ownership at large scope. ## The drama trap at senior level This is where reaching for the most dramatic story does its worst damage, because drama and seniority signal in opposite directions. Large incidents are exactly the situations where the response is proceduralised and individual authority is deliberately narrowed: the incident commander runs the call, everyone else executes. A candidate who tells the biggest outage they were part of usually ends up evidencing *followership at scale* while attempting to evidence leadership. The senior-scope material is usually somewhere far less exciting — the quarter spent getting three teams to agree on who owned a shared dependency, or the decision to stop a migration that everyone had already committed to. No sirens, but the blast radius, coordination load, decision authority and time horizon are all visibly at the rung. ## Calibrating before the loop For each recurring theme, take your intended example and score it on the four dimensions against the posted rung. Where an example sits a rung low, check whether a wider version exists — often the same work had a coordination layer you cut out of the story because it felt like preamble, and that layer is precisely the evidence. Where an example sits a rung high, decide in advance exactly which sentence marks the boundary of your own contribution, and rehearse saying it, so the boundary comes from you rather than from a follow-up. Doing this in advance is what lets you answer 'who else was in that decision?' without flinching.
- Who else was in that decision, and what did they want instead?The platform lead and the two teams consuming the storage tier were in it. The consuming teams wanted to wait for a full read-path reconstruction; the platform lead was neutral but owned the maintenance window. I argued for cutting over inside the window with declared rollback conditions, and carried it by agreeing to own the reversal personally. The final call was mine because the window was assigned to me, and I would say so the same way if it had gone badly.
- Your example sits below the level we are hiring at. Do you have something wider?Yes — and I would rather widen the same work than swap it. The coordination layer I skipped is the evidence: getting three teams to agree who owned a shared dependency before the migration could start took most of the effort, and I cut it because it felt like preamble. Told from there, the blast radius and the persuasion load are visible, and the technical decision becomes the last third rather than the whole answer.
- Is it ever better to tell a story at honest scope than to reach for a larger one?Almost always, because the errors are asymmetric. A modest story with sharply demarcated ownership reads as calibrated; an oversized one collapses the moment a probe reaches the boundary, and the damage spreads to every other answer in the round. I would rather say plainly what was mine, what was the group's, and what I inherited, and let the reach speak for itself.
saying these in an interview costs you the question
- Reaching for the biggest incident when the candidate's role was executing a plan
- Blurring a group's decision into first-person singular throughout
- Telling a solo-task story when interviewing for a role that leads others
- Equating a large number of affected users with senior-level judgment
- Being unable to say who else was in the room when asked