How to run a reference check that actually tells you something
Most reference checks are confirmatory rituals: the candidate hands you the names of three people they've already prepped, you read off a script of softball questions, and an hour later your hiring decision feels marginally more legitimate without actually being more informed. The fix isn't to skip references — it's to ask questions that are hard to spin.
What a structured reference check looks like
- 15–25 minutes per call. Long enough to get past the safe answers, short enough that the reference doesn't feel held hostage.
- Audio only, scheduled. Don't email a survey. Phone or video gets you the pauses and hesitations that an email can't.
- Same questions across all references for the candidate. Comparable answers reveal patterns; bespoke questions invite bias.
- One open-ended “hard” question. The kind that's hard to spin: “Tell me about a time they got something wrong” gets you 10x what “Are they a hard worker?” does.
The questions that actually move a decision
References will almost never volunteer a red flag — but they'll often confirm one if you ask precisely. The two highest-signal questions in any reference check:
- “Where on the team did they rank?” — forces a comparison instead of a generic “great employee” answer.
- “Knowing what you know now, would you hire them again — and for what?” — the “and for what” is what unlocks honest scoping.
Probe the interview concern. If you had a specific worry from interviews (e.g., “weren't sure about handling ambiguity”), name it. References almost always confirm or deny precise concerns — they almost never raise them.
What to do with the answers
Write down quotes verbatim, not summaries. Then read across all 2–3 references and look for: (a) any factual claim made by the candidate that wasn't confirmed; (b) consistent patterns of the same strength or weakness; (c) any reference who hesitated, gave hedged language, or was conspicuously brief. Hesitation is data.