What to Expect From Reference Checks

The reference call is a confirmation, not a retrial

If you take one thing from this guide, take this: by the time a company is dialling your referees, it has mostly decided to hire you. References usually come near the very end, after the interviews have gone well and often after a verbal offer or just before a written one. The call exists to confirm the picture the company already has, not to start a fresh evaluation. Hold onto that framing, because it tells you what the conversation is really for and stops you treating it as one more exam to pass.

Where references sit in the process

It helps to picture the funnel. A hundred applications might become ten phone screens, four onsite loops, and one or two finalists. By the time references are requested, the cost of being wrong about you has gone up sharply for the company. They have spent engineer hours interviewing you, they have a hiring manager who wants the seat filled, and they often have an internal narrative about why you are the right person. A reference call is the company stress-testing that narrative one last time. The default outcome is that it holds.

The mental model that serves you best: references are a confirmation step, not a fresh trial. The decision is mostly made. Your job is to make sure nothing in this stage gives anyone a reason to reopen it.

References are common but not universal. Some companies skip them entirely, some treat them as a formality, and some take them seriously and weigh them in the final decision. You will rarely know in advance which kind you are dealing with, so the safe assumption is that they matter and that you should prepare for them properly. The cost of over-preparing is a fifteen-minute phone call with someone who likes you. The cost of under-preparing is a referee fumbling a question that did not need to be fumbled.

There is also a timing dimension that catches people out. References are increasingly run in parallel with the background check and right-to-work verification, all of which kick off once you accept a verbal offer. This means the gap between "we want to hire you" and "here is your start date" is where references live. Knowing this lets you set expectations with your referees about when the call will come, which matters more than most candidates realise.

Who gets contacted, and who chooses

In most processes you supply the references, which means you have a lot of control over who gets contacted. The standard ask is two or three people who have worked with you directly, usually including at least one former manager. Some companies will specifically want a manager because a peer reference cannot speak to how you handled feedback, ownership, or difficult situations from above.

The shape of the request tends to follow seniority and role. Here is a rough map of what companies typically look for:

Notice the pattern. As you go up, the references stop being only about whether you can do the job and start being about your effect on the people and systems around you. An engineering manager will almost always be asked for a direct report, because the single most revealing reference for a manager is someone who reported to them. A manager who cannot produce a willing former report is a flag in itself.

A separate thing to be aware of is the back-channel reference, where someone at the hiring company quietly asks a mutual contact about you, outside the list you provided. This is more common in small, well-connected industries and at senior levels. You cannot control it, and worrying about it is wasted energy. The only real defence is the obvious one: leave roles on reasonable terms and treat colleagues well, so that an unprompted opinion is likely to be a fair one. The engineering world is smaller than it looks. The person interviewing you may well have worked with someone you worked with, and that link is invisible to you until it is not.

What referees are actually asked

The questions are usually less dramatic than people fear. A typical reference call covers ground like this:

• Confirming the basics: that you worked there, in what role, and for roughly what dates.
• How you and the referee worked together, and in what context.
• What you were good at, and where a manager would have coached you.
• How you handled feedback, pressure, or disagreement.
• Whether they would work with you again.

That last question carries a lot of weight. A warm, specific "yes, without hesitation" is worth far more than a long list of generic compliments. The questions about weaknesses are normal and expected, and a thoughtful referee answering them honestly tends to make the whole reference more credible, not less.

It is worth understanding how a trained interviewer reads the answers, because that tells you what a strong reference sounds like versus a weak one.

What a strong reference sounds like

A good reference is specific, balanced, and unhesitating on the points that matter. Vague praise reads as either a referee who did not know you well or one who is being careful. Specifics read as truth. Compare these two answers to the same question, "Can you tell me about a time they handled a difficult situation?"

Weak, even though it is positive:

"Oh, she was great. Really solid engineer, always delivered. Everyone liked working with her. I would definitely hire her again."

Strong:

"There was a payments incident in our second quarter together where a bad deploy was double-charging a subset of customers. She was not on call but she picked it up, found the root cause in about forty minutes, wrote the rollback, and then ran the post-incident review without getting defensive about the fact that it was partly her change. The thing I remember is she pushed for a guardrail in CI so it could not happen again, rather than just closing the ticket. Yes, I would hire her tomorrow."

The second answer is more useful to a hiring manager by an order of magnitude, and the candidate did not say a word of it. The referee did. That gap is precisely what briefing closes, which we will come to.

The hesitation tell

Experienced reference-takers listen for hesitation and for what is conspicuously absent. If a referee gives glowing answers on everything except teamwork, and goes quiet or generic when teamwork comes up, that silence is the signal. A reference does not need to contain a single negative sentence to leave a poor impression. It can do it through omission. This is another reason to pick referees who can speak warmly across the board, not just about your code.

What companies can and cannot ask

There are limits on what employers and referees can do, and they vary by country. In some places a former employer will only confirm dates of employment and job title as a matter of policy, partly to avoid legal risk. Certain topics are off limits or heavily restricted, such as questions about health, disability, or other protected characteristics, and in many jurisdictions there are rules around what can be asked about prior salary.

