Copy-ready job referral request templates: email subject lines that get opened, referral request emails for strangers, alumni and former colleagues, LinkedIn connection and message templates, follow-up messages, and what to write if you are the one submitting the referral.
A referral request fails or succeeds on whether the reader can make a decision without doing any work. That means four things, in roughly this order.
Who you are, in one line. Your current role and the relevant experience, not your life story.
The exact role. A requisition ID or a direct link. "Any openings you know of" is unanswerable and is the single most common reason requests are ignored.
Why you match, in two or three facts. Achievements with numbers that map to the posting's requirements. Not adjectives.
An easy exit. One sentence explicitly permitting them to say no. This is the part people leave out, and it is the part that most reliably increases replies, because it removes the social cost of declining.
Attach your resume. Keep the whole thing under about 150 words. If it needs scrolling, it will be read later, which means never.
The templates below are starting points, not scripts. Replace every bracket, and delete anything that is not true.
The subject line decides whether the email is opened at all. Be specific and boring. Clever subject lines read as marketing.
Referral request: [Role title], req [ID]
[Role title] referral, [X] years in [skill]
Referral request from a [University] alum
[Role title] at [Company]: quick referral request
Following up: [Role title] referral request
Avoid: "Quick question", "Opportunity", "Hi!", anything with an exclamation mark, and anything that hides what you want. Vagueness in a subject line reads as a sales email and gets deleted accordingly.
If you have a real connection, put it in the subject. "from a [University] alum" or "we worked together at [Company]" does more than any phrasing trick.
Subject: Referral request: Backend Engineer, req 12345
Hi [Name],
I am a backend engineer with [X] years on [technology], currently at [Company]. I am applying for the Backend Engineer role at [Their company], requisition 12345, and I am hoping you would consider referring me.
Two things that seem relevant to the posting: I [specific achievement with a number, for example "rebuilt a payments service handling 40k requests per minute and cut p99 latency by 60%"], and I [second achievement mapped to a stated requirement].
My resume is attached. Completely understand if you would rather not, since it is your name on it either way.
Thanks for reading, [Your name] [LinkedIn URL]
Why this works: it is scannable in fifteen seconds, it names the exact requisition, the evidence maps to the job description, and the last line removes the pressure that makes people leave these unanswered.
Subject: [University] alum, referral request for req 12345
Hi [Name],
I came across your profile while looking at [Company] and noticed we both studied [Course] at [University], a few years apart.
I am applying for [Role], requisition 12345. I have spent the last [X] years doing [relevant work], most recently [specific achievement with a number]. If you think the profile is a reasonable fit, I would be grateful for a referral.
Resume attached. No problem at all if you would rather not, or if you would just point me at the right team instead.
Thanks, [Your name]
The shared institution goes first because it is the reason they are reading rather than deleting. Do not stretch it. A connection that is obviously manufactured is worse than none.
Subject: Referral at [Company]? [Role], req 12345
Hi [Name],
Hope things are going well at [Company].
I am applying for [Role] there, requisition 12345. You will remember [specific project you worked on together] better than most, so you have a decent sense of how I work.
I have been doing [relevant work] since then, most recently [achievement with a number]. Would you be up for referring me? Resume attached in case it is useful for the form.
Either way, good to reconnect. [Your name]
With someone who has actually seen your work, lead with the shared project rather than a resume summary. They do not need convincing that you are competent. They need reminding of the evidence.
LinkedIn is where most people actually ask, because you can reach an employee without their email address. The rules are the same as email, only shorter: a wall of text in the messaging panel never gets read.
The connection request note has a 300-character limit, so every word has to earn its place:
Hi [Name], I am applying for [Role] (req [ID]) at [Company] and your team is exactly where I want to be. [One specific, relevant fact about you]. Would you be open to referring me? Totally fine if not.
Once they accept, or by InMail:
Hi [Name], thanks for connecting. I am applying for [Role] at [Company], requisition [ID]. Briefly why I think I fit: [one achievement with a number] and [one skill the posting asks for]. Would you consider referring me? Happy to send my resume whichever way is easiest, and no worries at all if it is not something you can do.
Keep it to a short paragraph. Do not paste your resume into the chat, do not send voice notes, and do not follow a "hi" with a "just following up" an hour later. Ask once, give them the exit line, and let it sit. Employees get many of these, and the polite, specific, easy-to-decline ones are the ones that get answered.
Follow up once, after about a week, and then stop.
Hi [Name], just floating this back to the top of your inbox in case it got buried. Still very interested in [Role], req 12345. Completely fine if it is not something you can do. Thanks either way.
That is the entire message. Do not add new arguments, do not restate your qualifications, and do not send a third one. A second follow-up converts almost nobody and costs you a contact.
Silence is usually not rejection. Employees get a lot of these, and a referral takes real time and carries real internal risk. Assume they are busy, not hostile.
Referral forms usually include a free-text box asking why you recommend this person. Recruiters read it, and most of them are filled with something like "good candidate, strong skills", which adds nothing.
A useful referral comment does three things: states how you know the candidate, gives one piece of concrete evidence, and is honest about the limits of your knowledge.
Worked with [Name] for two years at [Company], where they owned [specific system or project]. They [specific outcome with a number]. Strong fit for the [team] role in particular. I have not worked with them on [area], so I cannot speak to that directly.
If you do not know the candidate personally, say so plainly rather than implying otherwise:
I have not worked with [Name] directly. I reviewed their profile and background against this requisition and think it is a genuine match, particularly [specific reason]. Referring on the strength of the profile rather than personal experience.
That last framing protects your credibility, which is the thing that makes your future referrals worth anything. Recruiters trust referrers who are precise about what they do and do not know far more than referrers who are uniformly enthusiastic.
The mass-sent template. Referrers identify these instantly. If the message would read identically to fifty other people, it will be treated as if it were.
"Any suitable openings". This hands the referrer your job search. They will not do it.
The long autobiography. Anything past about 150 words gets deferred, and deferred means forgotten.
Applying to a role you clearly do not meet. Referrers who submit weak candidates lose standing with their own recruiters, so they are protective about it, which is entirely reasonable.
Guilt or urgency. "Please, I really need this" and "responding today only" both make declining feel expensive, so people avoid the conversation entirely by not replying.
No easy out. Without an explicit permission to decline, a busy person's cheapest option is silence.
If cold messaging is not producing replies, that is not a template problem. It usually means you are asking people who never agreed to receive referral requests. On RefOpen, employees verify their employer with a company email address and opt in to review requests, so the message is landing with someone who has already said yes to being asked. Your wallet is refunded in full if no referral is submitted.
Four things: who you are in one line, the exact role and requisition ID, two or three achievements with numbers that map to the job description, and one sentence explicitly making it easy to decline. Attach your resume and keep the whole message under about 150 words.
Specific and plain. "Referral request: [Role title], req [ID]" works. So does leading with a real connection, such as "Referral request from a [University] alum". Avoid vague subjects like "Quick question" or "Opportunity", which read as marketing and get deleted.
Name the exact role, give two or three pieces of concrete evidence that map to the posting, attach your resume, and explicitly say it is fine to decline. Keep it short. The permission to say no is what most cold requests are missing.
Once, after about a week, in two sentences. A second follow-up converts almost nobody and costs you the contact. Silence usually means the person is busy, not that you have been rejected.
Keep it far shorter than an email. A connection request gives you 300 characters: name the exact role, one relevant fact about you, and one line making it easy to decline. Once connected, send a short paragraph with one achievement that maps to the posting and an offer to send your resume. Do not paste your resume into the chat or send a second follow-up within the hour.
State how you know them, give one concrete piece of evidence, and be honest about what you cannot speak to. If you do not know the candidate personally, say that you are referring on the strength of the profile rather than implying a working relationship.
Most often because the request is generic, does not name a specific role, or gives the reader no easy way to decline. It can also mean you are messaging people who never agreed to receive referral requests. Platforms where employees opt in to review requests remove that problem.