Hiring-Manager and Bar-Raiser Rounds

## The round that is not sampling a skill Most slots in an onsite loop are *samples*. A coding round samples problem-solving under time pressure; a design round samples how you reason about a system you have never seen; a domain round samples depth in one area. Each produces an answer to a narrow question: did this person do the thing well, in this slot, today. The hiring-manager round is not a sample. The person running it is the one who will own the outcome of the decision — the headcount, the onboarding, the first year of your work, and the consequences if the hire is wrong. They are answering a different and much longer-horizon question: **do I want this person on this team, doing the work I actually have, at a rung I can defend?** ## The three things being gathered **Fit with the real work.** Teams advertise a role and then have a roadmap that is only partly that role. A manager is checking whether the work you are drawn to overlaps the work that genuinely exists — not because enthusiasm is charming, but because a mismatch predicts a departure that costs far more than a no-hire. **How you operate.** Ownership, disagreement, changing priorities, feedback. The manager is listening for the difference between what you *did* and what happened around you: what you decided, what you escalated, what you dropped, what you would do differently. A peer round rarely pushes past the outcome of a project; the manager usually does. **Level.** In a great many loops the manager is the person asked to state a rung and defend it. That defence is built from observed scope: what you owned versus influenced, over what span, with what blast radius, and how much ambiguity you absorbed before someone else resolved it. Vague ownership language does not read as modesty in a write-up; it reads as an absence of evidence, and absence pushes the recommendation down. ## It is written down, and it is not the only write-up The manager's round is scored like any other: a scorecard with what was asked, what the candidate said or did, a rating and a recommendation. What makes the manager's write-up distinctive is that it is usually the *advocacy* document — the one that argues for the hire and for the level. It is not, however, the only one that matters, and this is the part candidates most often misread. In loops that include a calibrating interviewer — the role commonly called a bar raiser, staffed from outside the hiring team — that interviewer files a separate scorecard weighted so it can block a hire the manager wants. An enthusiastic manager is the strongest advocate you can have and is still not the authority. Advocacy and veto are different powers, held by different people, recorded in different documents. ## An illustration A platform-infrastructure candidate sits a six-round onsite. Four rounds are technical, one is the manager, one is an engineer from an unrelated part of the organisation. In the manager's 45 minutes the shape is roughly eleven minutes on the arc of the last few years, twenty-six minutes inside one piece of work, and eight minutes at the end. The candidate, well prepared, tells the same migration story they gave the second technical round — same framing, same numbers, same ending. Nothing goes wrong in the room. The damage shows up in the debrief, where the scorecards are read side by side: the packet contains one project told twice and almost nothing about ownership, disagreement or what the candidate would repeat. The manager can advocate for the hire but cannot defend the posted rung, because their own write-up has no scope evidence in it. The calibrating interviewer's write-up, which had no team context to lean on either, says the same thing in colder language. ## What to do with this - Bring *different* material to the manager than you brought to the peer rounds. Their round is the one that most punishes recycled answers, because it is the one that most needs new observations. - State scope explicitly and unglamorously: what you owned, who else was involved, over what span, what you decided alone. - Talk about work that did not go well, including your own contribution to it. This is one of the few places where a polished peer-round story is visibly thin. - Expect direction questions, and answer them about the work rather than about the company. What kind of problems you want next is a legitimate, checkable answer. - Remember what the round produces: not a feeling, but a document that has to survive being read by people who were never in the room.