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

A passive software engineer usually ignores recruiter InMails for one reason: the message feels like work for them and value for you. The goal is to make replying feel easy, interesting, and low-risk. LinkedIn’s own guidance emphasizes keeping InMails brief, personal, conversational, and focused on starting a dialogue rather than pasting a job description.

A strong InMail has five parts:

1. Earn attention in the first sentence

Avoid:

"I came across your profile and think you'd be a great fit for an exciting opportunity." Engineers see this constantly.

Instead, prove you looked at their work:

• "Your work on distributed caching at [Company] caught my attention."
• "I noticed your contributions to [open-source project] and your background scaling [technology]."
• "Your move from backend infrastructure into platform engineering stood out."

Specificity beats flattery.

2. Lead with the technical challenge, not the job title

Engineers are usually more interested in what they will build than a title change.

Weak:

"We’re hiring a Senior Software Engineer." Better:

"The team is rebuilding a payments platform handling millions of transactions and needs someone who enjoys solving reliability and distributed systems problems."

3. Give enough details to qualify the opportunity

Passive candidates don't want a mystery call.

Include:

• Company/product (if possible)
• Tech stack
• Engineering challenge
• Location/remote expectations
• Compensation range when appropriate

Transparency helps candidates decide whether a conversation is worth their time.

4. Make the ask tiny

Don't start with:

"Do you have 30 minutes this week?" Try:

"Would you be open to me sending over a short overview?" or:

"Worth a quick conversation, or should I leave you alone for now?" A low-pressure question gets more replies because the candidate does not feel trapped.

5. Write like a human

A good InMail is usually around 5–8 lines. Avoid:

• "synergy"
• "rockstar"
• "ninja"
• "fast-paced environment"
• copied job descriptions

LinkedIn specifically recommends avoiding long job descriptions and making the message a conversation starter.

Example InMail

Subject: Your distributed systems work + a quick question

Hi Sarah — I noticed your work building high-scale backend systems at Acme, especially around Kafka and service reliability.

I’m reaching out because we’re building a team focused on similar problems: scaling infrastructure that supports millions of users while improving developer velocity.

Your background looked unusually aligned, so I wanted to ask: would you be open to taking a look at a short overview of what the team is building?

Totally fine if you’re happy where you are — happy to stay connected either way.

— Alex

Follow-up if they don't reply

After about a week:

Hi Sarah — just following up in case my note got buried. No pressure at all.

The main reason I reached out was your experience with [specific technology/project]. Even if a move isn’t on your radar, I’d be curious whether this type of engineering problem is interesting to you.

Either way, appreciate your time. The biggest mindset shift: don't try to "sell the job." Your first InMail only needs to earn a second conversation.

Writing an InMail that cuts through the noise of a senior software engineer’s inbox requires treating them like a peer, not a quota. Passive engineers don't care about your company's "fast-paced, dynamic environment" or "rockstar culture"—they care about technical challenges, autonomy, and compensation transparency.

Here is a step-by-step framework to write an InMail that actually gets a reply, complete with a high-converting template.

The 4 Rules of Engagement

High-Converting InMail Template

Subject: Scaling distributed systems at [Company Name] (and why I thought of your work on [Project/Skill])

Hi [First Name],

I was checking out your background—your recent work optimizing [mention a specific tech, repo, or past company project] caught my eye, especially how you handled [specific technical detail or challenge].

I lead tech recruiting at [Company Name] , and we're currently tackling a similar bottleneck: scaling our real-time event pipeline to handle 10M+ concurrent requests without blowing up our cloud budget.

We’re a team that believes in [mention one genuine perk: e.g., zero legacy constraints / async-first culture / deep technical ownership], and we use [Tech Stack: e.g., Rust, Kafka, Kubernetes].

• The Role: [Senior Backend Engineer]
• Comp: [$180k - $210k base + meaningful equity]
• The Catch/Hurdle: We’re heavily focused on low-latency messaging right now.

No pressure or long pitch calls required. If you're even casually open to seeing how we're architecting this, I'd love to share a quick architecture doc or chat for 15 minutes.

If not, no worries at all—keep building cool stuff!

Best,
[Your Name]
[Company Name]

Would you like me to tailor this template further based on:

• A specific tech stack you are hiring for?
• A startup vs. enterprise company environment?
• How to handle follow-up sequences if they don't reply?

