Recruiting outreach that candidates answer

The best candidates already have jobs, full inboxes, and a finely tuned filter for the phrase 'exciting opportunity.' Recruiting outreach fails for the same reason sales outreach fails — it reads like it was sent to a spreadsheet, because it was. The fix is also the same: find the right people precisely, then write to them specifically.

Sourcing is a search problem before it's a messaging problem

A reply rate is capped by list quality. If the list is 'everyone with the title Software Engineer within 50 miles,' no subject line can save it. Describing who you actually need — 'backend engineers who've worked on payments infrastructure and contributed to open source' — and searching on that description, across profiles and code rather than titles alone, produces a list short enough to personalize and strong enough to be worth it.

The message: five sentences, one honest hook

1. 1Open with the specific thing that made you reach out — a repo, a talk, a system they built. It must be true and it must be theirs, not their employer's.
2. 2Say what the role actually is in one plain sentence. 'Senior backend on the payments team' beats 'a unique opportunity with a dynamic culture.'
3. 3Give the one detail that differentiates: the problem, the scale, the comp range, the team. Pick your strongest card and play only that one.
4. 4Address the obvious objection preemptively — usually 'why would I move?' A sentence of honest context outperforms a paragraph of superlatives.
5. 5Close with a low-stakes ask: a 15-minute call, no process, no commitment.

Channel and follow-up

Personal-adjacent channels outperform the recruiter-saturated ones. A verified work email with a thoughtful note lands better than the fifteenth InMail this week. Follow up exactly twice, spaced days apart, adding one new piece of information each time — then stop. Candidates remember restraint; the ones who say 'not now' become the warm pipeline for your next search if the first touch respected their time.

Track replies, not sends

A sourcing operation that reports 'messages sent' is measuring effort. Reply rate per segment tells you whether the list was right; accepted-call rate tells you whether the message was. When either drops, the answer is almost never 'send more.'