When interviewing one level above your current title, how do you choose which stories to lead with?

## The real question behind a stretch loop When you interview at a rung above your current title, the hiring manager is not asking whether you have already done the job. They are asking whether the evidence you do have predicts that you will. That reframing decides everything about story selection, because it means the goal is not to maximise apparent scope; it is to make the prediction easy and safe to make. ### Two things the next rung is made of Most candidates optimise only for **reach** — more teams, larger surface. But a rung is two things, and the second one is what a stretch candidate usually under-shows: - **Reach** — the work touched more people, and something you supplied was adopted past your own team. - **Depth of judgment** — the calls you made inside that reach were good ones, including the ones that cost you something visible. A candidate who brings only reach stories reads as someone who has been near large work. A candidate who brings only depth stories reads as excellent one rung down. The portfolio to bring is one strong reach story that survives a probe, plus one depth story where the decision had a cost you can name, plus one story about something that did not work and what you changed. ### Selecting the lead story Rank your candidate stories by *the widest claim whose evidence survives the first follow-up*, not by the widest claim you could make. The widest defensible one goes first, because the first story sets the frame the interviewer reads the rest through. If the widest defensible story is single-team project work, lead with it anyway and let its quality do the work; leading with an inflated claim that folds on *'who else used it?'* means the interviewer re-reads everything after it with suspicion. ### Trajectory as the honest frame When you are genuinely a rung short on reach, the strongest available frame is direction of travel. In an infrastructure world it sounds like this: > *'Two cycles ago I owned one service's build path. Last cycle I owned our team's whole move onto the shared pipeline, on a 6-month plan I proposed. The part that went beyond my team is the playbook and compatibility layer two other groups migrated with. The 18-month capacity plan is the thing I am closest to owning and have not owned end to end yet.'* That answer does three things at once: it shows growth in scope rather than a single spike, it makes a checkable multi-team claim without inflating it, and it names the boundary of the candidate's experience before the hiring manager has to find it. Naming your own ceiling is counterintuitive and it is usually the most credible sentence in the round. ### The tradeoff you actually own There is no universally right answer to how hard to push the claim, and this is the judgment the rung is testing. Push too hard and the failure mode is familiar — staff-level scope claimed on evidence that describes one well-run task — and it does not merely fail; it re-frames your earlier answers. Push too softly and you get placed accurately at the rung you already hold, which may be the correct outcome, or may be an outcome you could have moved with better-chosen evidence. The practical resolution: **let the claim be modest and the evidence be dense.** Density is what a hiring manager cannot manufacture on your behalf. Named adopters, a decision with a cost, an artefact that outlived you, a horizon you can describe in specifics — four of those inside one story move a calibration further than any adjective. ### On how the decision gets made Levelling practices vary a great deal between companies: some calibrate against a written internal ladder, some decide in a group discussion after the loop, some let the hiring manager decide alone, and the same title can carry different scope in two places. Because of that, treat the level a role is posted at as information about their ladder rather than a verdict on you, and treat a placement one rung below your target as a data point about the match rather than a judgment you must argue with in the room. What you control is the accuracy of the evidence you present; where their ladder puts it is theirs. ### What not to do with a stretch loop Do not borrow scope from work you supported rather than shaped. Do not present a team's outcome as a personal one because you were on the team. Do not answer questions about the higher rung hypothetically — *'at that level I would…'* — when you have a smaller real example available; a real, smaller fact beats a large hypothetical every time, because only one of them can be probed.