Writing an InMail to a passive software engineer that actually gets a reply comes down to one golden rule: respect their time and intelligence. Engineers get dozens of generic pitches a week. To cut through the noise, your InMail needs to feel like a peer-to-peer message, not a marketing broadcast.

Here is a blueprint for writing a high-converting InMail, broken down from subject line to call-to-action.

1. The Subject Line: Keep it Casual and Relevant

Skip the hype words ("Rockstar," "Ninja," "Exciting Opportunity"). Instead, focus on connection, context, or a shared interest.

• Bad: Exciting Job Opportunity at [Company]
• Good: Loved your open-source work on [Project]
• Good: Engineering culture at [Company] / Quick Q
• Good: [Mutual Connection/Alumni] suggested I reach out

2. The Hook: Make it Personal immediately (First 2 sentences)

Don’t start with "I hope this message finds you well" or a paragraph about how amazing your company is. Start with them . Show you actually looked at their profile.

• Mention a specific technical talk they gave, a blog post they wrote, a complex migration they led, or a core contribution to an open-source project.
• Example: "Saw your recent breakdown on handling high-throughput Kafka streams—that migration bottleneck you solved at [Previous Company] looked brutal."

3. The Pitch: The "What's in it for them?" (1-2 sentences)

Software engineers care about three things: scale/tech stack, the problem they get to solve , and who they work with . Address the technical challenge, not the corporate perks.

• Name-drop the actual tech stack or architectural challenge early.
• Example: "Over at [Your Company], we’re scaling our core data infrastructure to handle a 10× surge in real-time events, and our team is running into the exact latency issues you tackled."

4. The Social Proof / Transparency: Drop the Salary/Details

Passive candidates won't jump through hoops to find out if the role is worth their time. Be transparent about what matters to them (compensation range, remote policy, equity) right away.

• Example: "It’s a Senior Backend role working with Go and Kubernetes. Fully remote (US), and the base is in the[$1 8 0 k−$2 1 0 k] range + equity."

5. The Low-Pressure Call-to-Action (CTA)

Never ask for a 30-minute phone call right out of the gate. That's a high-friction commitment. Instead, offer an easy out or an asynchronous chat.

• Bad: Do you have 15 minutes to hop on a call on Tuesday?
• Good: Open to trading a few messages here to see if there's a mutual fit?
• Good: No pressure at all, but if you're open to a chat about what we're building, let me know.

A Fill-in-the-Blank Template

Hi [First Name],

[Personalized hook: e.g., Noticed your background scaling microservices at X, or loved your comment on Y thread.]

I’m leading engineering recruiting at [Company], and we’re currently scaling our [Specific Team/Product] team. We're tackling [cool technical challenge, e.g., migrating a monolith to event-driven services using Kafka and Rust].

It’s a [Senior/Staff] role, fully [remote/hybrid], paying around[S a l a r y R a n g e] plus equity.

No worries if you're heads-down and happy where you are, but if this sounds like the kind of problem you’d enjoy chewing on, would you be open to a quick chat or trading a few notes here?

Best,
[Your Name]

If you'd like, let me know:

• What specific tech stack or role you're currently hiring for
• The biggest pushback or ghosting pattern you're seeing from engineers right now

I can help you tailor this template or write a custom InMail for your hardest-to-fill position.

The biggest mistake Technical Recruiters make with passive engineers is writing the message for the recruiter instead of the engineer.

LinkedIn’s own data consistently points in the same direction: shorter, personalized InMails outperform generic ones, and LinkedIn specifically recommends making the message a conversation starter rather than pasting a job description.

The formula that works

Think:

Personalized observation → Why them → What's interesting → Low-friction question

1. Lead with something specific

Don't say:

“I came across your impressive background…” Instead:

“I noticed you’ve spent the last 3 years working on distributed systems at Stripe…” That proves you actually looked at their profile.

LinkedIn reports that personalized InMails perform materially better than bulk messages.

2. Give them a reason to care

Passive engineers aren't looking for a job. They're potentially interested in a better technical problem.

Talk about things like:

• Architecture ownership
• Scale
• Interesting technical challenges
• Engineering autonomy
• Staff-level scope
• Greenfield work
• Impact
• Compensation, if compelling
• Remote/flexible setup
• Growth into leadership

For example:

“I’m recruiting for a backend team rebuilding our event-processing platform at massive scale. The role has ownership of architecture rather than just implementation.” That's much more compelling than:

