Candidate outreach email templates: first touch, follow-ups and re-engagement
On this page
A candidate outreach email is a short, personal message to someone who has not applied, asking whether they would talk about a specific role. The ones that get replies name the role, give one real reason you are writing to this person, state the pay range and work setup, and ask for something small, such as a 15-minute call. Keep it under about 120 words, send no more than two follow-ups, and make the last one easy to answer with "not now".
These templates are for email. LinkedIn messages have their own character limits and conventions, covered in LinkedIn InMail templates for recruiters. To ask your network for introductions rather than contacting candidates directly, use the referral request email templates. Once someone replies, the how to sell the role guide covers the first call.
The anatomy of an outreach email that gets a reply
| Part | What it does | Weak version | Strong version |
|---|---|---|---|
| Subject | Gets it opened | "Exciting opportunity" | "Staff data engineer, Denver: your dbt talk" |
| Why them | Proves this is not a blast | "Your impressive background" | One specific thing they did, and why it matters for this role |
| The role | Lets them decide fast | "A fast-growing company" | Title, team, what they would own, in one sentence |
| Facts | Removes the first objections | Nothing, or "competitive" | Pay range, location or remote, level |
| The ask | Makes replying cheap | "Let me know your thoughts" | "Worth 15 minutes on Thursday or Friday?" |
| The exit | Keeps the relationship | Nothing | "If the timing is wrong, a one-word reply is fine." |
The "why them" line is where most outreach fails. If you cannot write one true, specific sentence about why this person, you have not read enough of their profile to be writing yet.
First-touch templates
1. Passive candidate, in-house recruiter
Subject: [Role] at [Company] — [the specific thing you noticed]
Hi [first name],
I read [specific: your write-up on X / the release notes for Y /
your talk at Z] and [one sentence on why it caught your attention
for this role].
I'm hiring a [title] for [team] at [Company]. The person in this role
will [the one outcome they would own in the first year].
- Pay: $[range] base [+ bonus/equity]
- Location: [remote in US time zones / hybrid in city, ___ days]
- Reports to: [name, title]
Would you be open to a 15-minute call next week, even just to hear
more? If the timing is wrong, a quick "not now" is completely fine.
[Your name]
[Title, Company]2. Agency recruiter, client not yet named
Agencies often cannot name the client before a conversation. Give enough that the candidate can judge the role, and say when you will name the company.
Subject: [Role], [city/remote], $[range] — confidential search
Hi [first name],
I'm [name] at [Agency]. I'm working on a [title] role for a [company
type and size, e.g. "300-person logistics software company"] and your
[specific experience] is very close to what they described.
What they need: [one sentence].
Pay: $[range]. Setup: [ ].
I can share the company name on a short call — I won't send your
details anywhere without your permission. Would [two times] work?
[Your name], [Agency], [phone]3. Hiring manager writing directly
Subject: Would you consider joining my team at [Company]?
Hi [first name],
I lead [team] at [Company]. I'm writing myself because [specific
reason — a project of theirs, a shared problem you are solving].
We're about to [the real challenge], and I'm looking for someone to
[own X]. Pay is $[range]; [setup].
I'd enjoy 20 minutes comparing notes, whether or not you're looking.
Would [day] work?
[Name]
[Title]Candidates tend to read a note from the person they would work for differently from a recruiter's, because it answers "who would my manager be?" before they ask. Keep the recruiter copied so scheduling does not stall.
Follow-up templates
Send follow-ups as replies in the same thread, so the original message is below. Each should add something new, not just "bumping this".
4. First follow-up (three to five business days later)
Hi [first name],
One more detail I should have included: [something new and concrete —
the tech stack, the team size, the flexible schedule, the fact the
last person in the role was promoted].
Happy to send the full job description if that's easier than a call.
[Your name]5. Final follow-up (a week after that)
Hi [first name],
I'll stop here so I'm not cluttering your inbox. If [role] isn't
right, or the timing isn't, no reply needed.
If you'd like me to keep you in mind for [type of role] later, just
reply "later" and I'll check back in [three / six] months.
[Your name]The "later" option gives passive candidates a way to stay in touch without committing to anything. Record it and actually follow up on the date you gave.
Re-engagement templates
6. Past applicant for a new role
Subject: A different role at [Company] that may suit you better
Hi [first name],
You applied for [old role] with us in [month/year]. We went another
way then, but I remembered [specific strength from their application
or interview].
We've just opened [new role], which [how it matches that strength].
Pay is $[range]; [setup].
Would you like to talk about it? If you've moved on happily, I
completely understand.
[Your name]7. Silver medalist (finalist who narrowly missed)
Subject: [Company] — we'd like to talk again
Hi [first name],
When you interviewed for [role] in [month], the team rated you very
highly, and it was a close decision. [Hiring manager] asked me to get
in touch as soon as something suitable opened.
It has: [new role], [one sentence]. Because you've already met the
team, we'd suggest [shorter process, e.g. one conversation with X].
Is this worth a call this week?
[Your name]Only say the decision was close if it was, and only offer a shorter process if the hiring manager has agreed to it. The interview debrief template gives you a written record of why finalists were not chosen, which is exactly what you need before sending this.
8. Candidate you placed or worked with before (agency)
Subject: Checking in — and a role I thought of you for
Hi [first name],
It's been [time] since you started at [company]. I hope [something
specific they cared about] has worked out.
I'm not assuming you're looking, but I'm working on [role] and it
lines up with what you told me you wanted next: [their words].
$[range], [setup].
If it's not for you, I'd be grateful for a name or two of people who
might be interested.
[Your name]Check your client agreements before approaching someone you placed. Many include terms that restrict an agency from recruiting people it placed with that client, often for a set period.
9. Referred candidate
Subject: [Referrer name] suggested I get in touch
Hi [first name],
[Referrer full name] mentioned that you [what they said] and that you
wouldn't mind hearing from me.
I'm hiring a [title] at [Company]: [one sentence]. $[range], [setup].
Would a short call be useful? If not, no problem at all — and I won't
mention to [referrer] either way unless you'd like me to.
[Your name]Only use the referrer's name if they agreed you could. The last line matters: some candidates hesitate to reply if they think their answer will be reported back to a colleague.
Personalization that takes two minutes, not twenty
Good outreach is specific, but it does not need a research project per person. Look in this order and stop as soon as you find one real thing:
- What they built or shipped. A project, a portfolio piece, a published paper, a public code repository, a product they launched.
- What they wrote or said. A post, a talk, a podcast appearance, an answer in a community forum.
- A pattern in their career. "You've joined three companies at about 50 people and stayed through their growth", when the role is at that stage.
- A specific skill match. Named systems or credentials the role actually requires, not a list of keywords.
If you batch outreach, write the personal line for each person first, then paste in the rest of the template. It keeps you from sending the template with a weak line bolted on.
Consent, privacy and sending rules
- Candidates in the EU or UK. When you collect someone's personal data from a source other than them, GDPR Article 14 generally requires you to give them information about the processing, including the source, and where you use the data to contact them, at the latest at the time of the first communication (GDPR Article 14(3)). Many recruiters add a short line and a link to their candidate privacy notice. This is a summary, not legal advice; check with whoever owns privacy at your organization.
- Do not guess email addresses at scale. Sending to guessed addresses produces bounces that hurt your domain's sending reputation, and the ones that land can feel intrusive.
- Honor "no". Record a decline or an unsubscribe request in your ATS or CRM the same day so a colleague does not email the same person next week.
- Pay ranges. Several states and cities require pay ranges in job postings. Even where outreach emails are not covered, using the same approved range avoids contradictions.
Tracking what works
Track replies per template, not just in total. A simple sheet with the template used, the personal line, the send date and the outcome (no reply, not interested, later, call booked) is enough. After 30 or 40 sends of one template you will usually see whether the problem is the subject line (few opens, if you can see them), the first line (opens but no replies), or the role itself (replies that all say no for the same reason). Change one thing at a time.
When a reply turns into a call, the notes from that first conversation are what your next message is built on. If you use a transcription tool such as Interview Signal on that call, tell the candidate at the start; the consent guide has a line to read aloud.
Questions people ask
How many follow-ups should a sourcing email sequence have?
Two follow-ups after the first email is a common and reasonable limit, spaced several business days apart, with the last one saying clearly that you will stop. More than that tends to read as automated and can damage your employer brand with people you may want to hire later.
Should I put the salary in a cold outreach email?
If you have an approved range, yes. Pay is one of the first things a passive candidate wants to know, and in places with pay transparency rules you may be expected to share it anyway. A range in the first email saves a call with someone the role could never suit.
Where should I get a candidate's email address?
From sources where the person made it available for professional contact, such as a personal website, a public profile, a past application to your company, or a referral who asked first. For candidates in the EU or UK, GDPR generally requires you to tell them where you got their data no later than your first message.
What subject line works best for recruiting emails?
A specific one: the role or the thing you noticed about their work, in plain words. Subject lines that look like marketing, or that say 'Opportunity' and nothing else, are easy to ignore. Keep it short enough to read on a phone.