Reference checks that test what the interview found
Picture the last reference call for a customer support hire. The recruiter has ten minutes before the next interview, the reference is a team lead the candidate chose, and the questions are the ones on every template: How do you know the candidate? What are their strengths? Any areas of improvement? Would you hire them again? The answers come back warm, general and useless. “Great with customers. Very hard-working. Could be a bit more confident. Yes, of course.”
Nothing in that call tested anything. The candidate chose a friendly reference, the questions invited friendliness, and the recruiter learned nothing they did not already believe. This is why many hiring teams quietly treat references as a formality. The fix is not a cleverer list of reference check questions. It is building the call from what your own interviews already found, written down on a scorecard while it was fresh, so every question checks something specific.
What is a reference check?
A reference check is a short, structured conversation with someone who has worked with a candidate, usually a former manager, to verify what the candidate told you and to learn how they actually worked. It is most useful after the final interview, when you know which claims and which concerns are worth checking.
The US Office of Personnel Management describes reference checking as an objective evaluation of an applicant’s past job performance, gathered from supervisors, peers and subordinates. Two lines on that page are worth keeping in mind. Reference checks predict job performance better than years of education or experience. And adding structure, the same job-related questions for every candidate with a standard way of recording answers, greatly improves how useful they are.
What a reference check can and cannot tell you
A reference check is good at three things:
- Confirming facts. Dates, title, who they reported to, the size of the team, whether they were eligible for rehire.
- Testing specific claims. “I handled escalations for the whole floor” is either true, partly true or not true, and a former team lead knows which.
- Showing how the person is to manage. What they needed, what they did without being asked, what wore people down.
It is bad at two things, and pretending otherwise is how teams get burned:
- Ranking candidates. The candidate chose the reference. Almost every reference is positive, so a glowing reference says little about whether this candidate is better than the next one. Use the interview for ranking; use the reference for checking.
- Finding problems nobody wants to say out loud. Many former employers will confirm only dates and title, by policy. A reference who says “I can only confirm employment dates” is following a rule, not hinting at a problem.
So the job of the call is narrow: confirm, test and learn how to manage. Everything below serves one of those.
Before the call: build the questions from your interview
The most common reason reference calls are useless is that they are prepared from the job description, not from the candidate. Ten minutes with your interview notes changes the call completely.
Go back through the scorecard and the notes and pull out three lists:
- Claims to verify. Anything the candidate said that would matter if it were false: the size of the target they carried, the process they say they built, the reason they left.
- Scores of 1 or 2. Where the candidate’s answer was vague or thin, the reference may fill the gap. A candidate who could not describe a conflict clearly may still have handled conflict well.
- Things you will need to manage. Anything the interview hinted at that would change how you onboard them: a preference for written instructions, a first job in a target-driven team, a long commute.
If your first round was recorded, this is where the recording behind a scorecard pays for itself. A transcript lets you quote the candidate’s own words back to the reference, neutrally, instead of paraphrasing from memory: “She told us she ran the morning shift handover. Can you tell me how that worked?”
25 reference check questions, by what they verify
Choose eight to ten for a 15-minute call. Always ask the first group and the last.
The relationship (always ask)
- How do you know the candidate, and for how long did you work together?
- What was their role when you worked with them, and what was yours?
- How often did you see their work directly: daily, weekly, or mostly through results?
Role and facts 4. What were they responsible for, in your own words? 5. Roughly how large was the team, the target or the workload they handled? 6. Why did they leave, as you understand it?
The specific claims from your interview 7. They told us they [claim]. Can you tell me how that worked in practice? 8. What part of that was theirs, and what part was the team’s? 9. If I asked you to describe their best piece of work, what would it be?
How they worked 10. Describe a normal busy day for them. What did they prioritise? 11. How did they handle a mistake, theirs or someone else’s? 12. Tell me about a time they disagreed with you or a colleague. How did it go? 13. What did they do without being asked? 14. How did they handle a customer, client or colleague who was upset?
What they needed from a manager 15. What kind of instructions worked best for them: detailed, or a goal and freedom? 16. What feedback did you give them most often? 17. When they improved, what helped them improve? 18. What would their next manager need to know in the first month?
Calibration questions that get honest answers 19. Compared with others you have managed in the same role, where would they sit: top 10 percent, top quarter, middle, or below? 20. If they had one thing to work on in their next role, what would it be? 21. Was there a type of task or situation where you would not have put them?
The close (always ask) 22. If you had the chance, would you hire them again for the same role? 23. Is there anything I have not asked that you would want to know in my place? 24. Who else worked closely with them that I could speak to? 25. Is there anything you would like me to keep in confidence?
Questions 19 to 21 do most of the work. “Any areas of improvement?” invites a polite non-answer. “If they had one thing to work on in their next role, what would it be?” assumes there is one, which every honest manager knows is true, and gives the reference permission to say it.
Questions that get polite answers, and how to rewrite them
| Polite-answer question | Why it fails | Rewrite |
|---|---|---|
| What are their strengths? | Invites adjectives | What was the best piece of work they did for you? |
| Any weaknesses? | Invites “works too hard” | If they had one thing to work on in their next role, what would it be? |
| Were they a team player? | Yes or no, always yes | Tell me about a time they disagreed with a colleague. |
| Would you recommend them? | Always yes | Compared with others in the same role, where would they sit? |
| How was their communication? | Invites “very good” | How did they handle an upset customer or colleague? |
The pattern is the same as in a good interview: ask for events and comparisons, not opinions. A reference finds it much easier to describe a real afternoon than to rate a person.
Reading the answers: faint praise, pauses and real red flags
Most reference answers are positive, so the signal is in the shape of the answer, not its tone.
- Faint praise. “She was always on time” in answer to “What was her best work?” is a reference choosing what they can honestly praise. Follow up once: “And the work itself?”
- The pause before the rehire question. A real pause, followed by “Yes, for the right role”, is worth a follow-up: “What would the right role look like?”
- Mismatched facts. A different title, a much smaller team or different dates than the résumé deserve a direct, neutral question to the candidate, not an assumption. People round up; some invent.
- Specific praise. Detail is a good sign in both directions. “He rebuilt the escalation tracker in his second month and we still use it” is worth more than “excellent performer”.
- Refusal by policy. “I can only confirm dates and title” is common in large companies. Thank them, confirm what they can, and lean on your other references.
One concern from one reference is a question to explore, not a verdict. The same concern from two references who do not know each other is a pattern.
Reference checks in India: a few practical rules
Reference checking in India has its own habits, and a few rules keep it fair to the candidate and useful to you:
- Get consent and the right contacts from the candidate. Ask for a former manager by name, not just the HR department, and confirm they agreed to be called.
- Never call a current employer without permission. With long notice periods common, a candidate who is outed before they have an offer can lose their job. (Notice period itself is a fact to settle in the first call, not at the reference stage.)
- Separate verification from the reference conversation. Employment verification (dates, designation, last salary drawn) often comes from the former employer’s HR team or a verification agency. The conversation about how they worked comes from the manager. Do not expect the HR desk to answer question 12.
- Keep it about the job. Questions about family, health, religion or community have no place in a reference call, here or anywhere else.
Reference checks for freshers and high-volume roles
Two situations break the standard advice: candidates with no former manager, and roles where you hire forty people a month.
Freshers and campus hires. A final-year student has no line manager to call, and asking a college placement officer about a candidate’s work ethic gets you an attendance record at best. The right reference is whoever saw the candidate do real work: an internship supervisor, a project guide, the faculty member who ran their final-year project, the manager at a part-time job. Ask the same questions in groups 1, 3 and 4 above with the noun changed (“on the project” instead of “in the role”), and drop the calibration question about others in the same role unless the reference has supervised a cohort. Keep expectations modest. A project guide can tell you whether the candidate owned their part and met deadlines; they cannot tell you how the candidate will handle a hundred customer calls a day.
High-volume hiring. When you are hiring forty support agents a month, a 15-minute call for every one of them is 10 hours of recruiter time that buys little, because most entry-level references will be thin anyway. Three practical rules:
- Check references only for the final shortlist, never for everyone who applied or cleared the first round.
- Make the check proportional. For entry-level volume roles, employment verification plus one short call with the most recent supervisor is enough. Keep the full 15-minute script for team leads, roles with cash or customer data, and any candidate whose interview left a specific open question.
- Spend the time where the interview left a gap. A candidate who scored well everywhere does not need question 12. A candidate whose answer on handling an upset customer was a 1 does.
The point of a reference check is to reduce the risk left after the interviews. Where the interviews already left little risk, the check can be short.
A reference check script you can copy
Opening (1 minute): “Thank you for making time. [Candidate] is in the final stage for a [role] with us and gave us your name. This will take about 15 minutes, and nothing you say will be shared with the candidate word for word.” Relationship (2 minutes): questions 1 to 3. Facts (2 minutes): questions 4 to 6. Claims from our interview (4 minutes): questions 7 to 9, using the candidate’s own words. How they worked (3 minutes): two of questions 10 to 14, picked from the scores of 1 or 2. Calibration (2 minutes): questions 19 and 20. Close (1 minute): questions 22 and 23. Thank them.
Write the answers into the same scorecard as the interview, under the question they relate to, the same day. A reference note on its own sheet is a note nobody reads at the decision meeting.
Where the first round fits in
HireQwik does not run reference checks, and we would not want an AI on the other end of that call. Reference checks belong to the final stage, between people who know each other’s work.
What the first round can do is make that final call shorter and sharper. Every HireQwik interview is recorded and transcribed, and each one ends with per-question scores that quote the candidate’s own words. By the time a candidate reaches references, you have their exact claims about their last role, the questions where their answer was thin, and a recording to check before you dial. That is the material questions 7 to 9 need. If you are running the earlier rounds by hand, the same discipline applies: write down what the candidate said, in their words, while you still remember it.
The rest is scoring. A reference answer is evidence like any other, and it reads best next to the same 0-3 scale as the interview; our behavioral interview questions guide shows that scale, and how to write interview feedback covers notes the next reader can use. To see what a first-round transcript and scorecard look like, try the live demo.
Frequently asked questions
How many references should you check for a candidate?
Three is the usual minimum, and it is what the US Office of Personnel Management recommends. Try to include at least one person who managed the candidate directly. For an entry-level hire with little work history, a project guide, internship supervisor or part-time manager counts. One reference tells you about a relationship; three start to tell you about a pattern.
What questions should you not ask in a reference check?
Do not ask about anything you could not ask the candidate directly: age, marital status, family plans, health, religion, caste or community, or anything unrelated to the job. Keep every question about work the candidate did and how they did it. Also avoid asking the reference to compare the candidate with named colleagues or to share confidential details about their former employer.
Should reference checks happen before or after the job offer?
For most roles, run them after the final interview and before the written offer, or make the offer conditional on references. Checking every applicant early wastes time for everyone, and calling a current employer before the candidate has an offer can cost them their job. Always tell the candidate when you will call and get their agreement first.
See your own candidates screened
Book a 30-minute demo. Bring a live JD and we'll screen against it, then start with a pilot on your own candidates before committing to anything.
Existing customer? Sign in