A passive candidate, someone not actively job-searching, doesn't owe anyone a reply. That's the entire game: every message competes not against other job offers but against the very real option of simply ignoring it. Generic outreach loses that competition almost every time. Specific, respectful, low-friction outreach wins it often enough to matter. The difference between the two isn't subtle, and it's almost entirely under a recruiter's control.
Reference their actual, specific work
A message that opens with 'I came across your profile and was impressed by your background' tells a candidate nothing except that a template was used. A message that references the specific system they built, the talk they gave, the open-source project they maintain, or the post they wrote, and says something concrete about why it's relevant, signals that a real person looked at real work. That difference alone accounts for most of the reply-rate gap between outreach that works and outreach that gets deleted.
Lead with the problem, not the title
Someone who isn't job-searching doesn't care what the title is. They care, if they care at all, about whether the problem described is more interesting than what they're already working on. Outreach that opens with a job title and a list of responsibilities reads as a form to fill out. Outreach that opens with the specific, hard problem the role exists to solve reads as an invitation to think about something new, which is a fundamentally different, and far more effective, thing to offer a happily employed engineer.
- Describe the actual technical problem in one or two concrete sentences, not a title and a bullet list of responsibilities.
- Name the scale, stakes, or constraint that makes the problem genuinely hard, that's what earns curiosity.
- Skip company boilerplate in the first message entirely, it can come later once there's real interest.
Use warm intros over cold messages whenever possible
A message from a mutual connection, a former colleague, or someone in the same technical community converts at a rate a cold message from an unknown recruiter rarely matches, because it arrives with borrowed trust attached. Building and maintaining a real network of warm paths into the AI talent pool, rather than relying purely on cold outbound, is one of the highest-leverage investments a hiring function can make, precisely because it compounds: every good hire and every well-treated candidate becomes a future warm path to someone else.
Respect their time with a small, fast first step
Asking a passive candidate to block 45 minutes for a first call is asking them to treat an unsolicited message with the same weight as a scheduled meeting they chose to accept. A better first ask is small: a short async question, a five-minute call, or simply 'would this be worth 15 minutes to hear more.' Momentum matters more than thoroughness in the first exchange, because the goal of message one is only to earn message two.
What reliably kills the response rate
| Mistake | What it signals |
|---|---|
| Generic, mass-sent template | This is a numbers game and I'm one of a thousand recipients |
| Vague role description ('exciting opportunity') | There's nothing specific enough here to evaluate |
| Long process demanded before any real conversation | This company doesn't value my time the way it's asking me to value theirs |
| No acknowledgment they weren't looking | This outreach was written without any thought for who's receiving it |
