By the time you're calling references, you've usually made up your mind. The candidate passed the interviews, the team is excited, and the reference call feels like a formality. That's exactly why most reference checks produce nothing useful.
The typical call goes like this: you ask if the candidate was good at their job, the reference says yes, you ask about weaknesses, the reference offers something harmless like "they care too much," and everyone hangs up feeling fine. You learned nothing. Here's how to change that.
Why Most Reference Checks Fail
Three forces work against you. First, selection bias: candidates hand you people who will say nice things. Second, social pressure: references don't want to hurt someone's job prospects, so they round everything up. Third, vague questions: "Was she a strong performer?" invites a yes, and a yes tells you almost nothing.
None of this means references are worthless. It means the standard script is worthless. The information you want exists; you just have to ask questions that make it easy to share.
Ask for Stories, Not Verdicts
A verdict question ("Was he a good engineer?") lets the reference stay abstract. A story question forces specifics. Instead of asking whether the candidate handled pressure well, try: "Tell me about a time the team was behind on a deadline. What did she do?"
Stories are harder to inflate than adjectives. If the reference struggles to come up with an example, that's information too. People remember specifics about colleagues who made a real impact; they speak in generalities about colleagues who didn't.
Replace "Weaknesses" With Conditions for Success
Nobody answers the weakness question honestly. It sounds like an invitation to torpedo the candidate, so references deflect. Reframe it as a setup question: "Every hire needs the right environment to do their best work. What kind of manager gets the most out of him? What situations bring out his worst?"
Now the reference isn't criticizing anyone. They're helping you set the candidate up to succeed, which is something they're happy to do. The answers are often remarkably candid: "He needs clear priorities or he'll chase five things at once" is a real insight you can act on, both in your decision and in onboarding.
Use Ranking Questions to Force a Real Answer
One of the most effective questions in a reference call is a forced comparison: "Of all the people you've seen in this role, where does she rank? Top five percent? Top quarter? Middle of the pack?"
References who would never volunteer criticism will still answer this honestly, because "top quarter" doesn't feel like an insult. But the difference between "honestly, top two or three I've ever worked with" and a polite "definitely above average" is enormous, and you'll hear it instantly. Enthusiasm is hard to fake and easy to detect.
Listen for What's Missing
The most important data in a reference call is often the gap between what you asked and what you got. If you ask about leadership and the reference talks about work ethic, note it. If you ask whether they'd hire the person again and there's a pause before the yes, note that too.
A useful follow-up when you sense hesitation: stay quiet. Silence is uncomfortable, and references will often fill it with the thing they were deciding whether to say. Don't rescue them with your next question too quickly.
The One Question That Cuts Through Everything
If you only have time for one question, make it this: "Would you hire this person again for the same role, and how quickly?" Then listen to the speed and texture of the answer.
"In a heartbeat, I tried to bring her with me to my current company" is a genuine signal. "Yes, I think so, depending on the role" is a soft no wearing polite clothing. Almost no reference will say the word no, but the distance between an enthusiastic yes and a qualified yes is where the truth lives.
Handle Backchannel References Carefully
Reaching out to people the candidate didn't list can surface honest perspectives, but do it thoughtfully. Never contact anyone at the candidate's current employer without explicit permission; you can cost someone their job. Be aware that any single unlisted reference may have their own agenda, so treat one negative voice as a prompt for more digging, not a verdict.
When you do get conflicting signals, bring them back to the candidate in a respectful way. "One person I spoke with felt your documentation could be stronger, what's your take?" A thoughtful response to criticism often tells you more than the criticism itself.
Make It Structured, Like Everything Else
You wouldn't run interviews without consistent questions, and reference checks deserve the same discipline. Decide in advance what open questions remain about the candidate, write three to five specific questions targeting those gaps, and use the same core set across references so you can compare answers.
Document what you hear right after the call, while tone and hesitation are still fresh. A week later, all you'll remember is "the references were fine," and fine is exactly the non-answer you were trying to escape.
The Bottom Line
Reference checks fail when they're treated as a box to tick after the real evaluation is done. Treated as a final structured interview, with story-based questions, forced rankings, and careful listening, they routinely surface things no interview can: how someone behaves over months, not minutes. That's the one thing your interview process, however good, can never observe directly.