A cold email to a recruiter for a full stack developer role gets replies when it names your exact stack, proves it with one measurable result, and asks for one small next step, in under 90 words. Anything longer gets skimmed or deleted. Below is the template, the reason behind each line, and the follow-up cadence that turns silence into an answer.
You have applied to forty full stack postings this month. You got two replies, both rejections, one auto-generated. Meanwhile someone with a weaker resume is booking screens, because they stopped waiting on the queue and started emailing a human.
Here is why. Full stack is one of the most oversaturated titles on any board. A recruiter scanning three hundred "Full Stack Developer" resumes for one React/Node opening cannot tell you apart from the next one unless you tell them, in their inbox, why you are different. Cold outreach is not a trick. It is a shortcut around a broken queue.
Why does a full stack developer need a cold email strategy?
Because the title is a catch-all, and the ATS treats every version of it the same. A recruiter searching "full stack" gets people who touched React once, backend-heavy engineers with a thin frontend, and people who ship both ends of an app in production. One company's "full stack" means React, Node and Postgres. Another's means Angular, Java and a legacy Oracle backend.
That ambiguity cuts two ways. Recruiters pattern-match keywords against the req instead of reading closely. So your email has to do the pattern-matching for them, in the subject line and the first sentence. And you have to prove range without sounding vague about everything, which means leading with the specific combination you have shipped, not every tool you have touched.
Timing matters too. A posting that has been live a few days can already have a shortlist forming. If you only click "Apply," you compete with everyone in the first wave. An email that lands the same day the req opens skips that line.
Summary: the title is too generic to help you, so a direct, specific email does the differentiating the resume cannot.
Which full stack cold email template should you use?
There are two common versions of this email. They share the same core: stack, one result, one easy ask. They differ in who reads it and how the ask is framed. Pick based on the reader.
| Variant | Best for | Subject line style | Proof emphasis | The ask |
|---|---|---|---|---|
| Cold outreach template (recruiter or hiring manager, either one) | Cases where you are not sure who owns the req, or you are emailing an engineering manager at a smaller company | Stack, years of experience, company and team | Business result for recruiters, technical decision for engineering managers | "Consider me, or point me to whoever is screening it" |
| Cold email template (named recruiter, specific posting) | A recruiter you have identified who is working a live full stack req | Stack plus company and product area, in five to eight words | One shipped result tied directly to the stack in the posting | Binary choice: a 10-minute call, or you apply through the portal and flag your resume to them |
| C2C full stack contractor version | Vendor and recruiter outreach when you contract through your own corp | Same stack-first style | Same proof block | Same, but availability, rate flexibility and work authorization come first |
You do not need two separate emails in practice. The template below combines both. Use the "consider me or redirect me" ending when you are unsure who owns the role. Use the binary call-or-portal ending when you know the recruiter.
What does a full stack developer cold email look like?
It is short, specific and ends with one ask. Swap in your real stack and real numbers. Do not leave placeholders that read like placeholders.
Subject: Full stack (React/Node), 4 yrs, open to [Company]'s [Team/Product] role
Hi [First name],
Saw [Company] is hiring a Full Stack Developer for [specific team or product]. I have spent [X years] building full stack features end to end: React/TypeScript on the front end, Node/Express APIs, Postgres or MongoDB underneath, shipped to production, not just a portfolio repo.
At [Current or last company], I [one concrete result tied to the stack, e.g. rebuilt the checkout flow in React and cut page load time by rewriting the API layer into a cached GraphQL gateway].
Worth a 10-minute call this week? Or if you are not the right person, point me to whoever is screening it. Resume attached.
[Your name]
[Phone] · [LinkedIn] · [Portfolio or GitHub]
Look at what is missing. No "I hope this email finds you well." No life story. No paragraph about your passion for coding. Recruiters read a huge volume of these. Every sentence that is not proof or a request is a reason to close the tab.
Three things make it work:
- The subject line names the stack and the company. It reads as relevant before it is opened.
- One shipped outcome replaces a skills list. Recruiters have seen every "proficient in JavaScript, Python, SQL" line and trust results instead.
- The close is easy to answer. A binary choice or a redirect costs the reader almost no effort, unlike "let me know your thoughts."
Summary: name the stack, prove it with one number or result, ask for one action, then stop typing.
How do you write a subject line recruiters actually open?
Put the real keywords in it and skip the clever hook. The subject line filters before the email is read. It is also how the email gets found later, because recruiters search their inbox for "full stack" or "React."
- Lead with the stack, not your name. "Full Stack (MERN) developer, open to [Role/Team]" beats "Application from [Your Name]."
- Add years of experience if it is a strength. Recruiters filter by seniority fast, so "5 yrs full stack" saves them a click.
- Name the company when you found the req yourself. "Saw the [Company] Full Stack opening" signals you did not blast a template.
- Never open with "Quick question" or "Following up." These phrases read as spam before the email is opened.
For more tested options, see cold email subject lines that actually get recruiters to open.
What should you personalize and what can you reuse?
Keep one block fixed and change one line. That is how you send dozens a week without it feeling like dozens of custom letters.
- Stack summary and measurable result: keep fixed. This is your proof block. Reuse it word for word once it is tight.
- Company, team and posting reference: change every time. Generic emails get deleted fastest. This line makes it feel researched.
- Subject line: swap the company name. It takes seconds and decides whether the email gets opened at all.
- The ask: keep consistent. One clear ask is easier to act on than a vague one.
Ninety percent stays the same. The ten percent that changes is the part the reader cares about most.
Should you email the recruiter or the hiring manager?
Match the reader. Recruiters and hiring managers want different proof, so the same template needs a different emphasis.
- Large company with a recruiter: email the recruiter first. They filter volume, so lead with keywords and years of experience that match the req exactly.
- Startup or small team: email the engineering manager or team lead. They care less about title-matching and more about whether you can talk through a real technical decision, so make your one result technical.
- Both identifiable: send to both, staggered by a day. If the recruiter is quiet after a couple of days, the manager email is a second shot at the same req, not a duplicate ask. Do not send identical copies to several recruiters at the same company, because they talk to each other and it reads as spam.
- Never use careers@ or hr@. Those route into the same queue as your ATS application and defeat the point of going direct.
Summary: business impact for recruiters, technical depth for engineering managers, and always a named human.
How do you find a recruiter's email before you send?
- Check the posting first. Many listings on LinkedIn or career pages tag the recruiter directly.
- Look at the engineering or About page. Technical recruiters and talent partners are often listed there.
- Work out the email pattern. Most companies use firstname.lastname@ or firstname@. A press release or another employee's listed address confirms the format.
- Verify the address. A bounce wastes the one first impression you get. Use a verification tool.
- Warm it up on LinkedIn. If the recruiter posted about the role, comment or connect first, then email twenty-four hours later.
The full walkthrough is in how to find any recruiter's email address.
When is the best time to send a cold email to a recruiter?
Send it the same day the posting goes live, and send it early in the week. Recruiters triage inboxes in batches, usually first thing in the morning and again in the late afternoon once interviews wrap. Tuesday or Wednesday mornings tend to outperform Monday, when weekend backlog floods the inbox, and Friday, when attention has moved on.
Freshness beats everything else. Emailing about a posting already buried under hundreds of applications is a weaker version of the problem the ATS created. If you are sending within hours of the req opening, your name is one of the first, not one of two hundred.
How many times should you follow up, and what do you say?
Follow up twice, then stop. One email rarely closes the loop, and a short follow-up is expected in recruiting. Just never ask the same question twice.
- Wait a few business days. Three to four business days is the sweet spot. Faster feels pushy, slower loses the thread.
- Reply in the same thread. The context stays visible. Do not start a new email.
- Keep the first follow-up to two or three sentences. Example: "Still interested in the [Role] opening if it is active. Happy to send anything else that is useful. No worries either way."
- Send the second follow-up about a week later, only if the posting is still live. Add one new piece of proof: a GitHub link, a deployed demo, a recent project, a relevant post. Give them a reason to reopen the thread, not just bump it.
- Switch channels on the final attempt. A short, specific LinkedIn message about the same role sometimes breaks through where email went quiet.
- Stop after two follow-ups. A third message works against you. If the posting vanishes from the careers page, take that as your answer. It may have been a ghost job all along.
More on tone and spacing in how to follow up with a recruiter without being annoying.
What mistakes kill full stack cold emails?
Most outreach fails for boring, fixable reasons. Cold email itself is not the problem.
- Leading with your background story. The recruiter needs to know in the first line whether you are relevant.
- Listing every technology you have touched. A wall of acronyms reads as unfocused. Pick the stack that matches the req and lead with it.
- Attaching a resume that does not mirror the posting. If the req says React and Node, your top bullets should say React and Node, not Vue and Django from two jobs ago. If your email says React/Node but your resume talks Angular/.NET, that reads as confusion or padding. Keep the format clean as well, since formatting affects parsing once they open it.
- Sending to roles that are not really full stack. Some "full stack" postings are secretly backend-heavy or frontend-heavy. A five-minute skim of the description prevents a mismatched pitch.
- Using adjectives instead of a result. "Strong problem solver with a passion for clean code" says nothing. "Rebuilt the checkout flow, cut page load time, shipped it solo" says everything in one line.
- Burying the ask. If the recruiter has to hunt for what you want, they skip it.
- Emailing a dead req. Check whether the listing is fresh or reposted before you spend an email on it.
How should C2C full stack contractors change the template?
Lead with availability and rate flexibility in the first line. C2C recruiters filter for compliance and bandwidth before skill. If you contract through your own corp, state your visa or work authorization status up front, since that is often the first filter on a vendor hotlist.
The stack proof and the closing ask stay the same. What changes is the market. C2C moves on vendor hotlists and submission speed, a different game from direct W2 outreach. For the vendor-side version of the email, see this sample C2C submission email to a vendor.
What should you do after a recruiter replies?
Prepare for the technical screen right away. A reply asking for a call or more detail is usually the point where the screen gets scheduled. Full stack interviews tend to probe both ends of the stack unevenly depending on the team. Going in blind on what to expect wastes the advantage your outreach just bought you. Review what full stack interviews cover before you schedule the call, not after.
How do you scale cold outreach without becoming a spam operation?
Remove the research bottleneck, not the personalization. The template is not the failure point. Volume is. A handful of personalized emails a week is not enough to matter. Dozens a day by hand is unsustainable and produces sloppy, obviously mass-blasted copies.
The slow parts are finding the right recruiter, checking the posting is still live, and tracking who you already contacted. Automate those, so your time goes into the ten percent that changes per email. If you want the mechanics, read how to automate recruiter outreach without getting marked as spam.
This is the same problem GiraffyReach was built around. It detects fresh full stack postings as they go live and pairs auto-apply with recruiter cold outreach, so the email above goes out while the req is still new, not after the first wave of applicants has buried it. Be first, or be forgotten. For a title as crowded as full stack, that is just how the hiring queue works.