Tech recruitment cold email teardown: before and after
A typical tech recruitment cold email, what is wrong with it line by line, and a rewrite that an engineering leader would actually answer.
TLDR
- Most agency emails open with the agency, not the reason for reaching out.
- The rewrite opens on two real signals, offers specific proof and makes a small ask.
- Keep it under 70 words and make sure it could not be sent to anyone else.
I've sat on both sides of this email. In-house, I got pitches like the one below every week, and we turned almost all of them down. Later, building BD systems for a search firm, I learned what makes the other side reply.
Below is a typical tech recruitment cold email, then what's wrong with it line by line, then a rewrite.
This is a composite example built from common patterns, not a real agency's email.
The original
What's wrong with it
The subject line is a category, not a reason
"Top Tech Talent" is what every agency says. It tells John nothing about why this email is for him.
The first two lines are about Sarah
Her name, title, agency and every niche they cover. John has to read 40 words before anything relates to him, and most people stop at the preview.
No reason for reaching out today
Why now? Nothing in the email shows Sarah knows anything about John's company. It could be sent to anyone, which is exactly how it reads.
Claims without proof
"Extensive network", "pre-vetted", "proven track record". Engineering leaders skip these words because every agency uses them.
The ask is too big
A call about "hiring needs for 2026" is a meeting about nothing specific. Asking for a time slot in the first email adds pressure before there's any trust.
The rewrite
Let's say the signal is that John joined as VP of Engineering 70 days ago, and the company posted its first SRE role last week.
Why the rewrite works
- The subject is about his problem. Lowercase, specific and short. It reads like a colleague, not a campaign.
- The first line proves she did her homework. Two real signals: a new leader and a first hire in a new function.
- One relevant insight. First platform hires shape the team. It shows she understands the role, not just the keyword.
- Proof instead of claims. Two specific people with relevant experience, and they aren't on the job boards.
- A small ask. "Want me to send their profiles?" is easy to say yes to. The call comes after.
- Under 70 words. Easy to read on a phone between stand-ups.
A quick checklist for your next email
- Does the first line mention something true and recent about them?
- Could this email be sent to anyone else? If yes, rewrite it.
- Did you mention the stack, team or role in their words?
- Is there proof, like a specific candidate or a relevant placement, instead of a claim?
- Is the ask small enough to answer in one word?
Want the signals behind emails like this? Here are the 12 tech hiring signals worth tracking. Or get a free client hit list with the first message written for each company.
Want this running for your agency?
Get a free client hit list: 10 companies hiring in your niche right now, the hiring manager at each one, and the exact first message to send. Walked through on a 30-minute call.
Get my free hit list