Career & Business
Should I make this hire?
Last reviewed 2026-06-23
Hiring feels like a decision about a person, but it's really a decision about your judgment — whether you're reading this candidate accurately or rationalizing a choice you've already made emotionally. The more senior the role, the higher the cost of being wrong, and the more likely the hiring process has been designed to make you feel certain when you're not.
You've met them several times. They interviewed well. The references sound strong. And something in you has already decided. The problem with that sequence is that each step has reinforced the prior one, and the confirmation bias you started with — you needed to fill this role — has been selecting for favorable information ever since the first conversation.
Hiring feels like a decision about a person. It's actually a decision about your own judgment, made under conditions specifically designed to impair it.
What makes this decision different
Hiring is unusual because the evaluation process is adversarial in a direction you don't always register. The candidate is presenting the most compelling version of themselves. Your own brain — relieved to have found someone good after a long search — is selecting for evidence that confirms the choice. References, who are typically pre-selected by the candidate, will give you the best version of the story. The conditions that would reveal a bad hire are largely absent: the ambiguous situations, the difficult conversations, the moments of poor judgment that only emerge under real pressure.
There's also a scarcity effect. A strong candidate who has other options creates urgency that functions as pressure. That urgency makes the question feel like "do I take this candidate?" rather than "does this candidate meet the bar for this role?" Those are different questions with potentially different answers.
What the role actually requires
Most hiring decisions fail not because the candidate was obviously wrong but because the hiring manager didn't have a precise enough model of what the role actually required. Job descriptions describe inputs — skills, experience, attributes. But the actual question is outputs: what specifically does this person need to produce in months six through eighteen to make this hire worth it? The candidate who can produce those things may or may not be the candidate who looked most impressive in the room.
The discipline of specifying outputs — not "strong communication skills" but "they need to be able to walk a hesitant enterprise client through a complex renewal negotiation and get to yes" — is both harder and more useful than the typical hiring process. It lets you ask whether the evidence you have actually predicts the specific thing you need.
The questions that actually matter
1. Can you articulate precisely what "the right hire" would produce in 12 months? Not character traits but specific outcomes. If you can't describe what success looks like in concrete terms, you can't evaluate whether the candidate you've selected is likely to produce it. This is both an evaluation tool and a forcing function — if you find you can't be specific, the problem is upstream of the hiring decision.
2. What specifically might you be rationalizing? Name the pressures that could be distorting your assessment. You've been searching for months. The team is stretched. The candidate is available. The previous search failed. These pressures are real, and they tilt evaluation. The discipline is to notice the tilt and ask whether the evidence would look the same to someone who didn't feel the pressure.
3. What would a rigorous no look like? Imagine you've decided not to hire this person. What's the case? Not "they might not work out" — that's true of everyone — but specifically: what are the conditions under which this person underperforms in this role, and what is the evidence that those conditions don't apply? If you struggle to construct the rigorous no, you haven't fully evaluated the candidate.
4. What do the reference calls actually reveal — and who hasn't called back? The references who respond promptly and positively are not the whole picture. Who didn't respond? What did the manager references say that was notably less specific than what you expected? The absence of information is information.
What a council surfaces that you won't
The internal experience of hiring with confidence is not distinguishable from the internal experience of rationalizing. Both feel like certainty. What a council can do is hold the alternative hypotheses — the ways this could be wrong — with the same seriousness that you're holding the case for yes.
Charlie Munger's inversion: what would you need to see in month nine to know this was a mistake, and can you test for that now? Daniel Kahneman's framing: which of your assessments are System 1 pattern-matching (they remind me of people who've worked out before, the interview felt right) and which are genuinely System 2 (structured, evidence-based, specific)? The ratio of those two things in most hiring decisions is not what people believe it to be.
What this decision is actually about
A hire is a bet on a prediction about another person's performance in a specific context. The prediction has two components: what this person is capable of, and whether this role and this environment will bring that out. Most hiring decisions evaluate the first component and assume the second. The second is where most bad hires actually live: the person was capable, but the role was wrong, the manager wasn't right, or the moment was off. Examining both components is what separates a good hiring decision from a confident one.
Pressure-test it with your council → Start a Decision Review
Counselors who can help
- Charlie MungerInversion — what would need to be true for this hire to be a mistake, and can you rule those conditions out with the evidence you have?
- Daniel KahnemanHow System 1 is doing most of the evaluative work and how to deliberately engage slower, more structured assessment before you close.
- Brené BrownWhether the discomfort of not hiring is doing work you're attributing to confidence in the candidate, and what the relationship dynamics actually require.
Frequently asked questions
How do I know if a candidate is genuinely the right fit vs. just impressive in interviews?
Interview performance and job performance measure different things. The interview is a performance event that rewards polish, narrative skill, and the ability to give good answers to anticipated questions. The job requires judgment in ambiguous situations, handling setbacks without an audience, and collaborating with people who won't be evaluating them. The strongest signal comes from work-sample assessments — asking the candidate to do something close to the actual job — and from conversations with references who have managed them, not just worked alongside them.
What does a bad hire actually cost in practice?
Research on the cost of a bad hire typically estimates 1–2 years of total compensation, but that figure understates the damage. The visible costs are salary, recruiting fees, and onboarding time. The invisible costs are what the wrong person in the role prevented: decisions that weren't made well, opportunities that were missed, team members who were frustrated or left. In a senior role, the invisible costs almost always exceed the visible ones. The relevant question is not "what does it cost to undo a bad hire?" but "what does this role touch, and how badly can a wrong person damage those things?"
How do I handle a hire when I've already decided emotionally?
The fact that you've already decided emotionally is itself diagnostic information. The strongest version of this decision — the one you can defend retrospectively — is not "I felt strongly about them." It's "I had a structured view of what this role required, I tested it rigorously, and the evidence pointed to this person." If you've already decided, the most useful exercise is to try to talk yourself out of the hire: what would need to be true for this to be a mistake in twelve months? If you can't generate a convincing case against, you may not have examined it closely enough.
What should I actually check in references?
Most reference calls are conducted badly. People ask open-ended positive questions and get positive answers. The calls worth having are with people who managed this candidate, not just worked with them, and the questions worth asking are specific: "In what situations did they struggle most? How did they handle it when they disagreed with a decision made above them? If you were building a team from scratch, would this person be on it, and in what role?" The silence after the last question is often more informative than the answer.
How do I evaluate culture fit without it being code for "people like me"?
"Culture fit" is one of the most abused concepts in hiring and one of the most reliable sources of bias. The question worth asking isn't "does this person feel like they belong here?" but "can this person operate well in the specific conditions of this team?" — including the pace, the ambiguity, the communication norms, and the kinds of problems that arise. The former is a gut reaction; the latter is a behavioral hypothesis you can test against evidence. The evidence is in how they've operated in similar conditions before, not in how comfortable they made you feel in the room.
Pressure-test this decision with your council.
This is a real council response to a common decision. Get one for the decision you're actually facing.