How can a Technical Recruiter write an InMail to a passive software engineer that actually gets a reply?

Writing an InMail to a passive software engineer that actually converts requires dropping the corporate fluff and respecting their time. Engineers get dozens of generic pitches a week; to stand out, you need to sound like a human who actually understands what they do.

Here is a step-by-step framework to write InMails that get replies, followed by a high-converting template.

Key Rules for Engineering InMails

• Lead with the tech stack, not the company prestige: Brand name helps, but what actually hooks a developer is what they will be building and the tools they will use.
• Be transparent about compensation: Mentioning a salary range or remote/hybrid flexibility upfront drastically increases response rates because it removes the biggest guessing game.
• Keep it short and punchy: If they have to scroll on mobile, you've already lost. Aim for under 125 words.
• Ditch the fake personalization: Don't compliment a generic blog post they wrote five years ago unless it directly ties to the role. Instead, reference a specific technical challenge your team is solving.

The Anatomy of a High-Converting InMail

1. The Hook: A casual, direct opening mentioning how you found them (or why their background caught your eye) combined with immediate context.
2. The WIIFT (What's In It For Them): The core technical challenge or stack, plus flexibility/compensation.
3. The Low-Pressure CTA: A casual question instead of a rigid "15-minute call request."

The Template

• Subject Line: Quick question re: [Tech Stack/Role] at [Company] — or keep it blank/ultra-short (e.g., Engineering at [Company]).
• Body:

Hi [Name],

Reached out because your background scaling [mention specific tech, e.g., distributed Go microservices] at [Current Company] caught my eye.

We’re growing the backend team at [Your Company] to tackle [one cool technical challenge, e.g., real-time data streaming for 10M+ daily users], primarily using [Tech Stack: Go, Kafka, Kubernetes].

The role is [Remote / Hybrid in City], and the comp range is [X - Y + equity].

No worries if you're happy where you are, but if this sounds like an upgrade, are you open to a quick chat next week?

Best,
[Your Name]

Would you like me to help you tailor this template for a specific open role, or do you want strategies on how to source and filter the right passive profiles first?

A passive software engineer usually ignores recruiter InMails for one reason: the message feels like work for them and value for the recruiter. The goal is not to “sell the job” in the first message — it is to earn a reply. LinkedIn’s own guidance emphasizes short, personalized messages, a clear reason for reaching out, and starting a conversation rather than sending a job description.

A strong InMail has five parts:

1. Write a subject line that earns the open

Avoid:

• “Exciting opportunity”
• “Senior Software Engineer Role”
• “Are you open to new opportunities?”

Better:

• “Your work on distributed systems caught my eye”
• “Quick question about your backend experience”
• “Thought your [specific project] was interesting”
• “Reaching out about [technical area]”

The subject should feel like a human noticed something specific, not a recruiter blast.

2. Prove you know who they are

Weak:

“Your background looks like a great fit for an exciting opportunity.” Every engineer has received this.

Strong:

“I noticed you’ve been working on Kubernetes infrastructure and developer tooling at [Company]. The scale of the systems you’re building stood out.” Mention:

• A technology they use
• A project they built
• An open-source contribution
• A talk/blog/post
• A career move that makes sense

3. Give the “why this role” in engineer language

Engineers generally care less about “amazing culture” and more about:

• Technical challenges
• Ownership
• Architecture decisions
• Team quality
• Product impact
• Growth
• Compensation clarity

Instead of:

“We have an exciting opportunity at a fast-growing company.” Try:

“The team is rebuilding our event-processing platform from the ground up, owning architecture decisions around Kafka, Go, and distributed systems.”

4. Reduce the commitment

Don’t ask:

“Can you send me your resume?” Ask:

“Would you be open to a quick conversation to see if this is interesting?” or:

“Worth sharing a few details?” The first reply should be easy.

5. Make it short

A passive engineer may read your message between meetings. A concise InMail is more likely to get attention. LinkedIn recommends keeping messages brief and avoiding long job descriptions.

Example InMail

Subject: Your distributed systems work caught my eye

Hi Alex,

I came across your background while looking for engineers who have worked on high-scale backend systems. Your work on [specific technology/project] at [Company] stood out.

I’m recruiting for a Senior Backend Engineer role at [Company] where the team is solving similar problems around [technical challenge]. You’d have ownership over architecture decisions, not just implementation.

I know you may not be looking, but would you be open to a 15-minute conversation to compare notes and see if it’s worth exploring?

Either way, appreciate the work you’re doing.

— [Name]

Follow-up if they don’t respond

Wait about a week, then send something shorter:

Hi Alex — just resurfacing this in case it got buried. I know you’re probably busy, so no pressure. Happy to send over a few details about the team/project if it’s useful. The biggest mistake is treating passive candidates like applicants. Treat them like respected professionals who already have options. The InMail should answer: “Why me? Why this? Why now?” within a few seconds.

I can also provide a few templates specifically for Staff Engineer, FAANG engineer, startup engineer, or hard-to-reach backend/platform candidates if useful.

Writing an InMail to a passive software engineer that actually converts requires ditching the standard "I have an exciting opportunity" copy-paste template. Engineers get dozens of pitches a week, can smell generic outreach from a mile away, and value clarity, technical depth, and respect for their time.

Here is a blueprint to craft an InMail that stands out and gets replies:

• Subject Line: Skip the job title or "Exciting Opportunity at [Company]." Instead, make it peer-to-peer, hyper-relevant, or casual.
  • Example: "Loved your work on [Open Source Project / Tech Talk]" or "Scaling [Our Tech Stack] — thought of you."
• The Hook (First 2 Sentences): Prove you actually looked at their profile. Mention a specific commit, blog post, tech stack they use, or a mutual connection. Never start with "I hope this finds you well."
• The "Why You": Briefly state why their specific background caught your eye. (e.g., "Saw your experience building high-throughput distributed systems with Go...").
• The Value Prop (What's in it for them?): Passive candidates don't care about your company perks yet; they care about technical challenges, impact, and growth. Name-drop the hard problem they’d be solving.
• Low-Friction Call to Action (CTA): Do not ask for a 30-minute call right out of the gate. Ask a low-commitment question or offer to share a tech spec/salary range first.
  • Example: "Open to a quick 10-minute chat next week, or would you prefer I drop the compensation and tech breakdown right here?"

A High-Converting Example

Hi [Name],

Stumbled across your talk on [Topic] / your repo for [Project]—really slick approach to [specific technical detail].

I’m leading tech recruiting at [Company], where our core engineering team is currently untangling a similar scaling bottleneck as we migrate to a distributed event-driven architecture using [Tech Stack]. Given your background with [Skill/Tool], you’d probably have fun (or strong opinions) on how we're tackling it.

No pressure at all, but if you're ever curious about what we're building, I'd love to chat. Open to a brief virtual coffee sometime next week?

Best,
[Your Name]

Would you like me to tailor an InMail template for a specific tech stack or role , or help you draft a follow-up message for a candidate who hasn't replied yet?

The biggest mistake is treating an InMail like a job description delivered through LinkedIn. A passive engineer isn't asking, “What jobs are available?” They're asking, “Why should I care about this one?”

LinkedIn's own data supports a simple formula: short + genuinely personalized + clear value + low-friction question. Personalized InMails perform better, and messages in the 200–400-character range have historically performed particularly well.

A high-response InMail formula

1. Subject: make it about them, not the job

Avoid:

• “Software Engineer Opportunity”
• “Exciting Career Opportunity”
• “Job at [Company]”

Try:

• “Your work on distributed systems”
• “Your Stripe → backend path”
• “Quick question about your infra work”
• “Would this be interesting?”
• “Loved your work on [specific thing]”

LinkedIn recommends short, personal, intriguing subject lines rather than generic recruiting language.

2. Open with the specific reason you chose them

Don't say:

“I came across your profile and was impressed by your background.” That's recruiter wallpaper.

Instead:

“Your work scaling Kafka pipelines at Acme caught my eye.” Or:

“I noticed you've spent the last 4 years working on developer infrastructure.” The candidate should immediately know you actually looked at their profile.

3. Sell the engineering problem—not the company

Passive engineers are often more interested in what they'll build than your list of perks.

Weak:

“We're a fast-growing company with a great culture and competitive compensation.” Better:

“The team is rebuilding our event-processing platform from ~50K to 5M events/sec.” Even better if true:

“You'd own the architecture rather than just implement tickets.” LinkedIn specifically recommends focusing on the opportunity and what's in it for the candidate rather than dumping the job description into the InMail.

4. Give them an easy reason to reply

Don't end with:

“Let me know if you're interested.” That requires them to make a career decision before they'll even talk to you.

Instead:

“Worth a 15-minute conversation?” Or:

“Would you be open to hearing what the team is building?” Or, for a genuinely passive candidate:

“Even if you're happy where you are, I'd be curious whether this problem space is interesting to you.” You're asking for permission to have a conversation, not asking them to apply.

Example I'd actually send

That structure works because it answers four questions quickly:

• Why me? → specific experience
• Why this role? → interesting technical problem
• Why should I care? → relevant engineering challenge
• What's the ask? → 15-minute conversation

A stronger version for a truly passive engineer

If they're clearly happy at their current company, I'd make the pitch even less "recruiter-y":

This is often more effective than pretending you know they're looking.

The personalization trick

Don't personalize with fluff. Personalize with evidence.

One highly specific observation beats five generic compliments.

LinkedIn likewise recommends mentioning the particular profile content, experience, skill, accomplishment, mutual connection, or interest that prompted the outreach.

What I'd leave out

For the first InMail, don't cram in:

• the entire tech stack
• 8 bullet-point responsibilities
• company history
• benefits
• every remote-work detail
• a giant compensation paragraph
• the job-description link
• “Are you or anyone you know interested?”
• three paragraphs about how amazing your company is

LinkedIn explicitly advises against pasting the job description or job-post URL and recommends keeping outreach brief.

The simplest rule

Think of your InMail as:

“I found you for a reason → here's the interesting problem → here's why you might care → want to talk?”

Not:

“Here's our company → here's our job → here's the job description → please apply.”

And measure your own results rather than assuming one template is universally best. LinkedIn recommends testing messaging and monitoring InMail analytics; its current Recruiter guidance also notes a 13% minimum response-rate threshold for certain high-volume Recruiter accounts.

If you give me the engineer's profile/background + the role + company + key selling points, I can turn it into a high-response InMail that sounds like a human recruiter wrote it, not an ATS.

LinkedIn specifically recommends focusing on the opportunity and what's in it for the candidate rather than dumping the job description into the InMail.

4. Give them an easy reason to reply

Don't end with:

“Let me know if you're interested.” That requires them to make a career decision before they'll even talk to you.

Instead:

“Worth a 15-minute conversation?” Or:

“Would you be open to hearing what the team is building?” Or, for a genuinely passive candidate:

“Even if you're happy where you are, I'd be curious whether this problem space is interesting to you.” You're asking for permission to have a conversation, not asking them to apply.

Example I'd actually send

Absolutely. The goal isn't to “sell the job” in the first InMail. It's to earn enough curiosity that a passive engineer thinks, “This sounds relevant. I'll respond.”

LinkedIn's own data supports this: shorter InMails perform better, personalized messages outperform bulk outreach, and LinkedIn specifically recommends making the message a conversation starter rather than pasting a job description.

The formula that works

Use this structure:

1. Personal hook Show exactly why this engineer caught your attention.

“Saw your work on distributed systems at [Company]…” 2. Relevant opportunity Give 1–2 technically meaningful details—not a job-description dump.

“I’m hiring a Senior Backend Engineer to help redesign our event-processing platform at ~10M events/day.” 3. Why them Connect their experience to the problem.

“Your Kafka/platform work at [Company] looks unusually relevant.” 4. Low-friction CTA Don't ask them to apply. Don't demand a 30-minute call.

“Worth a quick conversation, even if you’re not actively looking?” That's it.

Example InMail

What makes this better than the typical recruiter message?

Avoid:

“Hi John! I came across your impressive profile and think you’d be a great fit for an exciting opportunity at a fast-growing company. We’re looking for a passionate engineer…” That could be sent to 500 people.

Instead, make the first sentence impossible to send to anyone else.

For example:

“Your migration from monolith → Kubernetes at Stripe is what prompted me to reach out.” That's personalization with a purpose—not personalization for its own sake. LinkedIn reports that personalized InMails perform materially better than generic/bulk messages.

Give engineers a reason to care

Passive software engineers usually don't need another description of responsibilities. Give them something technically interesting.

Instead of:

“You'll work with a talented engineering team on cutting-edge technology.” Try:

“The interesting part: they're rebuilding the authorization layer to handle 10× current traffic without adding latency.” Or:

“The team is replacing a legacy deployment pipeline with an internal platform used by 200+ engineers.” Or:

“You'd own the architecture for a new real-time data pipeline rather than just implementing tickets.” That answers the engineer's implicit question:

“Why would I leave a job I'm already reasonably happy with?”

LinkedIn also recommends emphasizing what's in it for the candidate—such as compensation, flexibility, advancement, and skill development—rather than focusing solely on the employer's hiring need.

Keep it short

This is one place where recruiters often overdo it.

LinkedIn's analysis found that InMails under 400 characters had response rates substantially above average, while very long messages performed worse.

A good passive-candidate InMail is often only 75–150 words, and sometimes much less.

Think:

Hook → interesting problem → why them → easy question.

Not:

Company history → benefits → 14 bullet points → tech stack → job description → calendar link → “Thoughts?”

Your CTA matters more than you think

Don't make the candidate do work.

Weak:

“Please review the attached job description and let me know if you're interested.” Better:

“Would you be open to hearing a little more?” Even better for highly passive talent:

“Not sure this is enough to tempt you away from [Company], but would you be open to a 15-minute conversation?” It gives them permission to say no, which paradoxically can make replying easier.

A strong follow-up

Don't send:

“Just following up on my previous message.” Instead, add new information:

That's a much better reason to reply than simply reminding them that you exist.

The recruiter mindset shift

The biggest change I'd make is this:

Don't write an InMail that explains why the candidate should want your job. Write one that makes the candidate curious enough to have a conversation.

And don't optimize solely for “interested in the role.”

A reply like:

“I'm not looking right now, but that sounds interesting.” is actually a successful first interaction.

LinkedIn itself recommends treating InMail as a conversation starter and avoiding lengthy job descriptions.

A simple template you can reuse

Subject: [Specific hook]

Hi [Name] — noticed [specific thing from their background].

I'm hiring for [role] at [company], where the team is [interesting technical problem / meaningful challenge]. Given your experience with [specific relevant experience], I thought there could be an interesting overlap.

I realize you're probably not actively looking—would you be open to a quick conversation? One final rule: if you can replace the candidate's name with another engineer's name and the message still works unchanged, it's probably not personalized enough.

To get a reply from a passive software engineer, you must lead with radical transparency (including the tech stack, compensation range, and remote policy) and reference a specific, real detail from their portfolio or GitHub/LinkedIn experience . Software engineers are flooded with vague, copy-pasted pitches, so brevity and relevance are your strongest tools to earn trust.

Core Anatomy of a High-Converting InMail

Step-by-Step Writing Framework

1. Keep it under 150 words: Developers scan quickly; long walls of text signal corporate bureaucracy or a lack of respect for their time.
2. Personalize the opening sentence: Mention a concrete piece of their work “why you're approaching this particular developer by referencing something from their work or experience.” [-- Elvatix].
3. State the numbers immediately: Passive talent will not jump hoops unless they know the compensation meets or beats their current baseline.
4. End with a low-pressure close: Give them an easy out or an option to just chat asynchronously.

High-Performing InMail Template

Hi [Name],

Saw your work on [specific project/repo/tech mention]—loved how you handled [technical detail].

I’m leading engineering recruitment for [Company or "a Series-B fintech scaling our core platform"], and we're building our next-gen backend using [Tech Stack: e.g., Go, Kubernetes, AWS]. We’re looking for a [Job Title] to take ownership of [specific technical challenge].

Quick facts:

• Comp: [Salary Range, e.g., $180k–$210k + equity]
• Setup: [Remote / Hybrid in City / On-site]

Open to a brief, no-pressure chat to see how this compares to what you're doing now?

Best,
[Your Name]

If you want, share:

• The seniority level of the role
• Whether you are working in-house or agency side

I can help you tailor this template further or adjust the transparency level for your specific company constraints.

Writing an InMail to a passive software engineer that actually converts requires ditching the standard recruiter pitch. Engineers are flooded with messages, highly skeptical of recruiters, and typically not looking to move—unless the right challenge or opportunity lands in their lap.

Here is a step-by-step blueprint to craft an InMail that cuts through the noise and gets a reply.

1. The Anatomy of a High-Converting InMail

• Keep the Subject Line Short & Specific: Avoid "Exciting Opportunity!" or "Hey [Name], quick question." Instead, name-drop a relevant tech stack or a specific engineering challenge: "[Company] + [Tech Stack / Scale Challenge]" or "Scaling [X] at [Company]—thoughts?"
• Lead with Relevance, Not the Job: Don't start with your company's mission statement or funding round. Start with them . Mention a specific project, open-source contribution, or career milestone on their profile that caught your eye.
• Skip the Fluff: Drop generic corporate speak like "rockstar," "ninja," or "fast-paced environment." Speak like a human peer, not an automated sales machine.
• Define the 'Why You Now': Briefly explain why this specific role matches their trajectory (e.g., "I noticed you've been heavily focused on distributed systems at [Current Co], and we're tackling...")
• Clear, Low-Friction Call to Action (CTA): Never ask for a 30-minute call right out of the gate. Ask a low-commitment question or offer a casual 10-minute sync/async chat.

2. The Proven InMail Framework (Copy-Paste Template)

Subject: Scaling [Tech/Challenge] at [Your Company] / Quick question

Hi [First Name],

I was checking out your work on [specific project/repo/mention from their profile or GitHub]—really liked how you handled [technical detail, e.g., the latency bottleneck / state management].

I’m leading engineering talent at [Your Company], and we’re currently scaling our [mention infrastructure/core product] team. We're running into a similar architectural challenge around [specific technical problem], where we need to [briefly state the engineering goal, e.g., process 10M daily events with sub-50ms latency].

Given your background in [their specific tech stack], I thought you’d appreciate what we're building—or at least have some great battle scars/opinions on how we're approaching it.

No pressure at all, but would you be open to a brief, 10-minute chat or an async back-and-forth this week to see if it’s worth a deeper look?

Best,
[Your Name]
[Your Company]

3. Golden Rules for Sourcing & Personalization

• Do Your Homework: If your opening line could be sent to 50 other people by changing the name, it's not personalized. Mentioning a tech stack they’ve used for 3+ years is high-signal.
• Be Transparent About Compensation: If possible, drop the salary range or equity context early. Passive engineers won't jump through hoops on a mystery box salary. If it's a pay cut, they’ll disengage immediately.
• Respect the Follow-Up: Send one polite follow-up 4 to 5 days later. Keep it brief: "Hey [Name], bumping this in case it got buried. No worries if the timing is off right now!" Do not send a 3-part sequence that feels like aggressive B2B sales.

Would you like me to tailor this template for a specific tech stack (like Go, Rust, or AI/ML) or a particular seniority level (like a Staff/Principal Engineer)?

A passive software engineer usually ignores InMails for one reason: the message feels like work for them. A recruiter asks them to read a job description, schedule a call, update a resume, and decide whether they are interested — before giving them a reason to care.

The InMails that get replies reverse that dynamic. They are short, specific, technically credible, and make replying easy. LinkedIn’s own guidance emphasizes being brief, personalizing the message, avoiding pasted job descriptions, and making the first message a conversation starter rather than a sales pitch.

The formula: “Why you → Why now → Why this → Easy reply”

1. Start with a real observation, not a compliment

Avoid:

“Your background is impressive.” Every engineer has seen that sentence hundreds of times.

Use:

“I noticed you’ve been working on distributed systems at scale, especially around Kafka and real-time data pipelines.” or:

“Your talk on reducing API latency caught my attention — the problems you’re solving are very similar to what our platform team is tackling.” The goal is to prove you did not copy/paste. Personalization and relevance are consistently cited as key drivers of stronger outreach.

---

2. Lead with engineering problems, not the job title

Software engineers are rarely excited by:

“We have a Senior Backend Engineer opening.” They are more interested in:

• What will I build?
• What technical challenges will I solve?
• Who are the engineers?
• Will I learn something?
• Is the work meaningful?

Instead of:

“We’re hiring a Senior Software Engineer.” Try:

“The team is rebuilding our event-processing platform to handle 10x traffic, and we’re looking for someone who enjoys solving scalability problems.”

---

3. Give enough context to qualify the opportunity

Do not hide everything behind “Can we chat?”

Include:

• Tech stack
• Team/product area
• Location/remote expectations
• Level
• Compensation range (when possible)

Passive candidates do not want a mystery meeting. They want enough information to decide whether the conversation is worth their time.

---

4. Make the ask low-pressure

Bad CTA:

“Are you available for a 30-minute call tomorrow?” Better:

“Would it be unreasonable to send over a few details?” or:

“Open to hearing what we’re building, even if you’re not actively looking?” or:

“If this sounds even mildly interesting, I can share more context.”

---

Example InMail that can get replies

Subject: Your work on distributed systems caught my eye

Hi Alex — I came across your work on building scalable backend systems at [Company] and noticed your experience with Go/Kubernetes.

I’m recruiting for a team building a high-throughput data platform where engineers are tackling similar challenges around reliability and scale.

It’s a senior backend role (Go, Kubernetes, AWS), remote-friendly, with a strong engineering culture and significant ownership.

You may be perfectly happy where you are, but would you be open to seeing a few details? No pressure either way.

---

A stronger “engineer-to-engineer” style version

Hi Maya — your open-source contributions around observability tooling stood out. We’re building infrastructure that helps engineers debug distributed services faster, and your background looked unusually aligned.

The team is working on Go, Kubernetes, and large-scale systems problems. I’m not assuming you’re looking, but I’d be curious if exploring a technically interesting challenge is on your radar this year.

Worth sending more context?

---

Follow-up after no response (5–7 days later)

Hi Alex — following up in case my note got buried.

The short version: we’re looking for someone who enjoys solving [specific technical challenge], and your background seemed relevant.

Totally fine if timing isn’t right. Happy to stay connected either way.

---

Common mistakes that kill reply rates

❌ “I hope you’re having a great day…” ❌ “Your profile matches an exciting opportunity…” ❌ Copying the job description ❌ Asking for a resume immediately ❌ Hiding the company, tech stack, or compensation ❌ Writing a five-paragraph pitch

The best passive-candidate InMails feel less like recruiting and more like a smart professional reaching out with an interesting problem. Short, personalized messages tend to perform better than generic long ones.

A useful test: If you removed the candidate’s name, would the message still clearly be written only for them? If not, it is probably not personalized enough.

The biggest mistake is treating an InMail like a job description. A passive software engineer is usually asking: “Why me, why this, and why should I spend time replying?”

LinkedIn’s own guidance consistently points toward short, personalized, conversational messages rather than generic pitches. Personalized InMails perform better, and LinkedIn reports that shorter messages tend to get higher response rates.

A high-response InMail formula

Use this 5-part structure:

1. Personal hook — Something genuinely specific about their background.
2. Why them — Connect that experience to what you're building.
3. Interesting opportunity — One compelling detail, not the whole job description.
4. Low-pressure CTA — Make replying easy.
5. Keep it short — Aim for roughly 200–400 characters when possible. LinkedIn reports that this range performs particularly well.

Example

Make the subject line earn the open

Avoid:

• “Exciting Job Opportunity!”
• “Software Engineer Role”
• “Opportunity at [Company]”
• “I’d love to connect”

Instead, make it specific and human:

• “Your distributed systems work”
• “Quick question about [technology]”
• “Your work at Stripe”
• “Scaling systems at [Company]”
• “Worth a conversation?”
• “Loved your work on [project]”

LinkedIn recommends concise, personalized subject lines and specifically cautions against generic “job opening” subjects.

The personalization trick that actually works

Don't write:

“I was impressed by your extensive experience with Java, AWS, Kubernetes, microservices, and distributed systems.” That's keyword personalization. Engineers see through it immediately.

Instead, find one interesting thing:

“I noticed you led the migration from monolith to Kubernetes at X.” Then explain why that caught your attention:

“We're dealing with a similar scaling problem, which is why I reached out.” That's much more credible.

Sell the engineering problem, not the company

Passive engineers are often more interested in what they'll get to build than a paragraph about your company.

Instead of:

“We're a fast-growing Series C company with amazing culture, competitive compensation, and great benefits…” Try:

“The team is rebuilding our event-processing platform and is hitting some interesting problems around throughput, reliability, and multi-region architecture.” That's something an engineer can actually react to.

LinkedIn similarly recommends focusing on the opportunity and what matters to the candidate rather than pasting a job description.

Give them an easy reply

Don't end with:

“Please let me know if you're interested and send me your availability.” That's work.

Try:

“Worth a quick conversation?” Or:

“Open to hearing more?” Or, even better:

“If you're happy where you are, no worries—I'd still be curious whether this type of problem is interesting to you.” The goal of the first InMail isn't getting the interview. It's getting the conversation.

My favorite recruiter template

One final rule: if you could send the exact same message to 100 engineers by changing only the name, it's not personalized enough.

LinkedIn's current Recruiter guidance explicitly recommends mentioning the profile detail that prompted the outreach, keeping the message brief, and making it a conversation rather than a sales pitch.

If you give me the engineering role, company, tech stack, and a candidate's LinkedIn/profile highlights, I can turn that into a genuinely personalized InMail rather than a recruiter template.

Writing an InMail that cuts through the noise of a passive software engineer’s inbox requires treating them less like a target and more like a peer. Engineers are notoriously skeptical of recruiters, despise copy-pasted corporate fluff, and get dozens of pitches a week.

To turn a passive engineer into a reply, structure your InMail around brevity, relevance, and transparency.

1. Ditch the Fluff and Keep It Short

Messages under 400 characters see significantly higher response rates. Respect their time by getting straight to the point without an overly long intro about how "impressed" you are by their generic profile.

• The Rule: Aim for 3–4 short sentences max.
• The Fix: Cut "I hope this message finds you well in these unprecedented times..." and replace it with why you are messaging them specifically today.

2. Personalize with Substance (Not Flattery)

Don't just say you looked at their profile—prove it. Mention a specific technical element, an open-source contribution, a talk they gave, or a complex stack challenge they likely face at their current company.

• Example: As noted by Okta Lead Recruiter Maria Mencias, “A few personalized touches really help make your message feel tailored to them.”
• Reference a shared connection, common past employer (which bumps response rates by 27%), or a mutual tech stack.

3. Lead with the Cards They Care About

Passive candidates aren't hunting for a job, which means they are looking at what the move would cost or benefit them. Transparency wins trust immediately. Include critical data points upfront:

• Tech Stack: Name the exact core technologies (e.g., Rust, Go, distributed Kafka streams) rather than "modern technologies."
• Compensation: Drop the salary range or total comp right in the pitch. Hiding salary is the #1 friction point for engineers who won't reply until they know the tier.
• Remote / Flexibility Policy: State clearly whether it's fully remote, hybrid (and how many days), or onsite.

4. End with a Low-Friction Call to Action (CTA)

Don’t ask for a 30-minute phone call right out of the gate. That's a high-friction commitment for someone who is happy where they are.

• Ask an easy, binary question or offer an asynchronous peek under the hood.
• Example: "Open to a quick 10-min chat this week, or would you rather I just drop the full job spec and comp details right here first?"

The High-Converting Template

"Hey [Name] — saw your work scaling data pipelines at [Current Company]. We’re running into a very similar distributed systems bottleneck over at [Your Company] with our real-time ingestion layer.

We’re looking for a Senior Backend Engineer to lead that architecture ($180k–$210k + equity, fully remote US). Are you open to a quick chat, or would you prefer I send over the full engineering brief to look over first?"

Would you like me to tailor a specific InMail template for a particular tech stack or seniority level you are currently hiring for?