The candidate hands over three references they've already prepped. HR runs through generic questions. The references give generic answers. The result confirms what the company already believed. The reference check has produced approximately zero new information, and the company moves to offer.

This is a waste of a high-leverage step. Done well, reference checks are one of the highest-signal parts of hiring. They can surface things the interview process missed. They can confirm or invalidate gut feelings the team had but couldn't articulate. They can flag concerns before they become hiring mistakes.

This article gives you the reference check template and the questions that actually surface useful information.

Why most reference checks fail

Three reasons.

The wrong people are doing them. Reference checks delegated to HR (or worse, to junior recruiters) miss most of the signal. The hiring leader should personally do reference calls for any role above a certain seniority, definitely for senior hires.

The wrong questions get asked. "Tell me about [candidate]'s strengths and weaknesses" gets you the rehearsed answer. The candidate prepped the reference for that. You have to ask differently.

The references are too curated. The references the candidate provides will mostly say good things. That's why they're the references. You need to also reach references the candidate didn't pick, where possible.

Fix these three things and your reference checks start producing real signal.

When to do reference checks

A few rules.

For senior hires (manager and above): every time. Always. Even if you're certain. The compounding cost of a bad senior hire makes the 90 minutes of reference checks the highest-ROI time you'll spend.

For non-senior hires: at least one or two checks. Even a 30-minute call with one strong reference is more signal than no reference check at all.

Always done after the team has agreed they want to make an offer, but before the offer is sent. Reference checks are confirmatory, not the basis for the initial decision. You're verifying what you believe, not learning the basics.

Done by the hiring leader, not delegated. Especially for senior hires. The hiring leader should know what they're looking for, what concerns the team has, and what questions to push on. Delegated reference checks lose most of the value.

How to set up the reference check

Before the call, do three things.

Ask the candidate for specific references. Not "three people who can speak to your work." Specific: "We'd like to talk to someone who managed you in the last role, a peer from the same period, and a direct report if you've managed people."

Ask the candidate to introduce you. A warm email introduction makes the reference much more likely to take the call and to be candid.

Identify the questions you most want answered, based on the interview process. What concerns did the team have? What competencies are you least confident about? Reference checks should probe the gaps in your assessment, not duplicate it.

If you can also reach references the candidate didn't list (former colleagues you know through your network, mutual contacts), do that. Those calls are typically the highest signal.

The reference check template

The structure to use. The whole call should run 30-45 minutes.

1. Opening (3 minutes)

Set the tone.

"Thanks so much for taking the time. I'm hiring [Candidate] for [Role], and we're in the final stages. I'd love your honest perspective. Everything you share will be confidential, and I'll be direct about any concerns the team had so you can address them. Mind if we just dive in?"

Two things to do here: signal that you want honest input (not a recommendation letter), and offer reciprocal directness about your team's questions.

2. Context (5 minutes)

Understand the reference's relationship to the candidate.

How do you know [Candidate]? How long did you work together?
What was the working relationship? (Manager, peer, direct report)
What was [Candidate]'s role during that time?

Don't skip this. The same answer means different things from a manager versus a peer versus a direct report.

3. Core questions (25-30 minutes)

This is the meat of the call. Below are the questions that actually surface signal. Pick 4-6 based on what you most want to learn.

On work and impact

Walk me through what [Candidate] actually owned during that period. What did they specifically do?
What's an accomplishment of theirs that you'd consider impressive?
Where did they have the biggest impact on the team or organization?

What you're testing: whether the candidate's claims line up with what the reference saw. If the candidate said they led X and the reference says X was mostly someone else's project, that's signal.

On growth and learning

What were they working on developing while you worked together?
Where did they grow the most during that time?
What kind of feedback did you give them, and how did they take it?

What you're testing: coachability and self-awareness. A reference who can describe specific feedback the candidate received and what they did with it is more credible than one who says "they were always great."

On working with others

How did they handle disagreement? Tell me about a specific time you saw that.
How did the team respond to working with them?
Were there any working styles they struggled with?

What you're testing: collaboration and interpersonal effectiveness. The third question often surfaces the most. "They worked great with everyone" is rarely true and often signals the reference isn't being candid.

On the hard questions

What's the constructive feedback you'd give them if they were sitting here?
If you were hiring them, what would you want to know about their development areas?
On a scale of 1-10, how strongly would you recommend hiring them? Why not a 10?

The first two are reframings of "what are their weaknesses" that produce better answers. The third one is a forcing function: any rating below an 8 deserves follow-up.

On the team's specific concerns

If your team had specific concerns during interviews, surface them directly.

"One thing I want to ask about: in our interviews, we got the sense that [specific concern]. Did you see anything that would speak to that?"

This is the most powerful question in a reference check. It tests both the candidate's reference (will they cover) and the reference's honesty.

The closing question

Would you hire them again? Under what circumstances?

A reference who would unambiguously hire the candidate again is the strongest signal. A reference who hedges ("well, it would depend on the role") is interesting and worth following up on. A reference who says "probably not" or "I wouldn't" is a critical data point.

4. Wrap-up (3 minutes)

Is there anything else you think I should know that I haven't asked about?
Thanks, and would you mind if I reach back out if anything else comes up?

Always ask the open question at the end. References often save the most important thing for last, after they've built comfort with you.

Reading the signal

A few patterns to watch for.

Hedging and softening. A reference who softens every statement ("they're really hardworking, but...", "they're great at X, although...") is signaling something. Listen carefully to what comes after the "but."

Specific examples vs generalities. A reference who can give specific stories about the candidate is more credible than one who speaks in generalities. Vague positivity often means the reference doesn't know the candidate well, or doesn't want to be candid.

What they don't say. If you ask "tell me about a time the candidate handled a conflict well," and the reference can't think of an example, that's signal. Strong candidates have examples. Weak ones don't.

Energy shifts. When you ask a probing question and the reference's tone changes, pay attention. The shift is usually telling you something the words aren't.

Volunteered concerns. If a reference brings up a concern unprompted, take it seriously. Even if they're hedging on it. They're signaling that they wanted you to know.

Off-list references

For senior hires, the most valuable references are often ones the candidate didn't list.

How to find them:

Look at the candidate's LinkedIn. Who else worked at the same company at the same time?
Ask your network. Anyone you know who worked with the candidate?
For hiring leaders especially, ask the candidate's listed references "who else would you suggest I talk to who might give me a different perspective?"

Off-list references are often more candid because the candidate didn't pre-select them. They're also more valuable because they're a less biased sample.

A note on ethics: off-list reference checks should be done with care. Don't reach out to anyone currently at the candidate's company without the candidate's permission. Don't make the candidate's job-seeking known to people who could harm them professionally.

What to do with the information

After the references, sit down with the hiring team and review what you learned.

Three buckets:

Confirmed: What the team believed was supported by references
New: What you learned that wasn't visible in interviews
Concerns: Anything that flagged

For confirmed and new positives, factor into your enthusiasm for the hire. For concerns, decide: can we address this directly with the candidate, do we need another reference, or does this change our decision?

A small concern from one reference is usually noise. A consistent concern across multiple references is signal. Treat it that way.

Build reference checks into your hiring process

The mistake most companies make is treating reference checks as a final compliance step. They should be a planned, structured stage in your hiring process, with the time and rigor that matches the seniority of the hire.

For senior hires: