Reference check
A reference check run properly is the cheapest hour in your process and the only point at which somebody who has already worked with this person tells you what it was like. Run as a formality it confirms dates and produces the phrase "great team player", which is what a reference says when the question had only one acceptable answer. The difference is entirely in the questions.
The questions, and how to read the answer
Eight questions, twenty minutes, on a call rather than by email. Written references are drafted by the candidate more often than anybody admits, and almost none of the signal is in the words. It is in the pauses, the qualifications, and what gets volunteered after the question has been answered.
In what context did you work together, and for how long?
A strong answer: A precise reporting line and dates that match what the candidate told you, with the shape of the team volunteered before you ask for it.
A weak answer: Vagueness about who reported to whom, or a period materially shorter than described. Note it, do not confront it, and ask the same question of the next reference.
What did they own that would have failed without them?
A strong answer: A specific thing, named, with what would have happened instead. A reference who managed somebody closely answers this in one sentence.
A weak answer: A restatement of the job title. It usually means this person never saw the work, which is a fact about the reference rather than about the candidate.
If you were building the same team again, where would they be on your list?
A strong answer: An immediate answer with a reason, including an honest "near the top for this kind of work, not for that kind".
A weak answer: A long pause followed by praise. The pause is the answer and the praise is the recovery.
What did they need from a manager to do their best work?
A strong answer: Something concrete you can act on: how much context they need up front, how they take feedback, what they do when under-directed. This is the most useful answer in the call, and it is useful whether or not it is flattering.
A weak answer: "Nothing, they were completely self-sufficient." Nobody is. It means the reference was not close to the work or is protecting the candidate, and either way the answer is empty.
What would you not put them on today?
A strong answer: A real limit, stated without hedging. Every good manager knows the shape of their people, and a reference willing to describe a limit is a reference you can believe about the strengths.
A weak answer: Refusal of the premise. "There is nothing" ends the useful part of the call, and everything after it should be treated as a character witness rather than as evidence.
How did they handle it when something they were responsible for went wrong?
A strong answer: A specific incident, with what the candidate did in the first day of it. Cross-check it against the failure story the candidate told you in the interview.
A weak answer: A general assurance about resilience. Ask again with a timeframe attached, such as in the last year.
Would you hire them again, and is that call yours to make?
A strong answer: A plain yes with a role attached, or a plain no with a reason. The second half of the question matters, because a peer who would rehire is telling you much less than a manager who would.
A weak answer: Qualified enthusiasm about a different role from the one they held. It is often the kindest way a former manager has of telling you something.
Who else saw their work closely that I should speak to?
A strong answer: A name offered readily, ideally somebody the candidate did not put forward. Most of the value in reference checking sits one step past the list you were handed.
A weak answer: Deflection to HR. Sometimes that is genuinely company policy and sometimes it is not, and the way it is said usually distinguishes the two.
Who to ask for, and what to do about a curated list
Every candidate hands you a list of people who will say good things. That is not dishonesty, it is what the request invites. The job is to get one step past the list without going behind the candidate’s back.
- Ask by role rather than by name. "The person you reported to on the project you described" is much harder to substitute than "two references".
- Ask each reference who else saw the work closely, then ask the candidate to introduce you. Done openly this is not a back-channel, and people who are comfortable with their work are usually comfortable with the request.
- A peer reference and a manager reference answer different questions. A peer knows what it was like to depend on them. A manager knows what it took to get their best work.
- A reference from the current employer is usually unavailable for good reasons. Do not read the absence as a signal, and do not accept it as a reason to skip the ones that are available.
- If every reference offered is from more than three years ago, ask about the gap plainly. There is usually a straightforward answer, and occasionally there is not.
When to run them
Run references before the offer wherever your process allows it. A reference call made after the offer is out has almost no ability to change anything, because by then the team has committed, the candidate has resigned in their head, and a mildly concerning call gets rationalised rather than acted on.
- Before the offer: the check can change the decision, which is the only reason to run it.
- After the offer, with the offer conditional in writing: acceptable where a candidate cannot expose a search, and only if you are genuinely prepared to withdraw.
- After joining: a courtesy call rather than a check, because no decision is attached to it any more.
- Never call somebody at the candidate’s current employer without explicit permission. It is the fastest way to cost a person their job and your company its name in that market.
Reading a reference call
- Score the reference before you score the candidate. Somebody who cannot describe the work is telling you nothing, positively or negatively.
- The pause before an answer carries more than the answer. Managers who rate somebody highly say so immediately.
- Superlatives with no particulars usually mean the relationship was good and the working relationship was thin.
- Take the volunteered addendum seriously. The sentence beginning "the only thing I would say" is the reason the call was worth making.
- One weak reference is data. Two weak references on the same theme is a decision, and the theme is what you take to the third.
What a reference cannot settle
- Whether they can do a job they have not done. A reference reports on the last role, and the risk in most hires is the delta between that role and yours.
- Whether they will accept and join. That gets settled in the interview, by asking who else has a say and what would make them say no.
- Facts. Dates, titles and qualifications belong in background verification, which is a different instrument with a different failure mode.
- Anything you did not ask about. References answer the question asked, narrowly, and almost never volunteer the thing you most needed unless you left silence for it.
References and the offer that does not hold
A reference will not tell you whether somebody will join. What it does is surface the conditions this person needs in order to work well, which is exactly what makes an offer conversation specific rather than generic. Specific offers hold better than generous ones, and the gap between an accepted offer and a person at a desk is where most hiring plans quietly fail.
What this looked like on a real role
4 disciplines
sales, clinical, AI, and marketing, through one function
References matter most for hires who arrive with no support structure waiting to absorb a misjudgement. On one founder-led engagement the clinical and AI hires had to own their remit from the first week, across four disciplines that shared nothing except difficulty.
If the offer stage is where your hires keep falling over, the useful exercise is to model it before you extend the next one: run the offer acceptance risk model.
How Continuity1 runs this funnel
The screening above is the job. These are the numbers it produces when a function owns it end to end, set against the published benchmarks for the same market.
A reference check is the last cheap instrument before an offer. What happens after the offer is the number most hiring plans under-budget for.
- 1 in 9
- Accepted offers that ghost before joining
- Indian employers report nearly 4 in 10 offers dropped. We lose 1 in 9.
- nasscom community
- 1 in 3
- Shortlisted candidates you meet who become the hire
- Aligned engagements run nearer 1 in 2, distant ones nearer 1 in 10. The market takes about 180 applicants to make one hire, and that sifting lands on your team rather than ours.
- Continuity1 tracked engagements
- 95%
- Offers that close inside your stated band
- 20 of the last 21. A flat fee earns nothing from an inflated offer; a percentage of CTC earns more.
- Continuity1 tracked engagements
- ~3
- Interviews your team sits in, per hire
- Ashby puts technical roles at 17.6 interviews per hire across the whole process, up 52% since 2021. The rest of that load sits with the function, not with you.
- Ashby talent-trends report
Every brief becomes a success profile before sourcing starts, calibrated with the people who will manage the role. That calibration is the step most hiring skips, and it is why a shortlist either matches the job or matches the job advert.
You review a scored shortlist and make the calls. The filtering never lands on your calendar.
Questions teams ask
How many references should I check?
Two who were close to the work beat five who were not. One manager and one peer from the same period is a sound default, and a third is worth it when the first two disagree or when the role is one you cannot afford to get wrong.
Should reference checks be done by phone or email?
By phone or video. The signal sits in the pauses, the qualifications and what gets volunteered after the answer, and none of that survives a written reply the candidate may well have helped draft.
What questions are off limits in a reference check?
Anything you could not ask the candidate: health, family, age, religion, and anything unrelated to the work. Keep every question tied to job performance, take notes, and get the candidate’s consent before you call anybody.
Can I speak to somebody the candidate did not list?
Ask the candidate first. Requesting an introduction to a named person who saw the work is reasonable and most people agree readily. Calling a current employer without permission is not reasonable, and it can cost somebody their job.
What if a reference is clearly reading from a script?
Ask something with no scripted answer, such as what the candidate needed from a manager, or what you would not put them on today. Scripts get written for the questions everybody asks.
Is a reference check worth doing if we already ran background verification?
Yes, because they answer different questions. Verification establishes that the facts are true. A reference tells you how somebody worked, what they needed, and what their manager would not put them on. A candidate can pass every documentary check and still be the wrong hire.
Related
- Background verification: what to check and how to grade a discrepancy
- Questions to ask an interviewee, with the read on each answer
- Interview questions to ask candidates, assigned by stage
- Panel interview: who sits in the room and what each seat owns
- Behavioural interview: the probes that break a rehearsed answer
- run the offer acceptance risk model
- The numbers above, with their sources