Why do strong engineers ignore recruiting emails?

Because they are employed, paid at or above market, and not looking, and they receive several near identical messages every week. Most are sent by people who found them through a filter and have not read their work. After enough of those, the reader pattern matches on the first line and archives without reading, so the message never competes on merit.

What is a realistic reply rate for cold outreach to senior engineers?

Low enough that a cold search needs real volume to produce a handful of conversations. Filling a senior role from a standing start commonly takes five to seven weeks as a result. Warm introductions convert at a completely different rate because the trust question is already answered.

Does offering more money fix low response rates?

No. Opening with compensation signals that the number is the only argument available, and the senior engineers most able to judge whether it is a good number are the least likely to move for it alone. An honest description of the hard technical problem tends to work better.

What makes a senior engineer reply to a message?

It comes from someone they have reason to trust, such as a founder whose product they respect or a former colleague. It refers to the specific work they did. And it asks for something smaller than a job change, such as an answerable question about a real problem.

For founders

Why strong engineers ignore your outreach

Whether you get a reply depends on who the message came from, what it asked for, and the fact that the person reading it already has a job they like. The wording almost never decides it.

Zelcast

The engineers you most want are employed, paid well, and not looking, and they receive several near identical messages a week from people who haven’t read a line of their work, so your message is up against the effort of replying at all. What raises a reply rate is who the message comes from, evidence that you know what the person built, and asking for something smaller than a job change.

The person you are writing to

The typical reader is three years into a role they mostly like, they’re paid at or above market, their equity is vesting, and their calendar is full. They aren’t unhappy enough to run a search, the ordinary state for most developers in the Stack Overflow developer survey, and engaging with you costs them something: a call they have to take at lunch and a conversation they have to have with themselves afterward.

Against that, a generic message about an exciting opportunity gives them nothing to weigh.

What the inbox looks like

Strong engineers get contacted constantly, and the messages are interchangeable, from the opening line to the promise that this one is different. Most were sent by someone who found them through a filter and has never read their code or watched a talk they gave.

Once you’ve seen a hundred of these, you stop reading them individually. You pattern match on the first line and archive, and that’s the wall your message hits. Rewriting the subject line doesn’t get through it.

What gets a reply

It came from someone they have reason to trust. A message from a founder whose product they respect, or a person who worked with them, clears the wall immediately. It is why introductions land when outreach does not, and most of the reason we exist. The longer version of that argument is in the best engineers are athletes now.

It shows you know what they built, down to the specific thing: a system they wrote about, a talk they gave, a library nobody uses but is very good. It works because it’s expensive and doesn’t scale.

It asks for less. A specific question about a specific problem is answerable in three lines, and a job change isn’t. Plenty of good hires start as a conversation with no vacancy attached and turn into something a year later.

It says something true about the hard parts. Senior people are more attracted by an honest description of what is broken than by a list of perks. If your data model is a mess and the person you want has fixed one before, lead with that.

Things that do not work

Volume. Sending five hundred instead of fifty gets you more archives and a reputation among the people who talk to each other.

Compensation as the opening move. Leading with money reads as the only argument you have, and the people best able to evaluate the number are the least moved by it.

Urgency. A deadline on a life decision is a reason to say no, and everyone recognizes the tactic.

Flattery without specifics. Telling someone their background is impressive when the message could be pasted to anyone confirms that it was.

What this means for how you hire

If your plan for filling a senior seat is cold outreach at volume, expect it to be slow. It works, and it works best for companies with a brand that does the persuading.

Most teams are better off spending the same hours on fewer people, or borrowing relationships from someone who has them. Borrowing works because the engineers you want will take a call from a person they trust.

Common questions

Why don’t engineers respond to recruiters?: They are employed and content, and they receive several near identical messages a week from people who have not read their work. Replying costs them time and offers nothing they can evaluate.
What is a good response rate for cold engineering outreach?: Low enough that the arithmetic needs volume, and that volume is what stretches a cold search into weeks. A trusted introduction converts at a completely different rate because it clears the trust question first.
Does paying more fix the reply problem?: No. Leading with compensation reads as the only argument available, and senior engineers who can evaluate the number are the least moved by it.
What gets a senior engineer to reply?: Coming from someone they trust, showing you know the specific thing they built, and asking for something smaller than a job change.