“We have an exciting Senior Software Engineer opportunity.”

3. Don't make them read the job description

LinkedIn explicitly advises against lengthy job descriptions and “here's a job, are you interested?” outreach.

Give them just enough information to become curious.

4. Make replying ridiculously easy

Don't end with:

“Would you be interested in discussing this opportunity?” Instead:

“Worth a 15-minute conversation, or are you pretty happy where you are?” Now they can answer yes, no, or maybe without committing to an interview.

---

A strong example

That's roughly the territory I'd aim for: personal, technically credible, brief, and no pressure.

LinkedIn reports that InMails under 400 characters have higher response rates than average, while messages over 800 characters perform below average.

Even better for a highly passive engineer

For someone who's clearly happy at Google, Meta, Amazon, Stripe, etc., I'd make the pitch about the technical opportunity, not the company.

Three things I'd avoid

• “I hope you're doing well!” — wastes your most valuable opening line.
• A giant paragraph about the company — they don't know yet whether they care.
• “Please review the JD and let me know if interested.” — you've just assigned them homework.

Instead, make the first InMail feel like a smart engineer was specifically identified for an interesting problem.

One more useful tactic: if you share a former employer or mutual connection, use it. LinkedIn reports that mentioning a common former employer can increase response likelihood, and its current guidance recommends leveraging mutual experiences and connections.

The mental model:

“I know you're probably not looking. I noticed something specific about your work. Here's why I think this particular problem might interest you. Want to talk?” That's a much better passive-candidate pitch than “I have an exciting opportunity I'd love to tell you about.”

“Worth a 15-minute conversation, or are you pretty happy where you are?” Now they can answer yes, no, or maybe without committing to an interview.

---

A strong example

That's roughly the territory I'd aim for: personal, technically credible, brief, and no pressure.

LinkedIn reports that InMails under 400 characters have higher response rates than average, while messages over 800 characters perform below average.

Even better for a highly passive engineer

For someone who's clearly happy at Google, Meta, Amazon, Stripe, etc., I'd make the pitch about the technical opportunity, not the company.

The biggest mistake Technical Recruiters make with passive engineers is trying to sell the job before earning the conversation.

LinkedIn’s own data supports a simple approach: shorter InMails perform better, personalization improves response rates, and messages should start a conversation rather than read like a job description. LinkedIn reports that InMails in the 200–400 character range are 16% more likely to receive a response.

The formula that works

Think:

Why them → Why this opportunity → Why it might matter → Easy question

A strong InMail usually has 4 parts:

1. Personal hook

• Mention something specific you noticed.
• A technology, architecture problem, project, promotion, open-source contribution, or previous company.
• Avoid fake personalization like “I was impressed by your profile.”

2. Specific reason you're reaching out

• Explain why their experience maps to the role.
• Example: “Your work moving the payments platform to Kafka caught my attention…”

3. One compelling detail

• Give them something they couldn't get from a generic job description.
• Scale, technical ownership, greenfield work, interesting engineering problem, autonomy, team quality, etc.

4. Low-friction CTA

• Don't ask them to “apply.”
• Don't immediately ask for a 30-minute call.
• Ask whether the opportunity is worth exploring.

LinkedIn specifically recommends keeping InMails brief, avoiding lengthy job descriptions, and making the message a conversation starter.

Example: Senior Backend Engineer

That works better than:

“Hi Sarah, I came across your impressive profile and think you'd be a great fit for an exciting Senior Software Engineer opportunity at a fast-growing company. Please review the job description and let me know if interested.” The second version could be sent to 500 engineers. The first makes Sarah feel like you actually chose her.

For really passive engineers, make the opportunity the hook

A passive engineer generally doesn't need another job.

They need a reason to interrupt their current situation.

So instead of:

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

“Your background in distributed systems is exactly what caught my attention. The team is currently redesigning the service responsible for X at ~Y scale, and this person will have architectural ownership rather than just implementing tickets.” That's much more compelling.

You can also lead with things engineers tend to care about:

• Technical challenge: “greenfield platform,” “distributed systems at scale”
• Technical ownership: “own the architecture”
• Engineering quality: “small senior team,” “strong testing culture”
• Impact: “your work directly affects X million users”
• Career trajectory: “first engineer leading this function”
• Technology: only when the stack is genuinely interesting
• Compensation: useful when it's a meaningful differentiator
• Location/flexibility: especially if remote/hybrid is a selling point

