Fwalla

Recruiter Outreach Email Examples for Every Situation

Twelve real examples across cold intros, warm intros, layoffs, career pivots, and follow-ups. Copy, adapt, send.

Twelve real examples of recruiter outreach emails — each one used against a specific situation. Copy the one that matches your case, swap the bracketed fields, and send. Every example below is written for a job seeker reaching out to a recruiter, not the other way around.

1. Cold intro — specific role you found

The single highest-converting pattern. Name the exact req in the subject.

ExampleSubject: Interested in your Senior Backend Engineer req — 6 yrs Go Hi Priya, Saw Ramp is hiring a Senior Backend Engineer on the Payments team. I'm a Backend Engineer at Plaid with 6 years of Go and distributed systems experience — the shape of the role lines up closely with what I've been doing. Two things that felt relevant: – Rebuilt Plaid's ACH pipeline for 3x throughput at half the p99 latency. – Led on-call rotation for a service moving $180M/day. Resume attached. Would a 15-minute intro any afternoon this week or next make sense? Thanks, Alex Chen 415-555-0182 · linkedin.com/in/alexchen

2. Cold intro — company only, no open req

ExampleSubject: Backend Engineer candidate for Infra at Vanta Hi Marcus, I've been following Vanta's Infra team — the recent posts on your platform migration are exactly the kind of work I want to be part of. I'm a Senior Backend Engineer at Segment (5 yrs, Go + Postgres) and would love to be in your loop when a req opens up. Quick snapshot: cut a hot-path service's p99 from 340ms to 42ms this year. Resume attached. Happy to do a short intro whenever your team's next hiring window lands. Thanks, Sam Rivera

3. Warm intro — mutual connection

ExampleSubject: Jamie Ortiz suggested I reach out re: iOS team Hi Dana, Jamie Ortiz mentioned you're the person to talk to about iOS openings at Figma. I'm a Senior iOS engineer at Instacart (7 yrs Swift, led the checkout redesign that increased conversion 18%). Would you have 15 minutes in the next couple weeks? Resume attached in case it's useful up front. Thanks, Priya Nair

4. Post-layoff

Own the situation in the first line. Recruiters have seen thousands of layoff emails in the last two years — the ones they respond to are direct and specific.

ExampleSubject: Staff Data Engineer — impacted by Twilio RIF, targeting Databricks Hi Rachel, I was part of the recent Twilio reduction and am now actively looking. Databricks is at the top of my list, especially the Lakehouse Storage team. Background: 9 years as a Data Engineer, most recently owning Twilio's event pipeline (~2M events/sec, 4 nines SLA). Attaching resume. Available for a call this week — mornings PT are best. Thanks, Jordan Lee

5. Career pivot

ExampleSubject: Pivoting into ML engineering — infra background Hi Ken, I'm transitioning into ML engineering from platform infra, and Anthropic is one of the teams I'd most like to join. The strongest overlap: I've spent the last three years building the GPU training platform at Cruise (2k+ H100s, uptime SLOs, cost dashboards). Since March I've been working through the FastAI course and shipped an OSS eval harness (github.com/ryanchow/evals-lite). Would a short call to see if there's a fit make sense? Thanks, Ryan Chow

6. Referral request (not the recruiter — the hiring manager)

Sometimes it’s more effective to skip the recruiter and reach the person who actually reads resumes. Different tone, same shape.

ExampleSubject: Interested in the Growth Eng role on your team Hi Elena, I saw you're the hiring manager for the Growth Engineer role at Notion. I'm a Full Stack Engineer at Airtable (5 yrs) and wanted to reach out directly rather than through the general pipeline. The overlap that felt strongest: I ran the onboarding activation experiments at Airtable that took D7 retention from 41% → 54% over the last two quarters. Resume attached. Would a short intro make sense, or should I go through the standard application first? Thanks, Chris Park

7. Following up after an application (no response)

ExampleSubject: Following up on my Senior PM application — Payments team Hi Wei, I applied for the Senior PM role on Stripe's Payments team last week (ref #48213). Wanted to send a short note directly since roles at this level tend to move fast. Two things I'd bring that felt on-point: – Owned the pricing rollout at Square that hit $22M ARR in year one. – Led a payments compliance program (SOC2 + PCI L1) that shipped in five months. Happy to send any additional context or hop on a 15-min call. Thanks, Sam Nakamura

8. Following up after an interview (thank-you + nudge)

ExampleSubject: Thanks for today — one follow-up on the caching question Hi Priya, Really enjoyed the conversation this morning. Wanted to follow up on the caching question — I sketched out the LRU+TTL approach we discussed and wrote up the tradeoffs vs a write-through cache here: [link]. Excited about the team and the roadmap you described. Let me know if any next steps or additional info would help. Thanks, Jordan Kim

9. First follow-up (no response, day 4–5)

Reply to your own original email so the recruiter sees full context. Do not rewrite the pitch.

ExampleHi Priya, Bumping this in case it slipped past. Still very interested in the Senior Backend Engineer role — happy to send anything else that would help. Thanks, Alex

10. Second follow-up (no response, day 10–12, final)

ExampleHi Priya, Last note from me on this thread — if the timing isn't right, totally understand. If you'd rather I check back in a quarter, or if there's someone else on your team a fit like mine would land better with, I'll follow your lead. Thanks either way, Alex

11. Response to a recruiter’s cold outreach (interested)

ExampleHi Rachel, Thanks for reaching out — the Staff SRE role sounds interesting. A few quick questions before we schedule: – Comp band for Staff SRE (base + equity)? – Remote-friendly, or hybrid to a specific office? – What's the on-call rotation look like day-to-day? If those work on my end, I'm free Tuesday or Thursday afternoon PT for a 30-min intro. Thanks, Alex

12. Response to a recruiter’s cold outreach (not now, keep the door open)

ExampleHi Rachel, Thanks for reaching out — the role sounds interesting but the timing isn't right on my end (just started a new project I want to see through). I'd love to stay in touch. Feel free to send anything new that opens up on the Payments team in Q4, and I'll do the same. Thanks, Alex

What these examples have in common

Every one names a specific role, team, or context in the first line. Every one has one concrete result with a number. Every one ends with a clear, low-friction next step. If your email is missing any of those three, it will underperform.

How to adapt these examples without sounding templated

  • Change the second sentence, not the first. The first line is the pattern; the second line is where you insert something recruiters can only get from your specific background.
  • Replace vague phrases with numbers. “improved performance” → “cut p99 latency from 340ms to 42ms.”
  • Read it out loud. If it sounds like a form letter, it reads like one too.

Automate the templates above. Free while you job-search.

Fwalla personalizes templates like these per recruiter, per role, and sends them from your own Gmail on a schedule that protects deliverability. Set it up once, wake up to replies.

Start free with Gmail
Related guides