How to Ask for a Job Referral

Asking for a job referral the right way can be the difference between your resume sitting in a queue and a recruiter actually reading it.

I spend a lot of time looking at how people actually get interviews, and the pattern is hard to ignore: the people who land interviews at competitive companies are usually the ones who got a referral first. Not because they were smarter. Because a human actually read their resume instead of it sitting in a queue with 243 other applications.

That number isn't made up. Greenhouse benchmark data put the average at 244 applications per job in 2025. A referred application at most large companies skips that general queue and lands in front of a recruiter or gets flagged for the hiring team. A referral doesn't guarantee you an interview, but it dramatically raises the odds a person reads your resume at all.

So this post is about how to actually ask for one. I've put this together from watching what works for candidates going through this process, plus the basic mechanics of how referral portals work inside companies. Most people ask wrong, and the wrong way is worse than not asking. Here's the version that works.

What Are You Actually Asking for When You Request a Referral?

There are three levels of referral, and they're not equal.

The strongest is a formal internal referral, where the employee submits you through the company's referral portal. That's the one that routes you past the ATS queue. The middle option is a warm intro to the hiring manager, which beats a cold application but doesn't carry the same weight. The weakest is a name-drop in your cover letter, which gives you a small bump and not much else.

You always want the first one. So when you ask, you're asking someone to submit you through their portal.

Here's the part people miss: you're not begging for a favor. Most big companies pay employees a referral bonus, often somewhere in the $1K to $10K range, when someone they refer gets hired. You're handing them a low-effort way to earn that bonus and help their team. Frame it that way in your head and the whole thing stops feeling like charity.

What Prep Do You Need Before Reaching Out?

The single biggest mistake is sending "hey, do you know of any openings?" That puts all the work on them, and nobody answers that. Before you reach out, have these ready:

• The exact role. Job title, job ID, and the URL. Not "your data team." The specific posting.
• A clean LinkedIn profile. Keyword-rich headline, an About section with a real metric or two, your relevant skills listed. The person you ask will look at it.
• A current resume tailored to that role. Run it against the job description first and close obvious keyword gaps. ATS pre-checkers do this in a couple minutes. This matters because if your materials are weak and someone refers you anyway, the mismatch reflects on them, and they'll be slower to help next time.
• A 2 to 3 sentence "why I fit" blurb they can paste straight into the portal note field. Recruiters now spend seconds on a referral note, so it has to be tight.

Our Resume Builder checks your resume against the job description and flags keyword gaps in minutes—exactly the pre-work you need before asking anyone to put their name on your application.

If you walk into the ask with all of this, the referrer can act in under two minutes. That's the bar.

How Do You Find the Right Person to Ask?

Go in this order:

1. People who've seen your work. Former managers, colleagues, clients. They can vouch for you honestly, so they can refer you directly.
2. Alumni from your school at the company. Shared identity gets you a high response rate even cold. People help people from their school.
3. Second-degree LinkedIn connections. If you have a mutual contact, ask for an intro first.
4. Cold contacts with a real anchor. Same former employer, same open-source project, same conference. The anchor has to be genuine.

Within a company, aim for mid-level individual contributors with roughly 3 to 6 years of experience on the relevant team. They have referral budget they haven't used, they care about their team growing, and they don't feel the social pressure a junior employee does. Senior leaders are overwhelmed by these requests and cold messages rarely land. Pick one or two people per company, not twenty. People talk internally, and the same message showing up in five coworkers' inboxes looks desperate. Three to five contacts per company is plenty, and you only message one or two at a time.

Simplify Network surfaces your first- and second-degree connections at target companies and shows you exactly who to ask—no more guessing whether someone is on the right team. It pulls the profile, flags the mid-level ICs most likely to respond, and tracks your outreach so nothing falls through.

How Should You Write the Message?

For a cold contact, keep it under about 100 words and structure it in three parts: shared context, the specific role plus one real reason you want this company, and a low-pressure ask.

Don't open with "will you refer me." Ask for their perspective or a quick call first. The referral follows naturally if the fit is obvious. For warm contacts who already know your work, you can ask directly.

Here's an alumni cold-outreach version that works:

Hi [Name], I came across your profile while looking at [Company]. I'm a [Year] [School] grad and saw you went there too. I'm interested in the [exact role title, Job ID] on your team. My background is in [2 to 3 relevant skills], and in my current role I [one specific achievement with a number]. If the fit looks reasonable, I'd appreciate your take on the role or the referral process. I've attached my resume and the job link to make it easy.

And a warmer version, for someone who already knows you or shares a strong tie:

Hi [Name], we're both [School] alumni and I noticed you're on the [team] at [Company]. I'm targeting the [role] in [city] (link: [URL]). My background is in [area], and I [one specific achievement with a number] in my current role. If you'd feel comfortable referring me, I can send a short blurb you can paste into the portal, plus my resume and the job ID. No pressure at all if it's not a fit.

Both messages end by handing over the materials and making it easy to decline. That "no pressure if it's not a fit" line does real work. It signals you're not going to be weird about a no.

When Should You Ask, and How Do You Follow Up?

Ask before you apply when you can. Most internal referral systems want the referral to come in before or alongside your application. If you've already applied, say so right away, because the referral can still help a recruiter notice your profile faster.

If they don't reply, wait several days, then follow up once. One line, restate the ask, make the no easy:

Hi [Name], following up on my note about the [role] at [Company]. Totally fine if it's not the right fit to refer me. If you do have a moment, I've attached everything needed. Either way, thank you.

Then move on. No second follow-up.

When you hear back either way, close the loop. Tell them when you get an interview or when the role closes. Thank them regardless of outcome. The point isn't just this one referral, it's that they'll help you again.

Getting a referral is about being organized and making the ask frictionless—and Simplify is built to handle the tracking and prep work so you can focus on the relationship.

Frequently Asked Questions

Do referred candidates really get interviewed more often?

The gap is significant. Multiple sources in recruiting research cite interview rates of 20–35% for referred candidates versus 1–3% for cold applicants to the same role. The mechanism is straightforward: referred applications at most large companies bypass the general ATS queue entirely and route directly to a recruiter or hiring team flag. With average applications per open role running near 244 in 2025, anything that routes you past that queue has a real, measurable effect on whether anyone looks at your resume.

What if I have no connections at the company I want to work for?

Start with alumni networks before treating any outreach as fully cold. Your university alumni association, LinkedIn's alumni filter, and school Slack groups often surface people at your target company you didn't know existed. If you genuinely have zero connections there, a cold outreach with a real shared anchor—same former employer, same open-source project, same niche conference—still works when the anchor is genuine. The key is specificity: one well-researched message to the right mid-level IC beats ten generic DMs to senior leaders who never reply to cold messages.

How do I handle it if I already submitted my application before finding a connection?

Disclose it immediately and upfront in your outreach message—something like "I already applied on [date], job ID XXXX." Most referral systems prefer the submission to precede the application, but the referral can still help in a meaningful way: it flags your existing application for a recruiter and can pull it out of the general queue faster. The referrer should know the situation so they can submit correctly on their end. Don't hide it; recruiters and referrers see the timestamp on your application regardless.

Does it matter which employee refers me, or is any referral equally good?

It matters more than most people expect. A referral from someone on the hiring team or directly adjacent to it carries more weight than one from someone in a completely unrelated department. Most referral portals allow the submitter to add a note explaining the relationship and why they're vouching for you—that note gets read by a recruiter in seconds. A generic "I met this person on LinkedIn" note is much weaker than a specific one-liner about shared work. Which is exactly why you write the blurb for them.