LinkedIn recommends explicitly communicating the “what's in it for me” for passive candidates rather than simply describing the vacancy.

The subject line matters

Don't waste it on:

• “Exciting Opportunity”
• “Software Engineer Opportunity”
• “Job Opportunity at XYZ”
• “Your Profile”
• “Interested in a New Role?”

Better:

• Your Kafka work
• Quick question, Sarah
• Your distributed systems background
• Loved your work on X
• Backend architecture @ [Company]
• Interesting platform challenge
• Question about your AWS work

LinkedIn has found that concise, personal subject lines tend to perform better.

One trick: personalize the reason, not just the name

Weak personalization:

“Hi John, I saw you have 8 years of Java experience.” Better:

“Your decision to move the pricing engine from a monolith to services caught my attention.” Best:

“I noticed you led the pricing-engine migration from a monolith to services. We're facing a remarkably similar problem, except at ~10x the transaction volume.” Now the engineer has an obvious reason to think:

“Wait—what are they doing?”

That's the response you want.

And don't oversell

Technical people are usually pretty good at detecting recruiting language.

I'd avoid phrases like:

“rockstar engineer” “ninja” “unicorn” “amazing opportunity” “disruptive company” “fast-paced environment” “world-class team” Unless you can substantiate them.

Instead, give them concrete facts.

“You'll own the API platform used by 40+ internal teams.” is much stronger than:

“You'll have tremendous impact in an innovative environment.”

A simple template you can reuse

The important part is not the template. It's the research behind [specific thing].

LinkedIn's current Recruiter guidance similarly emphasizes personalization, conversational tone, brevity, and explaining why you selected that particular candidate.

The mental test

Before pressing Send, ask yourself:

“If I removed the candidate's name, could this message be sent to 100 other engineers unchanged?” If yes, rewrite it.

A great passive-candidate InMail should make the engineer think:

“I wasn't looking—but this sounds unusually relevant to me.”

That's the sweet spot.

If you give me a specific role + company + candidate's background, I can also turn this into a high-response InMail tailored to that exact engineer.

To get a passive software engineer to reply to your InMail, you must stand out from the generic spam they receive daily. Write a highly personalized, brief message that focuses on their engineering identity rather than your open role.

The Winning Formula

• Hook them fast: Mention a specific project or technology from their profile.
• Show real context: Explain exactly why their background caught your eye.
• Keep it brief: Ensure the message is under 150 words total.
• Lower the barrier: Ask for a casual chat, not an interview.

Step-by-Step Blueprint

1. Write an Unignorable Subject Line

Avoid corporate jargon like "Exciting Opportunity" or "Job Opening." Instead, name a specific technology or shared connection.

• Bad: Job opportunity at TechCorp!
• Good: Question about your Go implementation at [Current Company]
• Good: Fellow [University Name] alum / scale challenge at [Your Company]

2. Prove You Read Their Profile

Software engineers instantly delete copy-paste templates. Prove you are a human who looked at their work.

• Bad: "I saw your impressive background in software engineering."
• Good: "I read your Medium post on optimizing PostgreSQL queries under heavy load."

3. State Your Problem, Not Your Title

Engineers are driven by interesting problems, not generic job descriptions. Explain the technical challenge they would solve.

• Bad: "We are looking for a Senior Full Stack Engineer with 5+ years of React."
• Good: "We are currently migration our legacy monolith to a distributed microservices architecture to support 10x traffic."

4. Use a Low-Pressure Call to Action (CTA)

Do not ask for a resume or a formal interview right away. Ask for a brief, casual sync.

• Bad: "Let me know when you are available for a 45-minute technical screening."
• Good: "Open to a 10-minute coffee chat next Tuesday to trade notes on distributed systems?"

High-Reply Template Example

Subject: Question about your Rust project / [Your Company Name]

Hi [Name],

I came across your GitHub repository for the async logging library. The way you handled memory allocation to reduce latency was incredibly clever.

I’m a technical recruiter at [Your Company]. Our core infrastructure team is currently rebuilding our data pipeline in Rust to handle a massive spike in real-time data ingestion. Your experience solving latency bottlenecks feels like exactly the kind of perspective we need.

I know you are likely happy at [Current Company], but I'd love to connect for 10 minutes next week to share what we are building.

