How IT Reference Checks Actually Work

You got the call. The hiring manager says you’re their top choice. “We just need to run reference checks and we’ll send the offer.”

And then… silence. Days. A week. Sometimes two. You refresh your email every twenty minutes wondering if this is the part where the offer falls through.

Most IT candidates treat references as a paperwork formality, a box HR has to tick before the offer letter goes out. That assumption is wrong, and it’s expensive. Reference checks have killed more IT offers than most people realize, and the reasons are rarely what candidates expect.

Here’s what actually happens when a company calls your references, what they’re listening for, and how to stop leaving this entire stage of the process to luck. For broader prep across the full hiring pipeline, our interview prep hub collects every guide in one place.

What Reference Checks Really Are (And Aren’t)

The cleanest way to understand reference checks is to separate them from what you probably think they are.

They are not a verification step. Verification of employment dates, titles, and salary is a separate process, usually handled by a background check vendor like Checkr or HireRight that contacts HR departments directly. Your former employer’s HR team almost certainly will not say anything beyond “yes, they worked here from X to Y” due to legal liability. That’s background verification, not a reference check.

Reference checks are different. They are conversations, usually 15 to 30 minutes, between a hiring manager (or recruiter) and someone you chose as a reference. The goal isn’t to catch you lying. It’s to answer a specific set of questions the interview couldn’t answer, things like:

• How does this person actually behave under pressure?
• Do they ghost when tickets pile up, or do they communicate?
• Are they the kind of engineer who documents their work or leaves you to reverse-engineer their scripts at 2 AM?
• Would you hire them again?

That last question is the killer. More on it later.

Why the Stakes Are Higher Than You Think

IT roles, especially sysadmin, DevOps, and security roles, come with significant blast radius. A bad hire in a help desk seat causes tickets to pile up. A bad hire with production access can take down revenue. Companies learned this the hard way over the last decade, and hiring processes adjusted.

Most mid-to-senior IT offers now hinge on reference checks in a way entry-level jobs do not. If you’re interviewing for anything above help desk, and especially for anything touching production infrastructure, assume the reference stage is a real filter, not a rubber stamp. The same goes for federal and contractor roles covered in our federal IT jobs and security clearance guide, where the bar is even higher.

Who Actually Makes the Call

Knowing who picks up the phone to contact your references changes how you prep them. There are three common setups:

The hiring manager does it themselves. This is the most serious version. The manager calls each reference personally and has a real conversation. They ask follow-up questions. They read between the lines. If the reference hesitates before answering “would you hire them again?”, the manager notices. This pattern is common at small and mid-sized companies, and at startups where the hiring manager is often the one who’ll work alongside you.

An internal recruiter or HR does it. This is more of a structured checklist: ten to fifteen standard questions, read verbatim, answers typed into a form. Less nuance, but still dangerous if a reference says something alarming.

A third-party service does it. Services like Xref or SkillSurvey send your references an online questionnaire. They answer rating-scale questions and sometimes open-ended ones, and a report gets generated. These are increasingly common at larger companies. The trap here: your references may click through a 20-question form without realizing the hiring decision weighs heavily on their numeric ratings.

Ask the recruiter or coordinator how references will be contacted. This is a reasonable question, and the answer tells you how to prepare your references.

The Questions They Actually Ask

Reference check questions fall into patterns. Here are the ones that show up in almost every IT reference call, and what each one is really trying to learn.

The Warm-Up Questions

• “How do you know the candidate, and for how long?”
• “What was your working relationship?”

These seem harmless. They aren’t. The caller is calibrating how much weight to give everything that follows. A reference who worked with you for three months on one project carries less weight than a direct manager who oversaw two years of your work. If most of your references say “we worked together briefly on one sprint,” the caller downgrades the entire check.

The Scope Questions

• “What were their primary responsibilities?”
• “Can you describe a project they led or contributed significantly to?”

Here’s what’s secretly being checked: whether your reference’s description of your work matches what you said in your interview. If you claimed you “led the AWS migration” and your reference describes your role as “helped with parts of the AWS migration,” you’ve got a problem. The discrepancy gets flagged and you probably lose the offer.