A few patterns worth knowing, without pretending this is legal advice:

• Confirmation-only references are common from large employers. Many companies instruct HR to confirm only dates and title, regardless of how the manager personally felt. If a former employer gives a flat reference, it is usually policy, not a comment on you. Hiring companies know this and weight your nominated references accordingly.
• Protected characteristics are off the table. Health, disability, age, religion, pregnancy, and similar topics should not feature in a professional reference. In the UK the relevant framing comes from the Equality Act 2010; in the US the equivalent guardrails sit under the employment practices the EEOC prohibits. A referee straying into these areas is a problem for them, not for you.
• Salary history is increasingly restricted. Several jurisdictions limit or ban asking about prior pay, which is part of why offer negotiation should rest on the market rate for the role rather than your last number. See our guide to negotiating tech compensation for how to anchor on the role instead.
• References should be honest but defensible. A referee who invents a damaging claim can expose themselves to liability. This is one reason most negative references are quiet rather than loud: omission and faint praise rather than accusation.

You do not need to memorise employment law to handle this well. The useful takeaway is that a structured, professional reference process tends to stay focused on your work and your conduct. If anything in a reference request strikes you as intrusive or improper, it is reasonable to raise it with the recruiter rather than ignore it.

Prepare your referees properly

The single most useful thing you can do is brief the people you list. A referee who is caught off guard gives a worse reference than one who is ready, even when they think highly of you.

A short brief should cover:

• That you have listed them, and rough timing for when a call or form might arrive.
• The role and company you are interviewing with.
• One or two things you would value them highlighting, tied to what the job needs.
• A reminder of a project you worked on together, so the details are fresh.

This is not coaching them to lie. It is helping an honest person give an accurate, specific, and timely answer instead of a vague one dredged up from memory. Always ask permission before listing someone, and thank them afterward regardless of the outcome.

A worked example: the briefing message

Here is the difference a brief makes, made concrete. Imagine you are interviewing for a senior backend role that emphasises owning a service end to end and mentoring less experienced engineers. A bad approach is to list your old manager and say nothing, hoping he remembers. A good approach is a short, specific message:

Subject: Quick heads-up, reference for a backend role

Hi Tom,

Hope you are well. I have reached the final stage for a Senior Backend
Engineer role at Northwind and I have listed you as a reference. They may
call or email you in the next week or so.

The role leans heavily on owning a service end to end and on mentoring
mid-level engineers, so if it comes up naturally, the two things that would
help most are:

  1. The notifications service rebuild we did last year, where I owned the
     migration off the old scheduler and ran it to production with no
     downtime.
  2. The work I did mentoring Priya and Sam through their first on-call
     rotations.

No need to prepare anything formal, just wanted the details fresh in case
they ask. Genuinely grateful, and happy to return the favour any time.

Thanks,
Alex

Notice what this does. It tells Tom the call is coming so he is not ambushed. It names the role so he can pitch his answers to it. It hands him two concrete, true stories so that when the interviewer asks an open question, Tom reaches for a specific incident rather than "yeah, he was solid." It does not script him or ask him to exaggerate. Every claim is something Tom witnessed. You have simply made it easy for an honest person to give a vivid, relevant reference instead of a forgettable one.

How briefing differs from coaching

There is a clear line and it is worth naming. Briefing supplies context and refreshes memory. Coaching puts words in someone's mouth or asks them to misrepresent what happened. The first is normal and expected; recruiters assume you have spoken to your referees. The second is risky and tends to backfire, because a coached referee sounds rehearsed and an interviewer who senses scripting starts probing harder. Stick to context and facts. Let the referee's own words carry it.

Choosing the right people

Pick referees who can speak to the work the role actually needs. If you are interviewing for a position with heavy ownership and ambiguity, a manager who saw you run a messy project unsupervised is far more valuable than a senior leader who barely worked with you but has an impressive title. Relevance and specificity beat seniority every time.

A few practical pointers:

• Favour people who saw your work closely over people who are merely senior.
• Mix perspectives if you can, for example a manager plus a close collaborator.
• Avoid anyone you parted from on poor terms, for obvious reasons.
• Keep your list current, and re-ask permission rather than reusing an old yes.

A simple scoring method

When you are unsure who to list, score each candidate on three axes from 1 to 5 and add them up:

A referee who scores 5 on warmth but 2 on relevance and 2 on recall will give a pleasant, useless reference. A referee who scores 4, 4, 4 is gold. Run the three or four people you are considering through this quickly and the right list usually picks itself. Seniority is deliberately not on the axes; it is a tie-breaker at best.

Lining up the right referees at each level

Who you should put forward shifts sharply as you climb, because the question the call is answering changes. The earlier table mapped what companies request; this is the practical counterpart, namely who you should actually line up and brief, and what each level is quietly testing.

