You rehearsed the behavioural questions, researched the company, and talked your way into a final round. Then the recruiter asks for two references, you forward two phone numbers from memory, and you stop thinking about it. That is a strange place to go quiet, because the call is often the last thing standing between you and a signed offer.
Reference checks are the least-prepared stage of the hiring process. Not because candidates are lazy, but because the whole thing feels administrative, like a background screen. It usually is not. Here is what happens on those calls, and how to set your references up so they help you instead of costing you the job.
The reference call is a signal, not a formality
Companies do not spend twenty minutes of a hiring manager's time on someone they have already rejected. In most processes, references are contacted after the final interview and either alongside the offer or immediately before it. If you have been asked for names, you are in the top one or two candidates.
That timing matters. The shortlist is short, so it is a decent moment to get your salary thinking straight. And the employer has stopped testing whether you can do the job - they are testing whether anything in your history contradicts the picture you painted over four interviews.
A reference call rarely wins you a job on its own. It can absolutely lose you one - usually through a lukewarm answer, not a hostile one.
Genuinely bad references are rare, because most people decline rather than trash someone. The dangerous outcome is the flat, non-committal one: short answers, vague dates, a referee who is clearly reconstructing who you are while they talk. That reads as "not memorable", and it plants doubt at exactly the wrong moment.
Choosing who to put forward
The instinct is to pick the most impressive name in your contacts. Resist it. A VP who saw you present twice and cannot describe your work is worth far less than a team lead who reviewed your output every week for eighteen months.
Rank your options roughly like this:
- A direct former manager from a recent, relevant role. This is what employers want, and what they will ask for by name.
- A skip-level manager or department head with visibility on your projects, if your direct manager has left or is unreachable.
- A senior peer or cross-functional partner - the product manager you shipped with, the client lead you supported. Strong on collaboration, weaker on the rehire question.
- A client or external stakeholder, useful for consultants, freelancers and agency people.
- A direct report, only if you are targeting a management role.
Two categories to avoid. First, the friend who will say lovely things. Experienced reference-takers spot this in about ninety seconds - the answers are warm, generic, and free of any specifics about deadlines, deliverables or conflict. It reads as a coached testimonial, and it makes the employer wonder why you could not produce a real manager. Second, anyone you have not spoken to in three years, whose memory of you is a job title.
Also worth knowing: large employers increasingly run a confirm-dates-only policy. HR verifies dates and job title, nothing more. That is not a red flag against you, but the reference is dead weight. Pair it with a named individual - a former manager speaking in a personal capacity - so the employer gets something substantive.
How to ask, and how much notice to give
Ask by phone or voice note if you can. Email works, but a real conversation lets you hear hesitation, and hesitation is information. If someone says "of course, happy to" with a two-second pause in front of it, find someone else.
Give at least a week of warning, then re-confirm once you know a specific employer is about to reach out. Never list someone who has not explicitly agreed. That is the most common own goal at this stage: the referee gets an unexpected call, is caught off guard, and gives a distracted answer while walking into a meeting.
Here is a message that works:
Hi Sarah - hope things are good at Meridian. I'm in the final stage for a Senior Analyst role at [Company] and they've asked for references. Would you be willing to speak to them? It would be a 15-20 minute call, likely next week. If yes, I'll send over the job description and a quick reminder of what we worked on together so you're not digging through old memory. Completely fine to say no.
That gives context, sets the time cost, offers a briefing, and leaves an easy exit. People say yes to it far more readily than to "can I put you down as a reference?".
The briefing step almost nobody does
Once your reference agrees, send a short brief. Not a script - a brief. Four things:
- The job title and company, plus the job description. Your reference cannot reinforce what the role needs if they do not know what the role needs.
- A two-line reminder of what you did together. Dates, your title, and the projects they were closest to: "You managed me from March 2021 to August 2023 as a Data Analyst; you'll remember the pricing dashboard rebuild."
- Two or three themes you would like reinforced, mapped to the job. If the role is heavy on stakeholder management, say so, and remind them of the difficult finance director.
- Who is calling and when. Name, title, expected window.
Keep it under 200 words. You are removing friction, not writing their lines. A reference who has read the job description gives answers that sound relevant. One working from cold memory gives answers that sound like a eulogy for a job you left.
What they actually ask - and how to prep for the hard one
Reference calls follow a predictable shape:
- Confirmation of dates, job title, and reporting line
- What you were responsible for day to day
- How you performed relative to peers at the same level
- How you handled pressure, deadlines, or one specific difficult situation
- How you took feedback
- Would you hire this person again?
- What is one area where they could develop?
The rehire question carries the most weight. A clean yes is table stakes. A qualified yes - "yes, in the right role" - is where offers start to wobble.
The development question is the trap, and it is why briefing matters. "Honestly, nothing comes to mind" sounds evasive. The right preparation is not to script a fake weakness. It is to make sure your reference knows which real, resolved one to reach for, ideally the one you also raised in your own interviews so the two accounts line up. "Early on she took on too much rather than delegating - we worked on it, and by her last year she was running intake for the whole team" builds credibility instead of draining it.
When your last manager is a problem
Sometimes the only recent manager you have is someone you clashed with. Do not put their name forward and hope. In order of preference: offer a skip-level or senior peer from the same company, which keeps the timeframe relevant even if the reporting line is not exact; offer a manager from the previous role, and be straightforward that the most recent relationship was difficult; or get ahead of it with the recruiter. A short, non-blaming sentence about mismatched working styles usually lands fine. What does not land is a recruiter discovering the problem live on the call.
Rebuilding a contact list from scratch? Your LinkedIn history is the obvious archaeology site - the same profile data a tool like Postulit reads to reconstruct a CV also tells you who you overlapped with, and when.
Close the loop
Message your reference the same week the call happens, and again when you have a decision, offer or no offer. Reference relationships are reusable assets, and the person who hears "thanks, I got it, and your call clearly helped" says yes faster next time.
One thing to do this week: pick your two strongest references, check you have current mobile numbers, and write the two-line project reminder for each now, while the details are fresh. When a recruiter asks - and you will usually have about a day to respond - the work is already done.