Reference Checks That Actually Get You Straight Answers

The reference call that told you nothing

You've had this call. You ask "how was she to work with?" and the answer is "great, we were sad to see her go, all the best with the hire." Twelve seconds of politeness and you learn nothing you didn't already know from the CV. You hang up, tick the box, and hire on gut feel anyway — which defeats the point of checking at all.

This isn't the reference's fault. Nobody wants to be the person who cost someone a job, and most companies have a policy of confirming dates and titles only, for legal reasons. If you want something more useful than a formality, you have to ask differently.

Pick the right person to call

The reference the candidate gives you is chosen because they'll say something nice. That's fine — you're not trying to catch anyone out, you're trying to get texture. But you can improve your odds:

• Ask for the direct manager, not HR and not a peer. HR gives you dates. A peer gives you gossip. A manager can actually speak to output.
• Ask for two references from two different jobs, if the candidate has more than one. A pattern across employers tells you more than one glowing call.
• If the candidate is reluctant to give you a current manager because "they don't know I'm looking," that's normal and not a red flag by itself — but it does mean you're only hearing about the past, not the present.

Questions that get past the script

Generic questions get generic answers. "Would you rehire them?" is useful but easy to dodge with silence, which itself tells you something. Better to ask about specific, checkable situations:

1. "Tell me about a project or task you gave them that didn't go well. What happened?" Everyone has one. If the reference genuinely can't think of anything, they're either being careful or haven't worked closely enough with the person to know.
2. "How did they handle being told they were wrong?" This is the question that separates people who take feedback well from people who look great in the interview and fall apart under correction.
3. "If you gave them a task with no instructions, what would they do?" Tells you about initiative versus needing to be managed closely — relevant for a small company where nobody has time to hover.
4. "What kind of manager did they need from you?" A good reference answers this specifically — "needed clear deadlines and would drift without them" is gold. A vague "oh, they were low-maintenance" is not.
5. "Is there anything you'd want to know before hiring them, that I haven't asked?" This open door catches things a structured question can miss, and gives a reference permission to say something without volunteering it unprompted.

Notice none of these ask for a yes/no verdict. You're asking for a story, and stories are harder to fake and easier to read for tone — hesitation, over-length praise, a laugh in the wrong place.

Listen for what's missing, not just what's said

A reference who talks for five minutes about how nice someone is, and never once mentions their work, is telling you something. So is a reference who answers every question with exactly one sentence. You're not analysing words on a transcript — you're on a call, so pay attention to:

• Enthusiasm gaps. Warm about the person, cool about the work (or the reverse).
• Qualified praise. "She's great at the technical side" and then silence on anything else, when you asked about teamwork.
• Too rehearsed. If it sounds like they prepared a statement, they probably did — worth a gentler follow-up question to get off script.

Get it in writing when you can't get it on a call

Some companies will only do email verification. That's not nothing — send three or four of the questions above by email instead of a form, and you'll sometimes get more candour in writing than on a call, because the reference has time to think and no live pressure to fill silence. A short email like this works:

> "Thanks for agreeing to speak with us about [name]. To save time, here are the main things we're trying to understand: What would you say their biggest strength was in the role? Was there ever a task that didn't go well, and how did they respond? What kind of management did they work best under? Anything you'd flag for us before we make a decision?"

What a reference check can't tell you

Be honest with yourself about the limits here. A reference check tells you how someone performed in a different job, under a different manager, with different tools and different pressure. It's a strong signal on character and work habits — it is a weak signal on whether they can do this specific job, especially if the role has changed since they last worked in it. That's a different question, and it's usually better answered by giving the candidate an actual task or a skills assessment rather than asking someone else to describe them from memory. If you want a consistent, comparable read on ability rather than reputation, that's a separate step — tools like AssessFit exist for exactly that gap, and references and skills checks work better as a pair than either does alone.

A short checklist before you call

• Confirm dates, title, and reason for leaving with HR or payroll if the company requires it — that's your factual backstop.
• Call the direct manager for the texture, not just HR for the paperwork.
• Ask for stories, not verdicts.
• Write down what you hear immediately after the call — memory of tone fades fast, and you'll want it when comparing candidates later.
• If a reference dodges a question twice, that's a data point. Don't ignore it because everything else sounded fine.

None of this makes a reference check bulletproof. People move on, forget details, or genuinely didn't work closely enough with someone to have a real opinion. Treat it as one input among several, not a verdict — and be suspicious of yourself if one great phone call is doing all the work of a hiring decision.