Reference Check Questions: A 2026 Template for Hiring Teams
The reference check happens last, after the interviews and the scorecards and the internal debate, when everyone already wants to say yes. That's exactly why most of them are useless: a hiring manager who's already decided isn't listening for a real answer, they're listening for permission to move forward. The reference on the other end of the line can tell, and gives back exactly as much as the call deserves — polite, generic, over in four minutes.
A reference check done properly isn't a formality. It's the one part of the process where someone who isn't trying to get hired tells you what the candidate is actually like to work with. Here's how to ask questions that get a real answer, and where the legal lines sit.
Why most reference checks produce nothing useful
The questions invite a one-word answer. "Would you rehire them?" and "Were they a good employee?" are easy to answer with "yes" and move on — they don't ask the reference to think, so they don't get a thoughtful response.
Everyone already knows it's a formality. If the candidate chose the reference, and the reference knows the offer is basically decided, both sides are performing a ritual rather than having a conversation. The call becomes about not saying anything that could sink an already-likely outcome.
The call is scheduled for five minutes. A reference who's rushed gives the safe, general version of everything. Real signal takes a slightly longer, slower conversation to surface.
Nobody asks a follow-up. The single biggest miss: a reference gives a slightly hesitant or vague answer, and the caller doesn't push. That hesitation is usually the most honest moment in the whole call, and it gets skipped past instead of explored.
What a reference check is actually for
Not to confirm the candidate is competent — the interviews should have already told you that. A good reference check answers questions interviews structurally can't:
- What are they like day-to-day, over months, not in a one-hour conversation? Interviews are a performance; a reference has watched the unscripted version.
- How do they behave under pressure or after a mistake? A reference who worked alongside them during a hard stretch has seen this; a candidate describing it in an interview is telling you how they'd like to be seen.
- What would this person tell you if you'd already decided not to hire? That's the honest answer you're trying to get to, even though the format makes it hard.
The question set
Ask these in order — the early ones build enough rapport that the later ones actually get answered:
- "How did you two work together, and for how long?" Establishes real context before anything evaluative — a six-month peer relationship and a one-year direct-report relationship produce very different answers to everything that follows.
- "What was [Name] responsible for, and what did they actually deliver?" Compare this against what the candidate told you in the interview — a real gap here, not a rounding difference, is worth a direct follow-up.
- "What's one thing they were genuinely great at?" Easy to answer, warms the reference up, and often surfaces a strength the interviews missed entirely.
- "What's one thing that was harder for them, or that you'd want a new manager to know going in?" The most important question in the set, and the one most callers skip. Framing it as "help their next manager set them up well" rather than "tell me a flaw" gets a real answer instead of a deflection.
- "Can you describe a specific time they handled a setback, a disagreement, or a mistake?" Ask for a story, not a rating — specific incidents are hard to fabricate on the spot and tell you far more than "they handle pressure well."
- "How did they take feedback or direction?" Directly predictive of how a new manager relationship will go, and rarely covered in interviews at all.
- "Would you put them on your team again, and in what kind of role?" Better than a plain "would you rehire them" — it asks the reference to be specific about fit rather than give a blanket yes.
How to hear the answer, not just collect it
Listen for hesitation before a positive answer. A half-second pause before "yeah, definitely" is a different signal than an immediate "yeah, definitely" — when you hear it, follow up gently: "you paused there — anything you want to add?"
Notice what's conspicuously left out. A reference who talks at length about someone's technical skill and says nothing at all about teamwork isn't necessarily hiding something, but it's worth a direct question: "how were they to work with day-to-day?"
Push once, politely, on vague praise. "They were great" isn't an answer — "what specifically made them great to work with?" usually is.
Ask for a second reference if the first one feels rehearsed. Candidates sometimes list the reference most likely to give a polished answer; a second, less-obvious reference (a peer rather than a hand-picked manager) often gives a more textured picture.
Where this fits with async video screening
Reference checks work best as the last filter on a small shortlist, not a box you check for every applicant — which only works if getting to that shortlist was fast. With Flash Interview, candidates answer one screening question on video up front, so you're only booking calls — interviews, and later, reference checks — with people who've already demonstrated basic fit. That keeps the reference call reserved for its real purpose: a deeper check on a candidate you're already fairly confident about, not a first-pass filter on everyone who applied.
The legal lines to stay inside
Reference-check law varies by jurisdiction, but a few practices are broadly safe and a few are broadly risky:
- Ask about job performance, not protected characteristics. Stick to role-related conduct and results; never ask about health, family status, age, or anything that could read as a proxy for a protected class.
- Get the candidate's consent before contacting a reference, especially a current employer — surprising someone's current manager with a reference call can cost them their job before they've even left it.
- Document what was asked and answered. A brief written note of the questions and responses protects you if a hiring decision is ever challenged.
- Know that some employers only confirm dates and title. A "policy only" response isn't a red flag by itself — many organizations restrict what any manager is allowed to say, regardless of how the employee actually performed.
The honest caveat
A reference check is one data point, chosen by the candidate, from a person who has some incentive to help them — it isn't neutral, and it shouldn't be the only thing a hiring decision rests on. Treat a great reference as confirmation of what the interviews already showed, not as a substitute for them, and treat one lukewarm or vague reference as a prompt to ask more questions, not an automatic disqualifier.
Flash Interview lets hiring teams screen candidates with a 50-second recorded video answer before a single call gets booked — so the interviews and reference checks you do run happen only with candidates worth that time. $39 per role, up to 50 candidates, no subscription.
Frequently asked questions
What questions should you ask on a reference check?
Start with context (how they worked together, for how long), then role and delivery, then a specific strength, then — the one most people skip — one area a new manager should know about going in, plus a real story about handling a setback or feedback.
How many references should you check per candidate?
Two is usually enough for most roles: one manager-level reference and one peer, since a peer often gives a more textured, less rehearsed answer than a hand-picked manager reference.
Is it legal to ask a reference about salary or health?
No — reference questions should stay on job performance and conduct. Asking about health, family status, age, or similar protected characteristics is legally risky regardless of intent.
What if a reference will only confirm dates of employment?
That's common and isn't itself a red flag — many employers restrict managers to name, title, and dates as a blanket policy. Treat it as a non-answer rather than a negative signal, and lean more on your other reference.
Should you check references before or after making an offer?
Most teams check references after a verbal offer is discussed but before it's formally signed — it keeps the process fast for a candidate you're serious about, while still giving you an exit if something significant surfaces.