How to ask for a referral on LinkedIn (free templates that get replies in 2026)
Asking a near-stranger on LinkedIn for a referral feels awkward. Do it anyway. A referral is the single highest-impact move in a job search, because it skips the part where your resume sits in a stack of 800 and gets filtered on keywords. A real person walks it to the hiring manager instead. Most people say yes when you make the ask small and specific. Below are three templates I keep coming back to, the order to ask people in, and what to do once someone says yes (or goes quiet).
- Ask the person closest to the work first: an engineer on the team, then a manager, then a second-degree connection, then a recruiter.
- Keep the message under 90 words. Say who you are, name the role, give two reasons you fit, and make one specific ask.
- Don’t attach your resume in the first message. Offer it, and send a clean PDF once they reply.
- Send one follow-up after about a week, then move on to the next contact. Most silence is a calendar, not a verdict.
Why a referral actually works
A company trusts its own engineers more than it trusts its resume parser. When someone inside vouches for you, three things happen at once: you skip the keyword gate that screens most applicants out, the recruiter gets a warm lead instead of a cold one, and the employee often earns a referral bonus if you’re hired. Everyone’s incentives point the same direction. That alignment is why even a lukewarm referral usually beats a polished cold application.
It also shows up in the numbers. Recruiting teams consistently rank referrals as their highest-quality, fastest-moving source of hire. Applicant-tracking vendor Ashby, looking at its own customers’ funnel data, found referred candidates advance through interviews at a markedly higher rate than people who apply cold (see its referrals report). The exact multiple shifts by company and role, so don’t anchor on one stat. The mechanism is the part that always holds: a referral changes which pile you land in.
Who to ask first (and who to skip)
Not every contact is worth the same message. The closer someone is to the actual work, the more their referral means to a hiring manager, and the more honestly they can tell you whether the role is even real. Work down this list in order:
- An engineer on the team you’re applying to.They know whether the req is live and what the bar looks like. Their referral carries the most weight because they’d have to work with you.
- An engineering manager in the org. They can route your resume internally without it ever touching the public application form.
- A second-degree connection. Someone you share a mutual with. The shared name softens the cold open and gives you an honest first line.
- A recruiter.Useful, but they field hundreds of DMs, and you’ll rank below an internal employee’s referral. Treat them as a backup, not the first move.
Skip the people who can’t help: a VP you’ve never met, anyone who left the company more than a few months ago, and folks in a different function and timezone who have no read on the role.
The anatomy of a referral ask
Every message that gets a reply does the same four things, in roughly the same order. Miss one and the ask gets weaker:
- Say who you are in one credible line.
- Name the specific role and team.
- Give two concrete reasons the role fits.
- Make one small, specific ask.
That’s the whole formula. The templates below are just this skeleton with the friction sanded off. Notice what’s missing: no life story, no “I’d love to pick your brain,” no resume attached before they’ve agreed to anything.
Three templates that get replies
Steal these and swap in your own details. Each one fits a different starting point, so pick the closest match rather than forcing the same message on everyone.
Template 1: cold second-degree connection
Use this when you share a mutual but have never spoken. The shared name is your whole opening.
Hi Maya, saw we both worked with [mutual] at [shared company]. I’m a senior frontend engineer (React/TS, 6 yrs, the last 3 on a billing dashboard at 4M MAU). Stripe just posted the Senior Frontend role on Checkout, which lines up almost exactly with what I’ve been shipping. Would you be open to flagging my application to the hiring manager, or pointing me to whoever owns that hire?
Happy to send a one-pager or my GitHub if it’s useful. Either way, thanks for reading.
Template 2: alumni or community connection
Use this when you share a school, bootcamp, or community. That bond does a lot of quiet work.
Hi Devon, fellow [bootcamp/school/community] here. I’m applying for the Senior Frontend role on your team at Stripe. I’ve been doing React and TypeScript at scale for four years, most recently leading a payments-dashboard migration to React 18, and the posting reads like my last 18 months. If you’re open to it, I’d really value a quick refer. Happy to grab coffee separately to hear about life on Checkout.
Template 3: re-engaging after silence
Use this once, about a week after a message that went nowhere. Keep it light and give them an easy exit.
Hi Sara, circling back briefly. Totally understand if the timing didn’t work. I wanted to flag that I’m still very interested in the Senior Frontend role. One small ask: is there a better person on the team for me to reach out to directly? Either way, I appreciate you considering it.
Here’s what a full exchange tends to look like once you get the first message right. The reply does most of the work for you.
DM, work email, or InMail?
LinkedIn DMs are the default for a reason: low friction, fast, and you can thread the follow-up onto the same conversation instead of starting over. But the channel depends on what you can actually find. Here’s how the three options trade off:
| Channel | When to use it | Friction | Can you follow up cleanly? |
|---|---|---|---|
| LinkedIn DM | The default. You're already on LinkedIn and you have at least a 2nd-degree link. | Low for them, low for you | Yes — reply on the same thread |
| Work email | When you can find a real address and want to signal higher intent. | Higher to source, easy to ignore | Yes, but a cold inbox is easy to bury |
| InMail | Only when you can't connect or message any other way. | Costs a credit; reads as salesy | Weakest — it's a one-shot pitch |
If you want the longer version of this comparison, including how to find a work email without guessing, we wrote it up in referral email vs LinkedIn DM.
What to do after they say yes
Make their job zero-effort. The moment someone agrees, send a single, clean message with everything they need in one place: a one-page PDF resume, the exact job posting link, and a three-sentence “why I’m a fit” blurb they can paste straight into their internal referral form or a Slack message to the hiring manager. If they offer a call, take it. After the referral goes in, send a one-line thank-you within a day, and another after the interview, whether it went well or not. Referrers remember the people who closed the loop.
What to do if they go quiet
Send one follow-up after about five business days, using Template 3, then let it go. Don’t take it personally, and don’t send a third message. Most silence is a full calendar, not a judgment on you. The better use of your energy is finding the next contact at the same company. If you want the full cadence, including what to say and what kills a follow-up, we broke it down in how to follow up on a referral request.
Doing this without it eating your week
Finding the right person inside a company, drafting a message that doesn’t sound like a form letter, and tracking who replied across ten companies is a part-time job on its own. That’s the part ResumesTailorhandles: it surfaces the right contacts inside the company, drafts a message in your voice from your resume and the job description, and keeps a simple board of who replied, who’s pending, and who needs a nudge. You still press send and you still write the human bits. The tool just removes the busywork between you and the ask.
Want the deeper background on why this works and how to ask people you don’t know at all? Read how to ask a stranger for a referral and how referral bonuses actually work.
Frequently asked questions
How long should a LinkedIn referral message be?
Under 90 words. If you can't make the case in that space, the message isn't ready. A short, specific ask is far easier to say yes to than a wall of text, and it respects the time of someone doing you a favor.
Should I attach my resume in the first message?
No. Offer to send it. Making someone download a file before they even know who you are adds friction for no reason. Once they reply with interest, send a clean one-page PDF and the job link together.
Is it okay to ask more than one person at the same company?
Yes, as long as they're on different teams or in different functions, and you send one ask per person. Two messages to the same small team reads as spray-and-pray, so space them out and write each one specifically for the person.
What if I have no mutual connection?
You can still ask. Lead with specific, genuine relevance instead of a shared contact: reference their work, the team's roadmap, or something they posted. A cold message that proves you did your homework beats a warm one that's generic.
How long should I wait before following up?
About five business days. Send one short follow-up that adds something useful or makes the ask smaller, then move on to the next contact. Most non-replies are a busy calendar, not a no.
Is it rude to ask a stranger for a referral?
Not if you make it easy to say yes. Referrals help the employee too, since many companies pay a referral bonus and a good referral makes the referrer look sharp to their team. Keep it short, specific, and low-pressure, and always give them an easy out.
Build, tailor, and get referred — free
ResumesTailor tailors your resume to any job description, surfaces the right referral contacts inside the company, and drafts the outreach — all in one workspace. Free forever, no credit card.