Most hiring teams treat the reference check as the last box to tick before an offer goes out. A recruiter books a fifteen minute call, asks whether the candidate was reliable, hears that yes, they were wonderful, and marks the stage complete.
That call cost you fifteen minutes and told you nothing.
Reference checks are not useless. The way most teams run them is. A well run reference conversation is the only part of your process where you hear from someone who watched the candidate work for a year or more. No interview loop can replicate that. The problem is that the standard script is built to produce comfortable answers.
Why the usual questions produce nothing
"Would you hire them again?" invites a yes. "What are their weaknesses?" invites a rehearsed line about perfectionism. "How would you rate their communication on a scale of one to ten?" invites an eight.
These questions share a flaw. They ask the reference to summarize and judge, which is exactly the task most people avoid when speaking on the record about a former colleague. References feel a duty of loyalty, they worry about legal exposure, and they do not know you well enough to risk candor.
So they hand you the safest possible version. You then read the absence of red flags as a green light.
Ask for episodes, not evaluations
The fix is to stop asking for judgments and start asking for specific events. People are far more willing to describe something that happened than to render a verdict on a person.
Instead of "was she a strong project manager," try "walk me through the most complicated project she ran while you worked together, and tell me what went wrong on it." The reference is now narrating rather than grading. Details surface that no rating scale would reach.
This mirrors what good behavioral interviewing does with candidates. You want evidence, not adjectives.
Anchor every question in the job you are filling
Before the call, pick the two or three things this hire has to do well in the first year. Build your questions around those specifics.
If the role means leading a team through ambiguity, ask: "Tell me about a time priorities changed underneath him. How did his team find out, and how did they react?" If the role requires influence without authority, ask who on the reference's team was hardest to win over and how the candidate handled it.
Generic questions get generic answers because you gave the reference nothing to aim at. Specific questions give them permission to be specific back.
Six questions worth stealing
A handful of prompts reliably produce real information:
- "What did she need from a manager to do her best work?" Surfaces working style without asking anyone to criticize.
- "If you were building that team again, what role would you put him in, and what role would you avoid?" Gets you fit information framed as a compliment.
- "What was the hardest feedback you ever gave her, and what happened after?" Coachability lives in the second half of that answer.
- "Who else there worked with him closely?" You are looking for the people the candidate did not put on the list.
- "What was she like during the worst week of that project?" Composure under pressure is hard to fake and hard for a reference to embellish.
- "What did the team lose when he left?" You learn what the person was actually doing, which is often not what the resume says.
None of these ask for a rating. That is the point.
Go past the list the candidate handed you
Candidates give you three people who like them. That is rational, and you should expect it. Treat the list as a starting point rather than the whole exercise.
The most useful move on any reference call is asking who else worked closely with the candidate, then requesting an introduction. References you reach this way tend to be more balanced, because the person did not volunteer for the job of advocate.
Be careful here. Contacting a current employer without permission can cost someone their job, and rules on what employers may disclose vary by state and country. Ask the candidate who is off limits, and honor it without argument.
Let the hiring manager make the call
Recruiters run good process. Hiring managers hear things recruiters do not.
When a former manager talks to the person who will manage this candidate next, the conversation shifts from verification to handoff. References open up considerably when the framing is "help me set this person up to succeed" instead of "confirm the following facts."
That framing is also honest. If the offer is going out, the most valuable thing you can walk away with is an operating manual for the person you just hired.
Write it down somewhere it will actually be used
Most reference notes get pasted into an applicant tracking system and never opened again. That wastes the one input you gathered from someone who watched a full year of performance.
Pull the two or three concrete things you learned about how this person works best, and hand them to the hiring manager for the first thirty days. If a reference mentioned that the candidate goes quiet when overloaded rather than flagging it, a new manager should know that in week one, not discover it in month four.
When a reference check should change your decision
Reference checks rarely produce a clean no. What they produce is a pattern that either confirms or contradicts what your panel saw.
If three people independently describe the same friction and your interviewers noticed something adjacent, that is a signal worth acting on. If one person is lukewarm while everyone else is specific and enthusiastic, you have probably found an old conflict rather than a performance problem.
The goal is not to catch anyone out. The goal is to reach the offer with an accurate picture of the person instead of a flattering one, and to know on day one where they will need support.