• Junior and mid-level. The call is mostly confirming that you are reliable, take feedback, and ship. A former manager or even a strong mentor covers it. Recall matters most, because the referee needs to vouch for consistent delivery rather than dramatic impact. One person who watched you work closely beats two who barely did.
• Senior. The question shifts to influence and judgement. Interviewers want to hear that you raised the standard around you, made good calls under ambiguity, and worked across team lines. A cross-functional partner, say a product manager or a senior engineer from another team, often adds more than a second engineering manager, because they speak to your reach beyond your own desk.
• Staff and principal. Expect more rigour and a higher chance of a back-channel. The interviewer is probing for organisational impact and technical leadership, the kind of thing that is hard to fake and hard to self-report. Choose referees who can speak to scope and to decisions that moved more than one team, not just to your competence.
• Engineering manager. The pivotal reference is a former direct report, which is why this guide lists engineering manager among its related roles. A hiring company assessing a manager will discount a glowing peer reference if no report will vouch for them. If you are interviewing for a leadership role, line up someone you managed who genuinely valued how you led. If you cannot produce one, that is worth sitting with before you apply, because the absence is itself the signal the panel is listening for.

Edge cases and how to handle them

A few situations come up often enough to plan for.

You cannot use your current employer. This is the most common worry, and it is completely normal. Your search is confidential and you cannot risk your current manager finding out. Recruiters see this constantly. Offer references from previous roles, or from people at your current company who already know you are looking and can be trusted. It is also reasonable to ask that any reference checks happen only after a written offer, so that your search is not exposed before anything is settled. A sensible employer will understand the request, and a company that pushes back hard on it is telling you something about how they operate.

You left a role badly. Maybe there was a clash with a manager, or a departure that was not amicable. Do not list that manager. Choose someone else from the same period, a peer or a skip-level who saw your work fairly. If the gap is conspicuous, a short, neutral framing handles it: "My manager on that team has since left the company, so I have listed a senior colleague I worked with closely instead." You are not obliged to relitigate a bad relationship.

You are early in your career with few references. New grads and career changers often have a thin list. University project supervisors, internship managers, open-source maintainers you collaborated with, and clients from freelance work all count. What matters is that they saw you do real work, not their job title.

A referee goes unresponsive. People get busy and emails get missed. This is exactly why you brief referees in advance and give the recruiter more than the minimum if you can. If someone goes dark, tell the recruiter promptly and offer a replacement rather than letting the process stall in silence.

The role wants a reference you genuinely cannot provide. If a company insists on a current-manager reference before any offer, and that is impossible for you, say so plainly and explain why. Most will accommodate. If one will not, weigh how that inflexibility predicts the rest of working there.

A short checklist

Before you hand over your list, run through this:

• Asked permission from every referee, recently, not years ago.
• At least one former manager, more if you are senior.
• Each referee scores well on relevance, warmth, and recall.
• Briefed each one on the role and the timing.
• Reminded each one of one or two specific shared projects.
• Confirmed contact details are current.
• Agreed, where needed, that checks happen only after a written offer.
• Planned to thank them afterwards, whatever the result.

FAQ

How many references should I provide? Two or three is standard. Provide what is asked for, and have a fourth in reserve in case someone is unreachable. More is not better; quality and relevance carry the call.

Can a bad reference cost me the job? It can, but it is rare when you have chosen and briefed your referees well. The more common failure is a lukewarm reference that introduces doubt, not an actively hostile one. Both are largely avoidable by picking people who will advocate for you.

Should I tell my referee what to say? No. Brief them on the role and remind them of shared work, but do not script them. Coached references sound coached, and that prompts more probing, not less.

What if my old company only confirms dates and title? That is policy at many large employers and hiring companies expect it. It is why your own nominated references matter. Lean on people who can speak freely about your work.

Do references happen before or after the offer? Usually after a verbal offer and around the time of the written one, often alongside background and right-to-work checks. You can reasonably ask that they wait until a written offer is in hand if your search is confidential.

Is a peer reference as good as a manager reference? For some roles, yes, especially senior cross-functional ones. But many companies specifically want a manager who can speak to how you took feedback and handled ownership, which a peer cannot fully cover. Aim for a mix.

Keep it in proportion

For most candidates, references confirm a decision that has already mostly been made. If your interviews went well and you treated your colleagues decently, the reference stage is rarely where things fall apart. Choose relevant people, brief them clearly, ask permission, and then let the conversation do its job. Spending more energy on it than that is usually energy better spent elsewhere in your search.

The honest summary is this: the reference stage rewards groundwork you mostly did years ago, by being someone people are glad to vouch for. Everything in this guide is just making sure that goodwill actually reaches the call.

Sources

• Equality Act 2010, legislation.gov.uk. The UK statute that defines the protected characteristics a professional reference should never touch.
• Prohibited Employment Policies and Practices, US Equal Employment Opportunity Commission. The US framing for pre-employment inquiries and protected characteristics.

Next steps in this stage

References sit alongside the rest of the offer phase, so the useful next reads are about what happens around the call:

• Negotiating tech compensation, for the offer conversation references run in parallel with.
• Post-interview follow-up etiquette, for keeping the late stage warm without overdoing it.
• Interview red flags to notice, since how a company handles your reference request is itself a signal.