35 Reference Check Questions Hiring Managers Actually Ask

Reference checks decide more hires than people admit. A reference call confirms whether the candidate who interviewed well actually shipped work, got along with the team, and would be hired back. The questions you ask decide whether you get the truth or a recycled HR script.

This guide gives you 35 reference check questions that real hiring managers ask, grouped by what you actually want to learn. Use the ones that match the role and skip the rest. Most reference calls run 15 to 20 minutes, so you will not get through all of them, that is fine.

How to use this list

Three rules that make reference calls actually useful:

• Pick 8 to 12 questions before the call, not all 35. Match the questions to the role and the gaps you noticed in interviews.
• Ask open questions. "What were they responsible for?" beats "Were they responsible for marketing?" every time.
• Listen for what the reference does not say. A long pause before a positive answer often means a soft no.

Before the call, send the reference a quick email confirming the role you are hiring for, the candidate's name, and a 15-minute time slot. Pair it with a structured reference check form so you log every answer in the same shape across candidates.

Verifying basic facts

Start with closed questions that confirm dates and titles. If anything contradicts the resume, the rest of the call needs to dig deeper.

1. What were the dates of employment for [candidate]?
2. What was their job title and how did it change over time?
3. Who did they report to, and how many people reported to them?
4. What was the salary range when they left?
5. Were they full-time, part-time, or contract?

What they actually did

The resume tells you what they say they did. The reference tells you what they really did.

6. What were their core responsibilities day to day?
7. What was a project they delivered that you remember well, and what was their role on it?
8. What did they own end to end, versus contribute to?
9. How did their work change between when they started and when they left?
10. What did they get promoted for, or what kept them from a promotion?

How they work with others

How a candidate behaves with peers, reports, and stakeholders is the single biggest predictor of whether they will succeed in your team. Spend the most time here.

11. How would you describe their working style?
12. How did they handle disagreement with you or peers?
13. Who did they collaborate with most often, and how did that go?
14. How did they communicate with people outside their immediate team?
15. What kind of manager got the best work out of them?
16. If they had a conflict with someone, how did it usually get resolved?

Strengths and weaknesses

Frame these in concrete terms. "What are their strengths" gets a recycled answer. "What did they do better than anyone else on the team" surfaces a real one.

17. What did they do better than anyone else on your team?
18. What did they struggle with, and how did you support them through it?
19. What kind of work would you not give them?
20. Where could they grow most in the next role?
21. What feedback did you give them most often?

Performance and impact

Ask about measurable outcomes. Push for numbers. A reference that cannot give you any will tell you what kind of work the candidate actually did.

22. What did they hit on the goals you set?
23. What is a metric or result they moved that you would highlight to a future employer?
24. How did they perform under pressure, deadlines, or difficult customers?
25. How did they handle ambiguity when the path was not clear?
26. What was their biggest miss, and how did they recover?

Why they left

The departure story matters. A clean departure with a strong relationship is a great signal. A vague or evasive answer here is a yellow flag.

27. What was the reason they left?
28. Did they give appropriate notice, and how did the transition go?
29. Was there anything they could have done to stay?
30. Would you hire them back? Why or why not?

Fit for this specific role

These are the role-shaped questions. Tell the reference what the role is in one or two sentences, then ask them to react.

31. I am hiring this person for [role]. What about that role plays to their strengths?
32. What part of the role might they find hardest?
33. What support would they need from a manager to thrive in this role?
34. Is there anything I have not asked that I should know before extending an offer?
35. If you were the hiring manager here, would you offer them the job?

What to listen for (red flags)

Listen for the pattern across the call, not the headline of any single answer. A reference rarely lies outright, but they signal heavily.

• Long pauses before positive answers. "Were they reliable?" followed by 4 seconds of silence is a no in a kind voice.
• "They were great" with no examples. Strong references give a story. Soft references give an adjective.
• Steering toward strengths whenever you ask about gaps. A reference unwilling to name a single weakness is protecting the candidate, not the truth.
• "You should ask them about that" on a direct question. Polite punt. Note the topic and follow up with the candidate.
• "Would not hire back" with no clean reason. Probe gently. Sometimes the answer is "wrong company" not "wrong person". Sometimes not.

Legal and compliance notes

Reference checks sit under FCRA when conducted by a third-party provider, and under state-specific laws (CA, NY, MA, others) regardless of who runs them. A few rules worth knowing:

• Get the candidate's written consent before contacting references. Most candidates expect this, and a signed authorization removes ambiguity.
• Stick to job-related questions. Avoid protected categories: age, religion, national origin, disability, family status, sexual orientation, political views.
• Document what was said, not your interpretation. "Reference said they would not hire back" is defensible. "Reference seemed unsure" is not.
• Tell the candidate which references you contacted, and when. Trust runs both ways.

For US employers, the EEOC's pre-employment inquiry guidance covers the no-go zones. Most violations come from a manager going off-script, not from the planned questions.

After the call

Three steps that turn reference calls into a hiring signal:

1. Compare answers across references. A pattern from 2 of 3 references is a real signal. One outlier on its own is noise.
2. Match against your interview notes. Where the reference and the interview agree, you have conviction. Where they disagree, that is the gap to close before offer.
3. Bring concerns back to the candidate. "Your reference flagged X. Can you walk me through that from your side?" Most candidates will give you context that resolves the concern, or confirm it.

Use a single structured reference form across every call. Cross-comparison is impossible if every conversation has a different shape.

The takeaway

Reference checks reward preparation. Pick 8 to 12 questions before the call, ask open-ended versions of them, listen for the silences, and compare answers across references. A 15-minute call that confirms what the interview suggested is worth more than another round of technical questions. A 15-minute call that surfaces a contradiction is worth more than any single test you could run.