Most teams treat references as a formality. What to ask, who to call, and how to read between the lines.
At some point in the last decade, the reference check quietly died.
Nobody announced it. There was no memo. Companies just stopped doing them — or started treating them as a checkbox that gets ticked after the real decision has already been made. A five-minute call, three softball questions, a polite “thanks so much,” and then an offer goes out regardless of what was said.
Ask most hiring managers when they last learned something genuinely useful from a reference call. Watch them think for a while.
That silence is the problem.
A well-run reference check is one of the most underused tools in hiring. It can tell you how to manage the person you’re about to hire. It can surface things no interview ever would. It can confirm your conviction or quietly save you from a very expensive mistake.
Almost nobody is using it properly.
Why Did We Stop?
It didn’t happen for one reason. It happened for three, and none of them are as solid as people think.
The legal anxiety. There’s a pervasive belief that former employers can’t say anything beyond confirming dates and job titles — that anything more opens them up to liability. This has created a culture of silence around reference calls that isn’t really justified. People can speak to their experience working with someone. They can describe how someone operated, what they were like to manage, where they thrived. They just can’t defame. There’s a wide gap between those two things, and most references have plenty of room to be genuinely useful if the caller knows how to ask.
The time pressure. Hiring moves fast, especially at startups, and reference calls feel like friction. You’ve found your person, the team is excited, you want to get the offer out — why slow down now? The answer is that a 20-minute call can save you from a mis-hire that costs you six figures in salary, lost time, and team disruption. That’s not friction. That’s due diligence. Automated tools have made it easier to collect basic reference data quickly — async surveys, structured forms — but the signal that actually matters still comes from a real conversation. Logistics can be automated. Judgment can’t.
The belief that it’s all coached anyway. And sometimes it is. Candidates prepare their references. References know what to say. The calls are warm and positive and tell you nothing. But that’s a failure of the questions, not the format. A good caller can get real information out of even a cautious reference — because people are bad at hiding what they actually think when the questions are specific enough.
The reference check didn’t become useless. We just got lazy about running it.
The Formality Trap
Here’s the most common version of a reference check: the offer has already been extended in the hiring manager’s mind, the verbal is basically done, and someone on the team reaches out to the candidate’s references as a final step before paperwork.
The questions are generic. The call is short. The reference is glowing. Everyone moves on.
That is not a reference check. That is a confidence boost dressed up as process.
When you run references after the decision is already made, you’ve removed any possibility that what you learn will change anything. You’re not gathering evidence — you’re gathering comfort. And comfort is not what you need at this stage of a hire.
Run your references before the final decision. Treat them as part of the evaluation, not a footnote to it. If what you learn on a reference call makes you pause, you want that pause to happen before the offer goes out — not after the candidate has already given notice at their current job.
What You Can Actually Learn
This is where most hiring teams undersell the process — because when it’s done well, a reference call is remarkably informative.
In 20 minutes with the right person, you can find out how this candidate responds to pressure and what that looks like in practice. What kind of manager brings out their best work and what kind shuts them down. Where they genuinely excelled and where they needed support. Whether the story they told in your interviews matches the one their former manager tells. And perhaps most usefully — what you should know going in before you hire them.
You’re also getting a second source on the red flags that may have surfaced in your interviews — the vague ownership, the conflict they talked around, the project outcome that didn’t quite add up. A reference call is your chance to either clear those flags or confirm them. We covered the full list of what to watch for in Red Flags You Might Be Ignoring in Candidate Interviews — the reference call is where you find out if your instincts were right.
Who You Call Matters as Much as What You Ask
Every candidate submits references who will say good things about them. That’s expected. That’s the game. You have to play it differently.
Start by asking for specific references, not just whoever the candidate volunteers. You want the manager they reported to directly — not a peer, not a colleague from a different team, not a mentor they stayed in touch with. The direct manager. If the candidate pushes back on providing one, that’s information worth noting.
For the peer reference, ask for someone who worked alongside them on something difficult — a tough project, a stressful quarter, a situation where things didn’t go to plan. Easy circumstances don’t reveal much about anyone. Hard ones do.
For senior or executive hires, consider back-channel references — people you identify through mutual connections who know the candidate’s work but weren’t submitted as official references. Approach these conversations informally: you’re curious about their experience working with this person, not running a formal check. That framing matters. People are far more candid when a conversation feels like a professional exchange between peers than when it feels like an official deposition. These calls are often the most honest ones you’ll have.
The list a candidate sends you is the starting point, not the whole picture.
The Questions That Actually Work
Standard reference questions get standard reference answers.
“Was Jane a strong performer?” — “Yes, absolutely, one of the best.” “Would you hire her again?” — “In a heartbeat.” “What were her weaknesses?” — “She worked too hard, honestly. Cared too much.”
These answers tell you nothing. They’re reflexive, safe, and often rehearsed. The questions that get real answers are specific, situational, and leave room for nuance.
Here are five that work:
“Can you walk me through a time this person received difficult feedback — how did they take it and what happened next?” This surfaces self-awareness and coachability in a way that no direct question about those traits ever could.
“What kind of manager brought out their best work? What kind made things harder?” The answer to this is a management briefing you’re getting for free. Write it down. Use it.
“Is there anything about how they operate — their working style, their tendencies under pressure — that you’d want a new manager to know going in?” This is the most useful question on this list. It’s forward-looking, framed as helpful rather than critical, and it often produces the most honest answers.
“If you were building a team and this person was available, what role would you put them in — and is there a role you’d steer them away from?” This tells you where they genuinely shine versus where they’ve been placed by circumstance.
“Is there anything that would make you hesitate if you were considering hiring them today?” Then stop talking. The pause after this question is often more informative than the answer itself.
Reading Between the Lines
References rarely lie outright. What they do is omit, hedge, choose their words carefully, and answer the question they wished you’d asked rather than the one you did.
Learning to hear what isn’t being said is the skill that separates a useful reference call from a useless one.
Watch for enthusiasm that’s conspicuously absent on certain topics. If a reference speaks warmly and specifically about someone’s technical ability but gets noticeably vague when you ask about how they worked with the team — that’s a signal. It doesn’t mean disqualify. It means probe further.
Watch for praise that’s generic from someone who supposedly worked closely with the candidate. “She’s just a great person, really great” from a manager who spent two years with them in the same team is a strange response. A manager who genuinely rates someone can usually tell you specifically why.
Watch for the carefully worded positive. “He always met his targets” is a very different statement from “he was one of the strongest performers I’ve managed.” Both are technically complimentary. Only one of them is enthusiastic.
And watch for hesitation before specific questions. Not nervousness — hesitation. The micro-pause before they answer the difficult feedback question. The slight shift in tone when the topic turns to a particular project or period. Those moments are worth following up on, gently and directly.
The Reference Call as a Management Briefing
This is the angle almost nobody uses — and it might be the most valuable one.
You are about to hire this person. Someone on your team is going to manage them, give them feedback, set their direction, and work with them through good quarters and hard ones. The person on the other end of your reference call has already done that. They know things about this candidate that no interview will ever surface.
So ask them.
Ask what this person needs to do their best work. Ask what kind of feedback lands with them and what kind creates defensiveness. Ask what motivates them and what disengages them. Ask what a manager did that brought out the best in them and what one did that caused problems.
This is free onboarding intelligence. Most companies discover it slowly and expensively over the first six months of employment. A 20-minute call with someone who’s already been through it is a shortcut to all of that.
The best hires aren’t just the right candidates — they’re candidates you’re set up to manage well from day one. A reference check done properly is part of how you get there.
It’s Also a Networking Call
One more thing that almost never gets mentioned: the person on the other end of your reference call is a professional in your industry who has managed someone you’re about to hire.
That’s a relationship worth having.
Be genuinely curious. Be professional. Thank them meaningfully for their time — not as a pleasantry, but because they’ve actually given you something useful. Follow up if you said you would.
The recruiting world is smaller than it looks. People remember who ran a thoughtful process and who treated a reference call like a box-ticking exercise. The former builds a reputation that attracts better candidates over time. We covered this dynamic in the 48-hour rule in the context of candidate follow-up — the same principle applies here. The reference call is not outside your process. It is your process.
A Simple Framework You Can Use Tomorrow
You don’t need a complicated system. You need a consistent one.
Who to ask for: Request the direct manager from at least one recent role. Ask for a peer who worked alongside them on something challenging. For senior hires, supplement the submitted list with one back-channel reference identified through your own network — approached conversationally, not formally.
When to run it: Before the final decision. Not after the verbal offer. Before.
The five questions that work:
- Walk me through a time they received difficult feedback. How did they take it?
- What kind of manager brought out their best work?
- What would you want a new manager to know going in?
- If you were building a team, where would you put them — and what would you steer them away from?
- Is there anything that would make you hesitate? (Then stop talking.)
What to listen for: Specific praise versus generic praise. Hesitation on particular topics. What’s missing as much as what’s said. Any version of “she’s great, but…” — because what follows that comma is the whole call.
What to do with it: Write a one-paragraph summary per reference and share it with the hiring manager before the final decision. Flag anything worth addressing in onboarding. And if something significant surfaces — a pattern of behavior, a gap between what you heard and what the candidate told you — raise it directly with the candidate before the offer goes out. Frame it simply: “A reference mentioned X — can you give me some context?” Most of the time it opens a useful conversation. Occasionally it changes the outcome. Either way, you want that conversation happening before the offer, not six months into the role.
The reference check never became useless. We just stopped treating it like it mattered.
Run it properly and it will show you things no interview ever could — and set you up to make not just a better hire, but a better start to the working relationship.
Want help building a reference process that actually works — or figuring out what your current one is missing? Let’s talk.