The Behavior Questions

• “How did they handle stress or tight deadlines?”
• “How did they respond to constructive feedback?”
• “Describe a time they had a conflict with a teammate. How did they handle it?”

These are the questions that reveal your working style. “They did fine” is not a good answer for a reference to give. Specific, positive stories are. If your reference fumbles these, the caller assumes the reference is hiding something, even if they’re just unprepared.

The Technical Questions

• “What were their strongest technical skills?”
• “Where could they improve technically?”
• “Were there areas where they needed significant support or supervision?”

The “where could they improve” question is a trap for references, not candidates. If the reference says “nothing, they were perfect,” the caller doesn’t believe them. A thoughtful answer, like “she was stronger on the network side than the storage side, but she picked things up quickly,” is actually reassuring. Prep your references to answer honestly but constructively.

For roles heavy on hands-on skills, interviewers dig into technical depth here. If the reference can’t speak credibly to your technical work, the offer can wobble. If you’re worried about this, our guide on why IT pros fail technical interviews covers the broader pattern of technical doubt derailing offers.

The Dealbreaker Questions

• “Why did they leave?”
• “Would you hire them again?”
• “Is there anything else I should know before extending an offer?”

These three do the real damage.

“Why did they leave?” needs to match whatever you said in the interview. If you told the interviewer you left for a promotion opportunity and your reference says you left because the team was being dissolved, you just created a credibility gap. Our article on why did you leave your last job covers how to frame this consistently, and your references need the same story.

“Would you hire them again?” is the single most important question in any reference check. A hesitant “uhh, yes, I think so” is worse than a flat “no.” Even a pause of two seconds before the answer is enough to make a hiring manager pull back. Your references need to be ready for this one without rehearsing it so hard it sounds fake.

“Is there anything else I should know?” is the open mic. A good reference uses it to add something positive. A neutral reference says “no, that’s everything.” A bad reference uses it to warn the caller. You have zero control over this answer in the moment, which is why reference selection matters more than reference prep.

Red Flags That Kill Offers

After a reference call, the hiring manager writes up notes. Certain patterns set off alarms regardless of what else was said. If you’ve ever wondered why an offer quietly disappeared after references, one of these likely happened.

The story mismatch. Your reference describes a different role, project scope, or timeline than what you claimed. Hiring managers notice this immediately. They don’t call you to clarify. They just withdraw.

The lukewarm recommendation. “He was fine. Did his job.” No specifics. No enthusiasm. This is how references signal “I don’t actually recommend this person but I’m not going to torch them.” Hiring managers read this loud and clear.

The “you should probably ask them about X” deflection. When a reference redirects a question back to you (“you might want to talk to the candidate about that timeline”), they’re flagging something without saying it directly. Hiring managers interpret this as a warning.

Contradictory references. One reference praises you, another damns with faint praise, a third describes a completely different work style. Inconsistency reads as you being different things to different people, which in hiring is rarely viewed as a strength.

Stale references. References who haven’t worked with you in five-plus years are treated skeptically. Someone who managed you in 2018 can’t credibly speak to whether you’ve grown since. Our piece on returning to IT after a career break addresses this specific situation for candidates with gaps.

References who don’t answer. If two out of three of your references don’t return calls within a week, hiring managers get nervous. Either you didn’t warn them (unprofessional) or they don’t want to speak up (worse). You lose the offer through inaction.

How to Actually Pick Your References

The mistake most IT candidates make is picking references based on title or tenure instead of fit to the role. A VP of Engineering who barely remembers you is worse than a senior engineer who sat next to you for two years.

The Ideal Reference Mix

For most IT roles above help desk, a solid reference set looks like this:

Role	What They Cover	Why It Matters
Former manager	Performance, reliability, growth	Validates your work history and trajectory
Peer/teammate	Collaboration, day-to-day behavior	Confirms you’re not a jerk to work with
Cross-team	Communication with non-IT or different teams	Shows you can work outside your silo

If you’re moving into a specialized role, say from sysadmin to security, a reference who can speak to your security-adjacent work is gold. Hiring managers for SOC analyst roles or penetration testing positions want to hear from someone who saw you actually do security work, not someone who heard you talk about it.