If you are open to it, let me know what day works best. If not, no worries at all—keep up the great work on that repo!

Best,

[Your Name]

If you want to tailor this strategy further, tell me:

• What specific stack or programming language is this role targeting?
• What is the biggest technical hurdle your engineering team is facing right away?
• What company stage are you recruiting for? (e.g., early-scale startup, FAANG, enterprise)

I can help you draft a highly customized template based on your specific hiring needs.

The biggest mistake is treating an InMail like a job description. A passive engineer is asking themselves, “Why should I spend 30 seconds on this?”

LinkedIn’s own data supports a few principles: personalized InMails outperform generic ones, shorter messages tend to perform better, and the strongest outreach gives the candidate a reason to continue the conversation rather than immediately asking them to apply.

The formula that works

Use this structure:

1. Personal hook → 2. Why them → 3. Interesting technical problem → 4. Low-pressure CTA

1. Start with something genuinely specific

Bad:

Hi John, I came across your profile and was impressed by your experience. Every engineer has received this 500 times.

Better:

I noticed you’ve spent the last few years working on distributed systems at scale, particularly around Kafka and Go. Even better:

Your work on reducing latency in the payments pipeline at X caught my attention. The personalization should prove why you picked them, not merely demonstrate that you looked at their profile. LinkedIn specifically recommends referencing relevant skills, previous roles, shared connections, projects, or other profile details.

2. Sell the technical challenge, not the company

Engineers are often more interested in what they'll build than a list of perks.

Instead of:

We're hiring a Senior Software Engineer to join our rapidly growing team. We have great benefits and an exciting culture. Try:

We're rebuilding our event-processing platform to handle 10x our current volume, with a lot of interesting problems around distributed systems, reliability, and latency. Now the candidate can evaluate the engineering problem.

3. Give them a reason to believe you're selective

Passive candidates don't want to feel like they're one of 200 people in a recruiter campaign.

Say:

I'm reaching out specifically because your experience with X/Y is unusually close to what we're tackling. That's much stronger than:

Your background seems like a great fit.

4. Make the CTA ridiculously easy

Don't ask for a résumé.

Don't ask them to apply.

Don't immediately ask for a 45-minute interview.

Try:

Would you be open to a quick conversation to see if the problem space is interesting? Or even:

Worth a conversation? The goal of the first InMail is not to close the candidate. It's to earn the next conversation.

LinkedIn similarly recommends asking candidates to continue the dialogue rather than pushing them directly into an application.

A strong example

Three things I'd avoid

• The giant paragraph. LinkedIn says InMails of 200–400 characters are more likely to receive responses, and more recent LinkedIn data found messages under 400 characters perform better than average.
• The job-description dump. Don't paste requirements, responsibilities, qualifications, benefits, and corporate boilerplate.
• Fake personalization. “I loved your impressive background” isn't personalization. Mention the actual technology, project, company, article, open-source contribution, or career move that made you reach out.

A useful rule for Technical Recruiters

Before sending, ask yourself:

“Could I send this exact message to 50 other engineers?” If the answer is yes, rewrite it.

A great passive-candidate InMail should make the engineer think:

“They actually looked at my background → this sounds technically interesting → maybe I'll hear them out.”

Also, measure your own results rather than blindly following generic benchmarks. LinkedIn's Recruiter reporting lets you compare response rates by factors such as candidate segment, company, school, and time in role.

If you give me the role, company, tech stack, and a sample candidate's LinkedIn background, I can show you exactly how I'd personalize the InMail.

Your work on reducing latency in the payments pipeline at X caught my attention. The personalization should prove why you picked them, not merely demonstrate that you looked at their profile. LinkedIn specifically recommends referencing relevant skills, previous roles, shared connections, projects, or other profile details.

2. Sell the technical challenge, not the company

Engineers are often more interested in what they'll build than a list of perks.

Instead of:

We're hiring a Senior Software Engineer to join our rapidly growing team. We have great benefits and an exciting culture. Try:

We're rebuilding our event-processing platform to handle 10x our current volume, with a lot of interesting problems around distributed systems, reliability, and latency. Now the candidate can evaluate the engineering problem.

3. Give them a reason to believe you're selective

Passive candidates don't want to feel like they're one of 200 people in a recruiter campaign.

Say:

I'm reaching out specifically because your experience with X/Y is unusually close to what we're tackling. That's much stronger than:

