Reference Check

There are things an interview cannot tell you. An interview runs an hour or two at most, and what comes out of it is the story the candidate prepared. What can be prepared and what surfaces over six months of working next to someone are different sets.

It shows up like this. Someone clears the technical interview cleanly and does fine in the culture interview that looks at how they work, and two months after joining one thing becomes visible: they're strong on work they own alone, but the conversation stops when a code review pushes back on them. No interview could have produced that situation. You can't genuinely argue with a stranger and watch what happens.

The scope written on a résumé also slips past interviews. A line saying someone led a launch frequently turns out to mean they ran the schedule, and pressing on that line during an interview turns the room into an interrogation. Someone who sat through that launch can settle the same question in one sentence without any of that.

What kept this step in the process is the cost of filling one seat wrong. Add the cost of the hire, the ramp-up time, and hiring again, and it routinely exceeds half of that person's annual salary. So a step gets placed right before the decision: ask someone who has already worked with them. Doing it with the candidate's consent is the precondition, not an option.

It starts with getting consent and a list of references, then moves through deciding what to ask, making the calls, and recording the result. Two or three references at twenty to thirty minutes each puts the whole thing at a day or two.

1. Consent and the list. Tell the candidate this step is happening and ask for two or three people who worked with them. As a rule, the current employer's manager comes off the list. If word that someone is looking gets out through that person, the candidate is the one who loses something.
2. Decide what to check. Pick only the two or three questions still open after the interviews. A call that re-asks what interviews already settled spends everyone's time. If the reaction to being pushed back on is what's still open, ask that one thing.
3. Establish the relationship. Open the call by confirming when, for how many months, and in what capacity they worked together. What someone who sat nearby for two months says and what someone who shared a project for two years says do not carry the same weight.
4. Ask about behavior. A question about whether someone is good generally returns that they are. Ask about past situations instead: what happened when opinions split, when they raised a slipping deadline. If the answer doesn't come back as a specific scene, treat that item as unconfirmed rather than as confirmed-good.
5. Record and apply. Write down what was said and how it fed the decision. With no record, the next candidate gets a different bar, and nobody can say later why one person cleared and another didn't.

Two things need care. One is that the candidate picked the list, so favorable answers are the default; include a question that can split, such as whether they'd work with the person again. The other is scope. Questions stay on the work, and never go past the consented range into private life or health.

Four parties are involved: the candidate, who consents and supplies the list; the two or three references who answer; whoever runs the calls; and the hiring manager, who takes the result and decides. When a recruiter runs the calls, scheduling and notes stay consistent. When the manager runs them, they can follow an answer with another question on the spot, which produces more.

The default mix of references is one direct manager from the previous job and one peer who worked alongside them. For a management role, add one person who reported to them. Three managers and nothing else tells you only how they took direction, and leaves how they were to work beside completely blank.

The timing is after all interviews are finished and immediately before the offer goes out. Put it earlier and there are still several candidates in play, which multiplies the number of calls. Push it past the offer and it becomes hard to reverse, because you end up telling someone who already has terms in hand that the answer changed.

Two exceptions come up. A candidate looking for their first job has nobody who has worked with them, so an internship supervisor stands in or the step is skipped. When the fact of a current job can't be disclosed, the check moves to after joining, or it comes out of the process and the take-home assignment carries more weight instead.

"I'll run a reference check before we send the offer. Consent is in."

Placing this step immediately before the decision.

"All three references were managers, so I asked for one peer as well."

Mixing the relationships changes which items actually get confirmed.

"All I heard was that they're a good person. That isn't a confirmation."

An answer with no specific scene in it won't be used as evidence.

Pagedeck ran this step for the first time on a senior engineering opening. Even after four interviews, Theo wasn't sure about one thing. The candidate's solo design work was good, but what kind of person they were when someone argued against that design never came out in an interview.

The references were a manager from the previous job and two peers from the same team. Theo ran the calls himself and asked one thing: whether a design review had ever split, and how it got resolved. Two specific scenes came back from the peers. Grace put that in the record and sent the offer.

The most common reading is that this is a background investigation behind the candidate's back. That picture comes to mind first — asking around without the person knowing. The actual process starts from the opposite end: the candidate is told, consent is given, and the candidate supplies the list. Left uncorrected, the misreading causes trouble in both directions. Candidates refuse the step outright, and companies run it without telling anyone, which crosses into handling personal information without consent.

The other common view is that no bad word means a pass. It's a verification step, so nothing wrong looks like clearance. But given that the candidate chose the list, favorable answers are the baseline. What you're reading is not the verdict but the specificity. A scene that arrives with a situation and a resolution attached is confirmation; an answer that they're diligent and pleasant is not. Left uncorrected, the process runs, nothing new enters the decision, and the offer goes out anyway.