Who Not to Pick

• The reference you haven’t spoken to in three years. They don’t remember enough about you to speak specifically. Specificity is what sells a reference check.
• The reference who doesn’t actually like you. Some people will agree to be your reference out of politeness and then damn you on the call. Ask yourself honestly: would this person be enthusiastic?
• The reference still at the company you’re hiding from. If you’re leaving a bad situation, don’t list a reference who will tell your current employer you’re looking.
• Family members, college friends, or clients. These get dismissed immediately unless the role specifically calls for a client-facing recommendation.

The Coworker Who Became a Friend

One subtlety: hiring managers can usually tell when your reference has become a personal friend. It doesn’t automatically disqualify the reference, but it discounts their praise. A reference who’s objective (“she was strong, though her documentation needed work”) reads as more credible than one who’s glowing about everything.

How to Prep Your References (Without Coaching Them)

There’s a line between prepping your references and scripting them. Cross it and the reference sounds coached, which reads as manipulative. Don’t cross it.

The Pre-Call Email

Send your references a short email the moment you expect the reference check. Include:

1. The role you’re interviewing for (title, company, and one-line description)
2. The specific skills or experiences you’ve highlighted (“I talked a lot about the Terraform migration we did in 2024”)
3. Your reason for leaving (so their answer matches yours)
4. When to expect the call (within the next week, typically)
5. Who’s calling and how (hiring manager vs. third-party service)
6. A simple thank-you

Here’s a rough template:

Hey [Name], thanks again for being willing to serve as a reference for the [Role] role at [Company]. The hiring manager, [Name], will likely reach out by phone this week. In our interviews, I focused on [specific project/skill], so if that comes up, your perspective there would mean a lot. I mentioned I left [Previous Company] because [one-line reason]. Really appreciate you. Happy to return the favor anytime.

That’s it. No scripts. No “please say X.” You’re giving them context, not coaching.

The Skills-Focused Reminder

If you’ve pivoted (say, from help desk to sysadmin, covered in our help desk to sysadmin progression guide), your reference needs to know which of your skills are relevant to the new role. A former manager remembers you as a help desk tech, not as a junior sysadmin, unless you remind them of the scripting work you did on the side. Spell it out.

The Response-Time Ask

Make sure your reference will respond quickly. If they’re on vacation, swap in a backup. A reference who takes two weeks to return a call stalls your offer. If the company you’re joining has a tight timeline, this matters enormously. See our 48-hour guide on what to do with a job offer for why speed matters at this stage.

What to Do When You Don’t Have References

This is more common than people admit, especially for career-changers and early-career IT pros. Here’s what to do.

You’re Entry-Level or a Career-Changer

If you’re breaking into IT from another field (our non-tech to tech transition guide covers this in depth), you probably don’t have IT-specific references yet. That’s fine. Pick the best professional references from your previous career. A hiring manager who understands the situation will give weight to what your references can speak to: reliability, work ethic, ability to learn.

If you did a bootcamp, a former instructor or cohort lead can work. So can anyone you contributed to on open source projects. If you’re active in communities like HackTheBox or TryHackMe, a team lead from a CTF or lab series counts.

You Left Your Last Job Badly

Maybe you got laid off. Maybe you were put on a PIP. Maybe you just left a hostile manager. You don’t owe the current search a reference from that place. Pick a peer, a cross-functional partner, or a manager from a job two positions back. Be honest with the recruiter that you’d prefer not to use your most recent manager.

Do not fabricate references. Hiring managers across IT, many of whom share stories in our IT hiring manager insights guide, have seen candidates fake a reference. The faker almost always gets caught. The offer almost always gets pulled.

You’re an Independent Contractor

Ask clients. A project lead, a CTO you worked closely with, a product manager who’s seen your work: any of these can speak credibly. The contractor vs full-time employee breakdown touches on this: your references in contract work are your clients, and you should be cultivating them throughout every engagement with the next job search in mind.

You’re a Veteran

Military transitions into IT are common (covered in our military cybersecurity training guide). Your commanding officer or a senior NCO absolutely counts. Hiring managers value military references for reliability and discipline. Don’t discount them.

