Reference checks are the step founders most often skip or phone in, and that is a mistake, because a real reference check is one of the last honest signals you get before committing to a hire. Done as a formality, generic questions, a nod, done in five minutes, it tells you nothing, which is exactly why people conclude references are useless. Done well, it can confirm what you saw in the interview or surface the thing that changes your mind. The difference is entirely in how you do it: asking specific questions about real behavior, talking to the right people, and listening as hard to what goes unsaid as to what is stated.
Key Takeaways
- A real reference check is a genuine signal, not a formality to rush through.
- Ask specific questions about actual behavior, not generic ones with easy answers.
- Talk to the right people, ideally those who worked closely with the candidate.
- Listen to what goes unsaid; hesitation and vagueness are signals too.
Ask Specific Questions About Real Behavior
Generic reference questions, was the candidate good, would you hire them again, invite generic, positive, meaningless answers, because almost no one badmouths a former colleague to a vague prompt. The way to get real signal is to ask specific questions about actual behavior and situations. How did they handle a project that went wrong? What would you have wanted them to do better? Can you describe a time they were stuck and how they got unstuck? Specific questions about concrete situations are much harder to answer with empty praise, and they surface the texture of how the person actually worked, which is what you are trying to learn (interview questions for a senior software engineer applies the same specific-over-generic principle).
Talk to the Right People, and Read the Silence
Two things beyond the questions matter. First, who you talk to: a reference who worked closely with the candidate, a manager or a teammate who saw their day-to-day, tells you far more than a distant or hand-picked contact. Push, politely, for people who actually worked with them rather than only the curated best friends. Second, and most important, listen to what is not said. References rarely lie outright, but they signal through omission and tone: a hesitation before answering whether they would rehire, a pointed lack of comment on a specific area, enthusiasm that goes quiet on one topic. Those silences and hesitations are often the real message, and a good reference check is as much about reading them as about the literal answers.
| Weak reference check | Strong reference check |
|---|---|
| Generic questions | Specific behavior and situations |
| Hand-picked distant contacts | People who worked closely with them |
| Only hears the words | Reads hesitation and omission |
| Rushed formality | Genuine, careful conversation |
A Concrete Version
You are about to hire a developer and do the reference check. The formality version: you ask a former colleague if they were good, hear yes they were great, and move on having learned nothing. The real version: you talk to someone who managed them directly and ask specific questions, describe a time a project went sideways, what would you have coached them on. The reference answers warmly about their technical skill but goes noticeably quiet and vague when you ask about how they handled feedback or worked under pressure. That silence is the signal. It does not automatically disqualify the candidate, but it tells you exactly what to probe further, information the formality version would never have surfaced.
The Honest Counterpoint
Reference checks are valuable and imperfect, and you should weight them appropriately rather than treating them as definitive. References are usually chosen by the candidate and skew positive, people have off days and personality clashes that unfairly color a reference, and a single lukewarm comment is not proof of a problem. The signal from references is real but noisy, so use it to confirm, probe, or raise questions rather than as a sole verdict, and combine it with the direct evidence of your own evaluation. For roles hired through a vetting partner, much of this diligence is already built into the process (the five-stage vetting process). Take references seriously, read them carefully, and weigh them alongside everything else.
The Bottom Line
Checking a developer's references well means treating it as a genuine signal rather than a formality to rush. Ask specific questions about real behavior and situations, which are hard to answer with empty praise, talk to people who actually worked closely with the candidate rather than distant curated contacts, and listen as carefully to hesitation and omission as to the literal words, because references signal through silence. Weigh the result alongside your own evaluation rather than as a sole verdict, and a proper reference check becomes one of the last, most honest signals you get before you commit.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers in 72 hours. See available engineers.
