Monday Intel N°5: A strong candidate is not a unanimous vote.

The debrief starts with a familiar split. One interviewer sees a builder who can move without a playbook. Another sees someone who has not operated at enough scale. A third wants stronger communication. The temptation is to run another interview until everyone feels comfortable. Before adding a round, ask whether the team is disagreeing about the candidate or about the job.

Name the job each person evaluated

A founding engineer and a specialist joining an established platform can both be excellent, but excellence looks different in each seat. If one interviewer rewards speed, another rewards mature process and a third expects deep expertise in every subsystem, the candidate may be getting measured against three incompatible mandates.

Write the next meaningful outcome the hire must own. Then ask each interviewer to connect their recommendation to that outcome. A concern that survives this exercise deserves attention. A concern that describes a different job deserves recalibration.

Sort the disagreement into three buckets

• Evidence: what the candidate actually said, built, explained or failed to explain. Capture the example, not just the adjective.
• Preference: a working style or background an interviewer likes. Explain whether it is essential to this mandate or simply familiar.
• Unknown: something the loop did not establish. Name the missing answer and the most direct way to get it.

This is not a trick for turning a no into a yes. A concrete failure to reason through a critical technical problem is not the same as a stylistic mismatch. Neither should be softened into a vague concern about fit. Precision protects the team and gives the candidate a fairer assessment.

Use another conversation only if it can change the decision

Suppose the open question is whether someone who has mostly built prototypes can own production reliability. Another general chat will not settle it. A focused walkthrough of a failure they handled, the monitoring they added and the tradeoffs they made might. Decide in advance what a sufficient answer would establish.

If nobody can name what the extra round would resolve, it is probably a request for reassurance rather than evidence. More conversations can make the process longer without making the decision clearer.

Keep a decision owner, not a popularity contest

The hiring owner should state the case for the hire, the strongest unresolved risk and how the team would support or test that risk after joining. Interviewers should be able to challenge that case. They do not all need to prefer the same background. They do need to understand the standard being used.

Do not lower the bar to get agreement. Make the bar clear enough that disagreement becomes useful.

This week’s move

At your next debrief, replace the first round of yes or no votes with three questions: What did we learn? What still matters that we do not know? Who owns the decision? If those answers are clear, the team can make a defensible call without pretending the hire carries no risk.