Sourcing without spam: how to write outreach engineers actually read

Look at the inbox of any senior backend engineer in Bengaluru on a Monday morning. Between six and fourteen recruiter messages, all opening with 'Hope you are doing well', all promising a 'great opportunity', almost none mentioning a company name in the first line. The reply rate on this outreach is now below 3% at most firms we benchmark. Ten years ago it was over 20%.

The market didn't change. The signal did.

Engineers still change jobs. The average tenure at growth-stage tech companies in India is 28 months, roughly what it was in 2019. What changed is the effort-to-signal ratio in the messages they receive. When every message looks the same, none of them are worth replying to, and the good ones lose because they are drowning in the bad.

Four rules we hold every outreach to

• Name the company in the subject line. Anonymity signals the recruiter is fishing, not hiring.
• One sentence on why this person specifically — a paper, a repo, a talk, a company they scaled through. Generic flattery is worse than none.
• The stack and the problem, not the perks. Senior engineers screen for the work.
• A single question, not a calendar link. Optionality respects the reader; a Calendly link demands their time before they've decided.

What good looks like

The best outreach we've written in the last quarter was 74 words long. It named the CTO, referenced a specific migration the candidate had led at their previous company, described the equivalent problem in the new role in one sentence, and asked a single question about their current tooling. Reply rate on that campaign was 41% against a market baseline of 4%.

You cannot fake this at volume. That is the point. Outreach that works costs the recruiter time, and the recruiter's time is what the candidate is actually evaluating when they decide whether to reply.

"If you would not be willing to send the same message to your best friend from your last team, do not send it to a stranger."