Your background seems like a great fit.

4. Make the CTA ridiculously easy

Don't ask for a résumé.

Don't ask them to apply.

Don't immediately ask for a 45-minute interview.

Try:

Would you be open to a quick conversation to see if the problem space is interesting? Or even:

Worth a conversation? The goal of the first InMail is not to close the candidate. It's to earn the next conversation.

LinkedIn similarly recommends asking candidates to continue the dialogue rather than pushing them directly into an application.

A strong example

To get a passive software engineer to reply to your InMail, you must stand out from the generic spam they receive daily. Write a highly personalized, brief message that focuses on their engineering identity rather than your open role.

The Winning Formula

• Hook them fast: Mention a specific project or technology from their profile.
• Show real context: Explain exactly why their background caught your eye.
• Keep it brief: Ensure the message is under 150 words total.
• Lower the barrier: Ask for a casual chat, not an interview.

Step-by-Step Blueprint

1. Write an Unignorable Subject Line

Avoid corporate jargon like "Exciting Opportunity" or "Job Opening." Instead, name a specific technology or shared connection.

• Bad: Job opportunity at TechCorp!
• Good: Question about your Go implementation at [Current Company]
• Good: Fellow [University Name] alum / scale challenge at [Your Company]

2. Prove You Read Their Profile

Software engineers instantly delete copy-paste templates. Prove you are a human who looked at their work.

• Bad: "I saw your impressive background in software engineering."
• Good: "I read your Medium post on optimizing PostgreSQL queries under heavy load."

3. State Your Problem, Not Your Title

Engineers are driven by interesting problems, not generic job descriptions. Explain the technical challenge they would solve.

• Bad: "We are looking for a Senior Full Stack Engineer with 5+ years of React."
• Good: "We are currently migration our legacy monolith to a distributed microservices architecture to support 10x traffic."

4. Use a Low-Pressure Call to Action (CTA)

Do not ask for a resume or a formal interview right away. Ask for a brief, casual sync.

• Bad: "Let me know when you are available for a 45-minute technical screening."
• Good: "Open to a 10-minute coffee chat next Tuesday to trade notes on distributed systems?"

High-Reply Template Example

Subject: Question about your Rust project / [Your Company Name]

Hi [Name],

I came across your GitHub repository for the async logging library. The way you handled memory allocation to reduce latency was incredibly clever.

I’m a technical recruiter at [Your Company]. Our core infrastructure team is currently rebuilding our data pipeline in Rust to handle a massive spike in real-time data ingestion. Your experience solving latency bottlenecks feels like exactly the kind of perspective we need.

I know you are likely happy at [Current Company], but I'd love to connect for 10 minutes next week to share what we are building.

If you are open to it, let me know what day works best. If not, no worries at all—keep up the great work on that repo!

Best,

[Your Name]

If you want to tailor this strategy further, tell me:

• What specific stack or programming language is this role targeting?
• What is the biggest technical hurdle your engineering team is facing right away?
• What company stage are you recruiting for? (e.g., early-scale startup, FAANG, enterprise)

I can help you draft a highly customized template based on your specific hiring needs.

To get a passive software engineer to reply to your InMail, you must stand out from the generic spam they receive daily. Write a highly personalized, brief message that focuses on their engineering identity rather than your open role.

The Winning Formula

• Hook them fast: Mention a specific project or technology from their profile.
• Show real context: Explain exactly why their background caught your eye.
• Keep it brief: Ensure the message is under 150 words total.
• Lower the barrier: Ask for a casual chat, not an interview.

Step-by-Step Blueprint

1. Write an Unignorable Subject Line

Avoid corporate jargon like "Exciting Opportunity" or "Job Opening." Instead, name a specific technology or shared connection.

• Bad: Job opportunity at TechCorp!
• Good: Question about your Go implementation at [Current Company]
• Good: Fellow [University Name] alum / scale challenge at [Your Company]

2. Prove You Read Their Profile

Software engineers instantly delete copy-paste templates. Prove you are a human who looked at their work.

• Bad: "I saw your impressive background in software engineering."
• Good: "I read your Medium post on optimizing PostgreSQL queries under heavy load."

3. State Your Problem, Not Your Title

Engineers are driven by interesting problems, not generic job descriptions. Explain the technical challenge they would solve.

