I start from why someone would move, not what the role is called. I research the person first, what they've built, published, or shipped, and open with something specific to that, never a templated pitch. The message leads with a problem worth solving, not a req number. I run a short cadence: an opener tied to their work, a follow-up with a different angle like team or stack if there's silence, then a soft close after three touches instead of chasing. I favor warm entry points, mutual connections, shared alumni groups, conference talks, GitHub activity, so the first line already has a reason to exist. I track reply rate by message type and rewrite whatever underperforms.
Example: "I saw your talk on event-driven architecture last month. We're rebuilding our payments pipeline around the same pattern, thought the problem might interest you, worth 15 minutes?"
Insider read
Really testing: Whether the candidate personalizes outreach around the person's work instead of the job posting.
The tell: Juniors describe sending more InMails; seasoned recruiters describe rewriting the message after tracking which line got replies.
Follow-up: What's your actual reply rate on cold outreach, and how do you know?
Say thisI open with their work, not our req, and I measure reply rate by message variant.