Hire this senior candidate
After the loop, before the offer.
Senior hiring is where anchoring does the most damage. The first interviewer to speak in the debrief — usually the most senior or most enthusiastic — sets the tone, and quieter dissent never surfaces until the hire underperforms six months later. Collecting each interviewer's verdict privately, with the signal that drove it, is the entire point of running the debrief async.
Should we extend an offer to this candidate for the role?
Each interviewer share: strongest signal (verbatim if possible), strongest concern, and what would change your mind. State explicitly whether your vote is independent of compensation — those are different decisions.
What each contributor weighs
Ask everyone to put these on the table privately, before they see another contributor's position.
- Your single strongest positive signal, quoted verbatim from the interview if you can.
- Your single strongest concern, and whether it is a dealbreaker or a coachable gap.
- What specifically would change your recommendation.
- Whether your yes/no is independent of the compensation ask — those are two different decisions.
- Director-level+ hires
- Critical first hire in a function
- Replacing a departing lead
How this decision usually goes wrong
- Halo effect — one impressive credential or company name carrying the whole loop.
- Consensus theater in the debrief, where nobody contradicts the hiring manager.
- Conflating 'I liked them' with 'they can do this specific job'.
- Letting comp-negotiation pressure leak into the competence decision.
How to run this decision in 48 hours
- Open a room seeded with the question above. Set a 48-hour deadline.
- Paste the opening context — keep it short. Engineers will not read more than 300 words.
- Invite by email. Each contributor submits position + reasoning + risks privately, before seeing anyone else.
- Read the synthesis. Claude maps consensus, dissent, blind spots, and confidence.
- Decide and log. The synthesis is the decision-log entry — no separate write-up.
A synthesis that shows whether the yes is unanimous or one loud vote, isolates the concern at least one interviewer was afraid to raise out loud, and keeps the hire/no-hire call separate from the offer-level call.
Related reading
- Anchoring bias in engineering decisions: what it is and how to defeat it
- Why every distributed engineering team needs a decision log