Reference Checks After a Layoff

If you were laid off (which many IT pros have been in recent cycles, captured in our IT layoffs 2026 survival guide), layoff references are slightly different. Here’s what works:

• Be upfront with your references that the layoff was not performance-based. They should mention this naturally when asked about your departure.
• If your manager was also laid off, they’re often your best reference. Shared experience makes them honest and clear.
• Don’t avoid the topic in your own interview. If your story and your references’ stories line up around “the org was restructured,” you’ll be fine. The concern is only if your version doesn’t match theirs.

The Hidden Risk: LinkedIn Backdoor References

Here’s something most candidates don’t think about: hiring managers increasingly do unofficial reference checks through their own networks. They look at your LinkedIn, see who you have in common, and DM that person. Sometimes they call.

This is called a backdoor reference, and you have zero control over it.

The only defense is to be the kind of colleague people speak well of, across every role. The engineer who’s cold, dismissive, or territorial during team meetings creates a trail of potential unofficial references who remember that. The engineer who helps, documents, and ships clean code creates the opposite.

You can’t prep for backdoor references. You can only earn them over years.

When References Go Sideways

Sometimes a reference call goes badly through no fault of your own. The reference is having a bad day. They misremember a project. They say something that creates confusion.

If a hiring manager follows up with a clarifying question after references, answer clearly and don’t get defensive. Say: “I can understand why that came across that way. Here’s what actually happened…” Most managers appreciate calm, specific follow-up. If you panic or get emotional, they assume the reference was right.

If an offer is withdrawn after references, you’re usually not told why. You can politely ask the recruiter for feedback, but don’t expect a straight answer. Legal teams discourage specifics. Treat the experience as information for next time: one of your references may no longer be useable.

You’re probably skeptical that references matter this much. Fair. Most articles on interview prep skip the reference stage entirely because it’s not as dramatic as bombing a technical question. But offers die here quietly all the time, and the candidates rarely know why.

FAQ

How many references should I prepare?

Line up four or five, even if only three are requested. Some companies ask for more. Some of your references may be unreachable during the call window. Redundancy matters.

Can an old employer legally say negative things about me?

In the US, yes, as long as what they say is factual. Most HR departments refuse to say anything beyond “yes, they worked here” for liability reasons, but individual managers acting as references can share opinions. This is why picking references carefully matters more than worrying about what HR might say.

Should I give references before a company asks?

No. Providing references on the resume or early in the process is outdated. Wait until the company requests them, usually right before an offer. Early reference requests are a minor red flag that a company is either disorganized or fishing.

What if I’m asked for my current manager as a reference?

Decline politely. Say: “I’d prefer not to involve my current manager until an offer is finalized, for obvious reasons. Here are three alternatives who can speak to my work.” No reasonable employer will push this.

How long does a reference check actually take?

Per reference, the conversation is usually 15-30 minutes. End-to-end, including scheduling, most reference processes take three to seven business days. Longer than that and something is stuck, usually because one reference hasn’t responded.

Can I see what my references said about me?

Almost never. Some third-party services will share a summary, but most don’t. You’re not legally entitled to see the content of a reference call unless the company is based in a jurisdiction with specific disclosure laws.

Is a reference check ever skipped entirely?

Rarely, and usually only for extremely senior roles where the candidate is well known in the industry. For most IT roles, assume references will be checked. Even internal hires sometimes get reference-checked across teams.

The Takeaway

Reference checks are the most ignored stage of the IT interview process, and also one of the most decisive. Companies don’t tell you when references sink an offer. They just go quiet.

The fix is simple but not easy: pick references who will actively advocate for you, give them enough context to be specific, and don’t leave this stage to chance. Your references are a reflection of your career. Make sure that reflection is the one you want employers to see.

If you’re further back in the job search, our why your IT job applications aren’t working guide covers the earlier stages. If you’re mid-interview, the first five minutes of an IT interview guide is where to look. And if an offer already landed, the 48-hour guide for new offers walks through the next steps.

Don’t treat references as the last item on a checklist. Treat them as part of the interview, because that’s what they are.