• Bad: "We are looking for a Senior Full Stack Engineer with 5+ years of React."
• Good: "We are currently migration our legacy monolith to a distributed microservices architecture to support 10x traffic."

4. Use a Low-Pressure Call to Action (CTA)

Do not ask for a resume or a formal interview right away. Ask for a brief, casual sync.

• Bad: "Let me know when you are available for a 45-minute technical screening."
• Good: "Open to a 10-minute coffee chat next Tuesday to trade notes on distributed systems?"

High-Reply Template Example

Subject: Question about your Rust project / [Your Company Name]

Hi [Name],

I came across your GitHub repository for the async logging library. The way you handled memory allocation to reduce latency was incredibly clever.

I’m a technical recruiter at [Your Company]. Our core infrastructure team is currently rebuilding our data pipeline in Rust to handle a massive spike in real-time data ingestion. Your experience solving latency bottlenecks feels like exactly the kind of perspective we need.

I know you are likely happy at [Current Company], but I'd love to connect for 10 minutes next week to share what we are building.

If you are open to it, let me know what day works best. If not, no worries at all—keep up the great work on that repo!

Best,

[Your Name]

If you want to tailor this strategy further, tell me:

• What specific stack or programming language is this role targeting?
• What is the biggest technical hurdle your engineering team is facing right away?
• What company stage are you recruiting for? (e.g., early-scale startup, FAANG, enterprise)

I can help you draft a highly customized template based on your specific hiring needs.

A passive software engineer usually isn’t ignoring recruiters because they “don’t like recruiters.” They’re ignoring messages that feel like work: generic, unclear, overly salesy, or obviously copied. The goal of an InMail is not to sell the job in one message — it is to earn a small amount of attention and start a conversation.

LinkedIn’s own analysis of InMails found that shorter messages and individually personalized messages tend to perform better than bulk, generic outreach.

The formula that works

1. Lead with why them, not why you’re hiring

Weak:

“I came across your profile and think you’d be a great fit for an exciting opportunity.” Every engineer has seen this.

Better:

“I noticed you’ve been working on distributed systems at [Company] and recently moved into platform reliability. That caught my attention because we’re building similar infrastructure challenges around scale and performance.” The engineer should immediately think:

“This person actually looked at my background.”

---

2. Mention the technical problem, not just the job title

Software engineers are usually motivated by:

• Interesting technical challenges
• Architecture decisions
• Ownership
• Learning opportunities
• Strong engineering teams
• Impact

They are rarely motivated by:

• “fast-growing company”
• “competitive salary”
• “exciting opportunity”
• “rockstar engineer wanted”

Instead of:

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

“The team is rebuilding their event-processing platform to handle 10x traffic, and this role would own the architecture decisions around Kafka, scalability, and reliability.”

---

3. Give them an easy “yes” or “no”

Don’t ask for a 45-minute interview.

Passive candidates are not looking for homework.

Try:

“Would you be open to a quick 15-minute conversation to see if this is interesting?” Or even:

“No pressure if you’re happy where you are — I’d just be curious whether this type of problem space is something you’d ever consider.”

---

4. Keep it short

A good first InMail is usually around 75–150 words. LinkedIn research has found shorter InMails tend to outperform longer ones, especially because candidates often read them on mobile.

A strong structure:

1. Personal observation (1 sentence)
2. Why you reached out (1–2 sentences)
3. Technical opportunity (1 sentence)
4. Low-pressure CTA (1 sentence)

---

Example InMail

Subject: Your work on [technology]

Hi Alex — I noticed your work on [specific project/technology] at [Company], especially your experience with [specific technical area].

I’m reaching out because I’m working with a team building [specific product/problem], where they’re dealing with challenges around [technical challenge]. Your background in [relevant skill] stood out as closely aligned.

The role involves owning significant parts of the architecture rather than just implementing tickets.

Would you be open to a quick 15-minute conversation to hear what the team is building? Totally understand if you’re not looking — happy to share details either way.

---

Things that kill reply rates

Avoid:

❌ “I hope this message finds you well” ❌ “Your impressive background caught my eye” ❌ A five-paragraph company pitch ❌ Copy/pasting the job description ❌ Asking for a resume before a conversation ❌ Pretending a role is “perfect” without explaining why

---

A useful test: before sending, remove the candidate’s name. If the message still works unchanged, it probably isn’t personalized enough.

The best recruiter InMails make engineers feel selected, not targeted.