How to do engineering reference checks that matter

A reference check that matters does one of two things: it confirms a decision you have already mostly made, or it surfaces one specific, concrete thing your interview loop could not see. Most reference checks do neither, because founders treat them as a formality run on the candidate's three favorite coworkers, with vague questions that invite vague praise. The fix is not more calls. It is better people, sharper questions, and a clear view of what a reference can and cannot legally tell you.

This post is the founder-side companion to running a fast loop. If you are still designing the interview itself, start with how to run a fast engineering interview loop and structured interviews and scorecards. References come after the loop, as the last gate before an offer.

What is a reference check actually for?

By the time you are checking references, you have spent 6 to 10 hours interviewing this person. You know whether they can code, design a system, and talk through tradeoffs. What you do not know is how they behave over 18 months: under deadline pressure, after a disagreement with a peer, when a project they owned slips. References are the only cheap way to compress months of observed behavior into a 25 minute call with someone who has already lived it.

So the goal is narrow. You are not re-verifying skills. You are testing the two or three specific doubts your loop left open, and you are listening for the thing nobody volunteers.

Listed references vs back-channel: which to trust

There are two kinds of references, and they are not equal. Listed references are the names the candidate hands you. They are pre-vetted to say good things, so their value is not the verdict (it will be positive) but the texture. A listed reference who has clearly worked closely with the person will give you concrete stories. One who speaks only in adjectives ("great engineer, team player") did not work closely with them, and that itself is a small signal.

Back-channel references are people you find on your own: a shared former colleague, someone in your network who overlapped at a past company. These are where the unvarnished signal lives, because the person did not choose them. They are also where the legal and ethical lines get real, so handle them carefully (more below).

Weight first-hand and recent over senior and distant. A peer who shipped alongside the candidate last year tells you more than a VP who managed them three levels down four years ago.

What questions surface real signal?

The difference between a useless and a useful reference is almost entirely the questions. Yes/no and leading questions get you nothing. Specific, behavioral, comparative questions get you stories you can act on. Decide your one or two open doubts before the call, then aim most of the questions there.

Open with calibration

• "How did you work together, and for how long?" (establishes how much weight to put on everything that follows)
• "What were they responsible for when you overlapped?" (verifies the scope claimed on the resume and in the loop)

Then go behavioral and comparative

• "Of all the engineers you have worked with at their level, where do they rank, and why?" The forced ranking breaks people out of default praise.
• "Tell me about a project of theirs that slipped or went sideways. What happened, and what did they do?" Everyone has one. A reference who cannot name one was not close to the work.
• "When they disagreed with a technical decision, how did they handle it?" This is the single best predictor of how they will behave on your small team.
• "What kind of work or environment brings out their worst?" Phrased as fit, not flaw, so people answer honestly.
• "Would you hire them again, on your own team, today?" Listen to the speed and warmth of the yes, not just the word.

The most useful answer in any reference call is the half-second pause before someone says "yes."

The closing question that does the most work

End every call with: "Is there anything I did not ask that I should have?" People hold back the one real concern until you give them a clean opening to volunteer it. This question is where a reference most often saves or sinks a hire.

What should you actually weight, and what should you ignore?

References are good at some things and useless at others. Weight them on behavior, judgment, reliability, and how someone handles conflict and failure. These are exactly the things a 6 hour loop cannot reveal and a person who lived through 18 months can.

Discount them on raw technical skill (you already tested that), on a single negative from someone with an obvious grudge, and on stale data. A strong reference does not override a clear no from your loop, and a glowing reference does not rescue a candidate your interviewers had real doubts about. The loop is the primary signal. References adjust at the margin and catch the rare landmine.

Where are the legal lines?

This is the part founders get wrong, usually out of enthusiasm rather than malice. A few lines you do not cross (this is general guidance, not legal advice, and US employment law varies by state):

1. 01Get consent before contacting anyone the candidate listed, and especially before back-channeling. Contacting a current employer without permission can cost someone their job and cost you the hire. Always ask first.
2. 02Never ask about protected characteristics. Age, race, religion, national origin, disability, pregnancy, marital or family status, sexual orientation. Not directly, not as a proxy ("are they planning to start a family soon?"). These questions create legal exposure and tell you nothing useful.
3. 03Stick to job-related behavior. Performance, reliability, collaboration, and judgment are fair game. Health, personal life, and politics are not.
4. 04Keep notes factual and consistent across candidates. If a reference says something concerning, write down what was said, not your interpretation. Run the same process for everyone so your decisions are defensible.
5. 05Honor confidentiality. If a back-channel reference speaks candidly on the condition you not repeat it, do not relay it to the candidate or anyone else.

The simplest safe default: only contact people the candidate has approved, ask everyone the same job-related questions, and treat back-channel outreach as something you clear with the candidate first.

How does this fit a fast offer process?

References are the last gate, not a parallel track, and they should not slow you down. Run them in the 24 to 48 hours between your final loop debrief and the offer, in parallel with finalizing comp. For a senior hire that means 2 to 3 short calls over two days, decided and scheduled the moment the loop says yes.

Speed matters because the best engineers have other offers moving. If you treat references as a week-long bureaucratic step, you lose candidates while you check the people who were always going to say nice things. Once references confirm, move straight to the close. See how to close an engineering candidate and how to make a startup offer candidates accept for the next step.