ConnectDevs

Tag: Response Rate

  • Recruiter InMail Response Rate: Benchmarks and 9 Ways to Raise It

    Recruiter InMail Response Rate: Benchmarks and 9 Ways to Raise It

    Recruiter InMail Response Rate: Benchmarks and 9 Ways to Raise It

    Your recruiter InMail response rate decides how many candidates you actually talk to, and for most teams it is lower than they think. LinkedIn’s own guidance for Recruiter accounts is a 13% response rate, and plenty of recruiters sit below it. This guide shows what a good rate looks like, where the numbers come from, and nine changes that raise replies without sending more messages. It also covers cold outreach to candidates beyond LinkedIn, because the best teams no longer rely on one channel. Every statistic below links to its source, and vendor-reported data is labeled.

    TL;DR

    • A good InMail response rate is roughly 15-25%, and LinkedIn expects at least 13% on Recruiter accounts.
    • Cold email to candidates replies far lower, around 5-6% per message in one 2026 vendor dataset.
    • The biggest levers are targeting, a specific opener, short copy, two to three follow-ups, and a second channel.
    • Track positive replies, not just replies, or you will optimize for the wrong thing.

    Table of Contents

    What is a good InMail response rate?

    A good recruiter InMail response rate is about 15-25%, in line with the 10-25% range for personalized InMail that daily.dev’s roundup reports (a secondary, vendor-published figure). Below 13% is a warning sign, because LinkedIn’s own rule says Recruiter and Recruiter Lite users should hold a 13% response rate across 100 or more InMails in every 14-day period (as quoted by Pin from LinkedIn Talent Solutions). Above 30% usually means a tight, specific talent pool and short, personal messages.

    Context matters. A senior staff engineer gets many more messages than a regional operations manager, so the same copy earns different results. Compare yourself to your own role types first and to the market second.

    Recruiter outreach benchmarks by channel

    Public InMail benchmarks are thin and mostly come from vendors, so treat them as ranges. The cleanest recent dataset is Pin’s 2026 report, which analyzed 4 million+ messages across 1,500+ organizations between June 2025 and May 2026. It is vendor-reported data, but the sample is large and the method is stated (Pin recruiting outreach benchmarks 2026).

    Channel Reply rate (Pin, 2026) What it tells you
    Automated email 4.96% Generic sequences get the lowest replies.
    Recruiter-written email 6.31% Human edits help, but cold email is still a low-reply channel.
    LinkedIn messages 17.08% The in-platform inbox is where candidates expect recruiters.
    Email + LinkedIn, 2-step sequence 45.76% Versus 19.73% for email-only in the same report.

    Two other data points are worth knowing. Pin’s matched-candidate analysis of 165,000+ people contacted on both channels found that 78% of repliers answered only on LinkedIn, 17% only on email, and 5% on both (Pin channel comparison). Gem, which analyzed 6.2 million email sequences for its 2026 report, publishes its full benchmarks behind a download (Gem 2026 email outreach benchmarks).

    Why most InMails get ignored

    Candidates, especially engineers, see a steady stream of near-identical messages. Most fail for the same four reasons.

    • Wrong person. The profile never matched the role closely enough.
    • No reason. The message could be sent to anyone, so it reads that way.
    • Too long. A wall of company history buries the ask.
    • One shot. Many candidates simply miss the first message, and the recruiter never follows up.

    Notice that none of these is a subject line trick. Fix targeting and relevance first, and the formatting tweaks matter later.

    9 ways to improve your InMail response rate

    1. Send fewer, better-matched messages

    Tighter lists beat bigger lists. daily.dev’s roundup of InMail data reports that campaigns of about 50 recipients get roughly three times the replies of mass sends, though that is a secondary compilation, so test it on your own roles (daily.dev InMail statistics). Before you write a word, ask whether you would pass this profile to the hiring manager. If the answer is “maybe,” skip it.

    2. Open with a reason specific to them

    Name something real: a project, a repo, a talk, a stack choice, a promotion. One sentence of genuine relevance does more than three sentences about your company. Even basic personalization shows up in the data. In Pin’s email dataset, messages using the candidate’s first name replied at 5.13% versus 2.61% without it.

    First names are the floor, not the goal. Specifics are what separate you from the other twenty recruiters in that inbox.

    3. Keep it short

    daily.dev’s compilation, citing LinkedIn research, reports that InMails under 400 characters are 22% more likely to get a response. For email, Pin found the best reply rate (5.46%) at 150-199 words, while messages under 50 words did worst at 2.43%. So short is good, but not empty. Give enough to make a decision.

    4. Put the deal terms up front

    Engineers and other in-demand candidates decide fast. State the stack, work model, level and, where you can, the pay range in the first lines. Hiding these details forces a reply just to learn basics, and many candidates will not bother.

    5. Write a plain, short subject line

    Pin’s data shows subject lines of five to six words performed best at a 5.35% reply rate. Skip clickbait and “Quick question.” Name the role and the reason, such as “Staff backend role, your Kafka work.”

    6. Follow up two or three times

    Most replies do not come from the first message. In Pin’s data, the first three touches produced 93.2% of all replies, and a fourth added little (97.7% cumulative). Message 2 alone drew 33.7% of replies.

    So plan three touches, add new information each time, and stop. Candidates who reply to touch four are rare, and you risk annoying people you may want later.

    7. Add a second channel

    This is the biggest lift in the dataset. Pin reports 45.76% reply rate for two-step email plus LinkedIn sequences versus 19.73% for email-only, a 2.3x lift. Treat InMail as one touch in a sequence, not the whole plan.

    If you already hit your InMail credit limits, email gives you a way to reach candidates outside LinkedIn. Our guide to finding passive candidates beyond LinkedIn covers where to find them.

    8. Send on mid-week days

    In Pin’s email data, Thursday (5.16%) and Wednesday (5.14%) led, and Saturday (3.90%) trailed. The gaps are small, so do not rebuild your workflow around them. Just avoid weekends and test your own audience.

    9. Reply fast and make the next step easy

    Candidates reply quickly or not at all. Pin reports 74.8% of replies arrive within 24 hours, with a median of about four hours. If a reply sits in your inbox for two days, you are wasting the work you just did.

    Offer one concrete next step, like a 15-minute call or an async screen link, rather than “let me know your thoughts.”

    Before and after: a weak vs strong message

    The table below is an illustrative example, not measured data.

    Element Weak version Stronger version
    Subject Exciting opportunity! Senior data engineer, your Spark work
    Opener I came across your profile and was impressed. Your talk on streaming pipelines at a recent meetup matched what our team is building.
    Details Fast-growing company, great culture. Senior level, Python and Spark, remote in EU time zones, stated pay range.
    Ask Let me know if you are interested. Open to a 15-minute call Wednesday or Thursday?
    Follow-up None Two short follow-ups, each with new information

    How to measure it properly

    Total reply rate hides a lot. “Not interested” and “please remove me” count as replies, yet they do not fill a pipeline. Track three numbers per role: reply rate, positive reply rate, and replies that became a screen.

    Also segment by role family and seniority. A 12% rate on principal engineers might beat a 25% rate on junior roles. Review weekly, change one variable at a time, and give each test at least 100 sends so the result means something.

    Manual follow-ups and reply tagging eat recruiter hours, which is why many teams automate that layer. Our post on recruiter productivity shows where the time goes, and LinkedIn Recruiter alternatives compares tools if InMail credits are your bottleneck.

    FAQ

    What is a good recruiter InMail response rate?

    Aim for 15-25%. LinkedIn expects at least 13% for Recruiter and Recruiter Lite users over 100+ InMails per 14 days. Rates above 30% usually come from narrow, well-matched talent pools.

    How do I improve my InMail response rate?

    Start with targeting, then write a short message with a specific reason for contacting that person and the key role details up front. Follow up two to three times and add a second channel such as email. Track positive replies so you know what is working.

    How long should a recruiter InMail be?

    Short. A compilation citing LinkedIn research reports that InMails under 400 characters are 22% more likely to get a reply. Aim for three or four short sentences with the role, the reason, and one clear ask.

    How many times should I follow up with a candidate?

    Two or three follow-ups is usually enough. In Pin’s 2026 vendor data, the first three touches generated 93.2% of replies. After that, returns drop quickly.

    Is email or InMail better for cold outreach to candidates?

    In Pin’s 2026 data, LinkedIn messages replied at 17.08% against 4.96-6.31% for email. The channels reach different people, though, and combining them lifted two-step sequence replies to 45.76% from 19.73% for email alone.

    What is the best day to send recruiter outreach messages?

    Wednesday and Thursday led in Pin’s email data, and Saturday was weakest. The differences are modest, so message quality matters far more than send day.

    Why is my InMail response rate low?

    Usually the cause is weak targeting or a generic message, not the subject line. Check whether the profiles truly match the role, then check whether your opener gives a specific reason to reply. Fixing those two beats any formatting tweak.

    Conclusion

    Raising your recruiter InMail response rate is mostly a discipline problem: match tighter, say something specific, keep it short, follow up, and use more than one channel. Start with two changes this week, measure positive replies, and add the rest as you go.

    If the follow-ups and reply sorting are what slow you down, ConnectDevs Pilot sends multi-touch campaigns from your own Gmail, stops follow-ups when a candidate replies, and sorts replies into Interested, Meeting, Follow up, or Not now. To find better-matched candidates before you write, see AI sourcing.

  • Recruiting Email Templates for Engineers: 10 That Get Replies (2026)

    Recruiting Email Templates for Engineers: 10 That Get Replies (2026)

    Recruiting Email Templates for Engineers: 10 That Get Replies (2026)

    Good recruiting email templates for engineers share three traits: they are short, they mention something specific about the person and they ask one easy question. Engineers ignore messages that read like mass mail, so a template should be a frame you personalize, not a script you paste. This guide gives you ten recruiting email templates for engineers, from the first message to follow-ups and reactivation, plus the rules behind them.

    It is written for technical recruiters, agency owners and founders who send their own outreach. Every template uses placeholders in [brackets] that you must replace with real detail.

    TL;DR

    • Lead with one concrete observation about the engineer’s work, then link it to the role in one sentence.
    • Keep messages short. Pin cites a 2022 LinkedIn figure that InMails under 400 characters earned responses 22% above average.
    • Follow up two or three times. Pin also cites a 2024 Gem finding that a four-stage sequence drew about twice the replies of one email.
    • Personalize every message. If you cannot fill a bracket honestly, do not send it.

    Table of Contents

    Rules every engineering outreach email should follow

    An effective recruiting email for engineers is under 120 words, names a specific piece of the person’s work, states the essentials of the role and asks one low-pressure question. The essentials are the company, the problem the role solves, the location or remote policy and a pay range if you can share one.

    Reliable benchmarks are scarce, and most come from vendors. Our guide to recruiter outreach response rates reviews the data, including a Pin study of more than 400,000 candidate replies in which candidates showing signs of being between roles replied 74% more often. The lesson is that targeting beats clever copy. A perfect email sent to someone who is not movable still fails.

    Four habits matter more than wording:

    1. Be specific. Name a repository, talk, post or product the engineer worked on.
    2. Show the money and the stack. Engineers reply faster when the cost of replying is low.
    3. Ask one question. “Open to a 15-minute call this week?” beats a list of options.
    4. Respect no. Stop the sequence when someone declines.

    10 recruiting email templates for engineers

    1. First touch: a specific project

    Subject: Your [project or talk name] and a [role] at [Company]

    Hi [First name],

    I read your [post, talk or project] on [topic]. The part about [specific detail] stood out because we are working on a similar problem at [Company]: [one-line problem].

    We are hiring a [role] on the [team], [remote or location], paying [range]. The stack is [two or three tools].

    Open to a 15-minute call this week to see if it is worth a longer chat?

    [Your name], [title] at [Company]

    2. First touch: a career move

    Subject: After [past company], what next?

    Hi [First name],

    I noticed you spent [time] building [area] at [past company]. We are looking for someone with that depth to lead [project] at [Company].

    Pay range is [range], and the team is [size]. If a move is not on your mind, no problem. Would it help if I sent a one-page summary?

    [Your name]

    3. Referral-based

    Subject: [Referrer name] suggested I reach out

    Hi [First name],

    [Referrer name] mentioned your work on [topic] and thought you might want to hear about a [role] at [Company]. [One sentence on the role and why it fits them.]

    Happy to share the details by email first if a call feels like too much. Worth a look?

    [Your name]

    4. Founder to engineer

    Subject: Founder here: [role] at [Company]

    Hi [First name],

    I am the founder of [Company], where we [one-line product]. I am hiring our [first or next] [role] myself, and your work on [specific thing] is close to what we need.

    You would own [scope] and report to me. Pay is [range] plus [equity detail if real]. Want to see the product and talk for 20 minutes?

    [Your name]

    5. Agency to engineer, client unnamed

    Subject: [Role] for a [stage] [industry] company, [pay range]

    Hi [First name],

    I recruit [specialty] engineers at [Agency]. I am working with a [stage and industry] company that needs a [role] to [outcome]. Stack: [tools]. Pay: [range]. Location: [rule].

    I can share the company name once we speak and you confirm interest. Would a 10-minute call this week suit you?

    [Your name]

    6. Follow-up one: add new information

    Subject: Re: [original subject]

    Hi [First name],

    Following up with one detail I left out: [new fact, such as the team’s recent launch, the interview process length or remote policy].

    If the timing is wrong, tell me and I will stop writing.

    [Your name]

    7. Follow-up two: the polite close

    Subject: Last note from me

    Hi [First name],

    I will leave this here. If [role] at [Company] is ever of interest, reply to this thread and I will pick it up. Is there someone in your network who might want it?

    [Your name]

    8. Reactivating a silver medalist

    Subject: A new [role] that fits what you told us

    Hi [First name],

    You interviewed with us for [past role] in [month]. We did not move forward then, but you stood out for [specific strength]. We now have a [new role] where that matters.

    Interested in an update on what has changed? Happy to share the details first.

    [Your name]

    9. Replying when someone is not interested

    Subject: Re: [original subject]

    Thanks for the quick answer, [First name], and no problem at all. If you know an engineer who might like [role], I would be glad to talk to them. Either way, I will not message you again unless you ask.

    [Your name]

    10. Replying when someone asks for details

    Subject: Re: [original subject]

    Thanks for replying, [First name]. Here are the details: team [size and mission], stack [tools], pay [range], location [rule], process [number of steps and total time].

    If it still sounds interesting, here is my calendar link: [link]. Pick any 20 minutes.

    [Your name]

    Subject lines that work

    Keep subject lines plain and specific. Mention the person’s work or the role, not hype. Patterns that tend to read as human:

    • “Your [project] and a [role] at [Company]”
    • “Question about your work on [topic]”
    • “[Referrer] suggested I write”
    • “[Role], [pay range], [remote or city]”

    Avoid urgency tricks and all-caps. Test two versions on the same role and compare replies, not opens.

    How to build the sequence

    A simple sequence has three messages: a first touch, a follow-up with new information after a few days and a polite close. ConnectDevs’ Pilot page shows an example with a first email on day 0 and follow-ups at +3 and +5 days, sent from the recruiter’s own Gmail address. It stops follow-ups automatically when a candidate responds and sorts replies into categories such as Interested or Not now. Pilot is an outreach layer, not an applicant tracking system, and the dashboard figures on its page are illustrative.

    Send mid-week. In Pin’s dataset, replies sent on Tuesday or Wednesday were positive 64% of the time, versus 56% to 57% on weekends. The gap is modest, so test your own audience.

    Before you write, make sure you have the right address and the right people. Read our guide to finding candidate email addresses, and use AI candidate sourcing to build a target list of engineers whose skills match the role.

    Consent and compliance

    Rules vary by region, and this is general information, not legal advice. In the EU and UK, if you collect personal data from a source other than the person, Article 14 of the GDPR requires you to give required information no later than your first contact. In practice, add one line that says who you are, why you are writing and where you found their details. In the US, the FTC’s CAN-SPAM guide says the law has no exception for business-to-business email, so include sender details and a working way to opt out where it applies. Always honor a request to stop.

    FAQ

    What should a recruiting email to a software engineer include?

    Include one specific detail about their work, the company and problem, the stack, the location or remote policy, a pay range if possible and one easy question. Keep it under about 120 words.

    How long should a recruiter email be?

    Short. Pin cites LinkedIn data from 2022 showing InMails under 400 characters drew responses 22% above average. Treat that as directional and test your own.

    How many follow-up emails should I send?

    Two or three is common. Pin cites a 2024 Gem finding that a four-stage sequence drew about twice the replies of a single email. Add new information each time and stop when someone says no.

    What is the best day to send recruiting emails?

    Tuesday and Wednesday are a sensible default. In Pin’s dataset, replies on those days were positive 64% of the time, compared with 56% to 57% on weekends.

    Should I use templates or write every email from scratch?

    Use templates as a frame and personalize the opening and the role details every time. A message with no specific detail reads as mass mail and gets ignored.

    Is it better to email or use LinkedIn InMail?

    Neither wins everywhere. Test both for your role and respect privacy rules on contact data.

    Conclusion

    The best recruiting email templates for engineers are short frames that force you to be specific. Pick the template that matches your situation, fill every bracket with real detail, follow up with new information and stop when someone declines. Track replies per 100 messages and keep what works.

    Want to run campaigns from your own Gmail with reply tracking? Explore ConnectDevs Pilot and see how outreach hands off to AI interviews.

  • Recruiter Outreach Response Rate: What to Expect and 9 Ways to Improve It

    Recruiter Outreach Response Rate: What to Expect and 9 Ways to Improve It

    Recruiter Outreach Response Rate: What to Expect and 9 Ways to Improve It

    If your recruiter outreach response rate feels low, you are not imagining it. Passive candidates get a steady stream of near-identical messages, and most are ignored. The good news is that reply rates respond to a handful of controllable factors: who you contact, when, how long your message is and how many times you follow up.

    This guide explains what public data actually says about candidate replies, why trustworthy benchmarks are scarce, and nine changes that tend to lift replies. It is written for recruiters, sourcers, agency owners and founders who send their own outreach.

    TL;DR

    • Reliable, neutral benchmarks for recruiter reply rates are rare. Most published numbers come from vendors, so track your own baseline.
    • Targeting beats copywriting. Pin’s 2026 study found candidates between roles replied 74% more often than those with no job-market signal.
    • Follow-ups matter. A four-stage sequence drew about twice the replies of a one-off email, per a Gem figure cited by Pin.
    • Keep messages short, personal and specific, and send them mid-week.

    Table of Contents

    What is a good recruiter outreach response rate?

    There is no single trustworthy benchmark, because reply rates vary sharply by role, seniority, channel and message quality, and most published figures come from vendors measuring their own customers. Treat any headline number as a rough guide, not a target.

    The most useful recent dataset is a Pin study of more than 400,000 candidate replies. Two cautions apply. Pin sells recruiting software, and it classified replies with its own model. It also reports what replies look like, not what share of messages get one.

    Even so, the findings are practical:

    • Of replies scored for sentiment, 62.1% showed positive engagement, while 25.4% were “not interested”.
    • 69.2% of replies scored for job-seeking status came from people not actively looking.
    • Candidates showing signs of being between roles replied 74% more often than candidates with no job-market signal.
    • Candidates with a recently updated profile replied 23% more often.

    Your own baseline is worth more than any of these. Measure replies per 100 messages, split by role family and channel, then improve against yourself.

    Why candidates do not reply

    Candidates ignore outreach when it is generic, irrelevant, badly timed or missing the details they need to decide. Four causes show up repeatedly.

    1. Wrong person. A perfect message to someone who is not movable still fails.
    2. Generic opener. “I came across your impressive profile” signals a template within a second.
    3. Hidden essentials. No salary range, location rule or company name makes replying feel risky.
    4. No follow-up. Many candidates see a first message at a bad moment and never revisit it.

    Nine ways to improve your response rate

    1. Target people who can actually move

    Prioritize signals of readiness: recent profile updates, tenure that is ending, a recent layoff or a role change. In Pin’s data, flagged candidates still replied 34% more often to the same message across 1,799 roles, which suggests targeting alone moves results.

    2. Lead with their work, not yours

    Open with one concrete observation about a project, repository, talk or career move. Then connect it to the role in a sentence. If you cannot write that sentence honestly, the candidate is probably not a fit.

    3. Put the essentials in the first message

    Include the company, the problem the role solves, the location or remote policy and a pay range if you can. Candidates reply faster when the cost of replying is low.

    4. Keep it short

    Pin cites a 2022 LinkedIn figure that InMails under 400 characters drew responses 22% above average. Treat it as directional, but short messages are easier to answer on a phone.

    5. Ask one easy question

    “Open to a 15-minute chat this week?” works better than a paragraph of options. Make the next step obvious and small.

    6. Follow up two or three times

    Pin cites a 2024 Gem finding that a four-stage sequence drew about twice the replies of a single email. Space follow-ups by a few days, add a new detail each time and stop when the candidate says no. A recruiting-focused AIHR guide suggests that if a candidate has not replied after two or three contacts, they are unlikely to.

    7. Send mid-week

    In Pin’s dataset, replies sent on Tuesday or Wednesday were positive 64% of the time, versus 56% to 57% on weekends. The gap is modest, but timing is free to change.

    8. Use the channel the candidate uses

    Pin found email replies skewed toward scheduling and LinkedIn replies toward questions. If a public or work email is available and appropriate under local privacy rules, test both channels on the same role.

    9. Make replying feel safe

    Offer a short call, not a commitment. Say that you will keep the conversation confidential. Reply quickly when they answer. Our guide to reducing candidate ghosting covers the follow-through side of this.

    How to measure it properly

    Track reply rate and positive reply rate separately, by role family, channel and sequence step. A high reply rate full of “not interested” answers is a targeting problem. A low reply rate with a high positive share is a reach or timing problem.

    Metric What it tells you If it is low
    Replies per 100 messages Overall message and targeting health Check targeting, then subject and opener
    Positive reply share Quality of audience and offer Tighten the target profile and share more role detail
    Reply by sequence step Whether follow-ups earn their keep Add or reword follow-ups
    Reply to screen conversion Whether replies turn into conversations Speed up your response and scheduling

    Where automation helps and where it hurts

    Automation is good at consistency, sequencing and tracking, and bad at judgment about who to contact and what to say. It saves time on follow-ups, reply sorting and handoffs. It hurts when it multiplies a weak message.

    ConnectDevs approaches this in two parts. AI candidate sourcing helps you decide who to contact, using natural-language searches with human review. Pilot then sends multi-touch campaigns from your own Gmail, tracks opens, replies and bounces, stops follow-ups when someone responds and sorts replies into categories such as Interested or Not now. Interested replies can hand off to its AI interviewer for a first conversation.

    It does not replace your judgment. You still choose the audience, write or approve the message and decide who moves forward. For a wider look at what automation can safely take on, see our post on what AI recruiting agents actually automate.

    FAQ

    What is a good response rate for recruiter outreach?

    It depends on role, seniority and channel, and neutral benchmarks are scarce. Measure your own replies per 100 messages by role family and aim to beat that baseline each month.

    How many follow-ups should a recruiter send?

    Two or three follow-ups is a common practice. One data point cited by Pin found a four-stage sequence drew roughly twice the replies of a single email. Stop when a candidate declines.

    What is the best day to send recruiting emails?

    Pin’s dataset found replies on Tuesday and Wednesday were positive 64% of the time, versus 56% to 57% on weekends. Mid-week is a sensible default, but test your own audience.

    How long should a recruiter message be?

    Short. Pin cites LinkedIn data that InMails under 400 characters earned responses 22% above average. Lead with one specific point about the candidate and one clear ask.

    Do passive candidates reply to recruiters?

    Yes. In Pin’s study, 69.2% of replies scored for job-seeking status came from people not actively looking. Many are exploratory, so a low-pressure first ask works best.

    Is it better to use LinkedIn InMail or email?

    Neither wins everywhere. Email replies in Pin’s data skewed toward scheduling, and LinkedIn replies toward questions. Test both for your target role and respect local privacy rules on contact data.

    Conclusion

    Better outreach starts with better targeting, then short, specific messages, a sensible follow-up sequence and fast replies. Set your own baseline this week, change one variable at a time and keep the changes that lift positive replies, not just opens.

    Want to see a full outreach workflow? Explore ConnectDevs Pilot to see how campaigns, reply sorting and AI interview handoff fit together.