Blog

Cold Email for Recruiting Senior Engineers

March 2026

Senior engineers get 10-15 recruiting messages per week on LinkedIn. Most of them look identical: "exciting opportunity," "fast-growing startup," "competitive compensation." They all blur together, and almost all of them get ignored. The average response rate for recruiter InMails is around 10-15%. Top-tier candidates respond to even fewer.

If you want to stand out, you have to break every pattern those other messages follow.

What engineers hate about recruiter messages

The biggest complaint is that the message could be sent to anyone. "Your background is impressive" means nothing — you'd say that to every engineer on LinkedIn. The second complaint is hiding the details. When you write "competitive salary" instead of a range, or "exciting product" instead of what the product actually does, you're asking them to spend time on a call just to learn basic information. Senior engineers value their time too much for that.

The third complaint: not reading their profile. If someone's been at the same company for four years and just got promoted, they're probably not looking. If they recently changed their headline to "open to opportunities," they are. If their GitHub shows heavy Rust contributions and you're pitching a Java role, you've wasted both of your time.

What actually gets replies

Lead with what makes the role interesting from a technical perspective. Engineers don't care about your company's mission statement. They care about what they'd build, what the technical challenges are, and who they'd work with. Be specific. "You'd own the real-time data pipeline serving 2M events/second" is compelling. "You'd work on our data infrastructure" is not.

Include the salary range. Including comp information in the first message increases response rates by 30-40% according to LinkedIn's own recruiting data. If you can't share the range, at least share the level and equity structure.

Sample LinkedIn message

This is the kind of message Simpler Outreach generates for recruiting. Scenario: reaching out to a senior backend engineer who's been contributing to open-source distributed systems projects.

Hi [Name] — saw your recent contributions to [open-source project], particularly the work on the consensus layer. That's a hard problem and your approach to [specific PR or feature] was well thought out. I'm hiring for a senior distributed systems role at [Company]. The short version: you'd own the real-time event processing pipeline that handles about 3M events/sec across 40+ microservices. Team of 6, all senior. Stack is Go, Kafka, and ClickHouse. Comp is $220-260K base + equity (0.15-0.25%). Remote-friendly, with the core team split between SF and London. I know you probably get a lot of these messages. If this doesn't match what you're looking for right now, totally understand. But if it's interesting, I'd be happy to share more about the technical architecture — no sales pitch, just the details. [Your Name]

Why this works

The opener references a specific open-source contribution. This alone puts you in the top 5% of recruiter messages. The role description is concrete: event volume, team size, tech stack. Salary and equity are upfront. The close respects their time and offers something of value (technical details) rather than asking them to "hop on a quick call."

Notice the length — it's longer than a typical recruiter message, but every sentence carries information. Engineers don't mind reading if every word is useful. They mind reading fluff.

Timing and volume

Don't batch-send on Monday morning when everyone's inbox is full. Tuesday through Thursday, mid-morning works best. Send to 15-20 highly targeted candidates per week rather than 100 generic ones. Personalization at this level takes 5-10 minutes per message, but a 30% response rate on 20 messages beats a 5% rate on 100.

Need recruiting outreach that senior candidates respond to?

Generate your message

Simpler Outreach writes recruiting messages that reference the candidate's actual work and present the role with the specifics they want to see. One-time payment, use it forever.