The 4.77% InMail Trap: Send GitHub First for Engineers

Every sourcer I talk to still opens the day inside LinkedIn Recruiter. The 2026 benchmark data says that is now the worst first-touch decision you can make for engineers, designers, and anyone else with a public body of work. The September 2026 "Ask HN: Who is Hiring?" thread went live this week with 105 jobs and 130 candidates on the companion aggregator, and it is a working case study of the channel most recruiters ignore.

The one-number version: 4.77% vs a 30%+ ceiling

LinkedIn InMail response rates in the Software and SaaS vertical sit at 4.77% in 2026, per Overloop's benchmark set. Ashby's sourcing data shows email sequences with AI personalization tokens hitting 35.3%, up from 24.1% without them. On comparable outreach, that is roughly a 6x delta for the price of changing where and how you send message one.

The mechanism is not that GitHub or email is magic. It is that the person you want has been hit repeatedly this quarter on LinkedIn with a template that opens "I came across your impressive background" and zero times on the platform where they actually spend Saturday morning.

4.77%

The "13% floor" is a leash, not a benchmark

LinkedIn Recruiter's overall average response rate is around 13%, and that number does double duty: fall below it across 100+ InMails in a rolling 14-day window and LinkedIn triggers an InMail Improvement Period that can restrict your seat's bulk sending. It is written into LinkedIn Recruiter Help.

Read that against the vertical data:

• Overall LinkedIn Recruiter average: ~13%
• Talent acquisition specifically: ~12%
• Legal and Professional Services (highest tracked): 10.42%
• Software and SaaS (lowest tracked): 4.77%

If you source engineers at volume on a stock LinkedIn Recruiter seat, the platform structurally punishes you for doing the job you were hired to do. The Software and SaaS vertical average is less than half the throttle threshold. There is no such penalty on GitHub, on a Rust Discord, or in a well-run HN thread. That is not a philosophical point about candidate experience. It is a compliance mechanic that quietly caps your daily send volume on the exact segment where the platform performs worst.

The matched-cohort proof: channel moves reply rate 3 to 4x on the same people

The only honest way to compare channels is to send to the same people through each one, and Pin did exactly that. On identical people, 16.6% replied via LinkedIn versus 4.4% via email. More interesting: 15.5% replied on LinkedIn while staying silent on email, versus 3.3% who replied only on email.

That study happens to favor LinkedIn against email. The point is the size of the delta on identical humans: channel choice moves reply rate 3 to 4x without touching the shortlist or the copy. Every "GitHub gets 35%" or "InMail gets 12%" number you have ever read compared different audiences and is therefore mostly noise. Matched-cohort data is the standard. Ask any vendor quoting you channel benchmarks whether their number is matched. It usually is not.

The 2026 benchmark table

Here is the dataset a sourcing lead should have taped to the monitor. Every row is a 2026 figure, and each source is public.

Two rows deserve a second look. Ashby's personalization lift (24.1% to 35.3%) is the largest single lever in their dataset and it operates on any channel. And in Refolk's index, US Rust talent is 4.6x scarcer than US Go talent, which is the exact type of pool where LinkedIn template blindness is worst and off-LinkedIn identities are least contested.

Follow-ups beat channel switching until you hit the ceiling

If you are running single-send campaigns, fix that before you touch channel strategy. Ashby's sourcing sequence data shows a one-email sequence replying at ~7%, two emails at ~15%, and three at ~23%, after which returns plateau. Across multiple datasets, follow-ups drive 42 to 58% of all replies. A single-send campaign forfeits roughly half its potential response before message one lands.

The ordering that actually works:

1. Get to 3 touches per candidate on your current channel.
2. Add first name and one specific detail per message. Pin's data shows first name alone lifts reply rate from 2.61% to 5.13%.
3. Only then start channel-shifting to break the 23 to 35% ceiling.

Channel choice is a ceiling-breaker, not a cold-start fix. If your InMail sequence is one message with a "Hi {FirstName}, saw your impressive background" opener, you have a copy problem, not a LinkedIn problem.

Channel choice is a ceiling-breaker, not a cold-start fix. Fix the sequence first, then leave LinkedIn.

The refund-adjusted math LinkedIn does not want you to run

LinkedIn refunds an InMail credit on any reply within 90 days of send. That flips the "InMail is expensive" narrative, but only for top-quartile senders. A sourcer at 30%+ reply rate effectively pays for InMails at a discount. A Software and SaaS sourcer at 4.77% pays roughly 6x the sticker price per useful contact, because roughly 95 of every 100 credits burn without a refund. Glozo's cost-response math puts it plainly: a 10% response rate doubles your effective per-credit cost against a 30% one.

The exercise is worth ten minutes:

• Pull your last 200 sent InMails from Recruiter.
• Count replies (any reply) within 90 days.
• Divide seat cost by net (unrefunded) credits used.
• Compare to the fully loaded cost of a GitHub-first workflow (your time to identify plus email find plus send).

Run the number before you renew the seat. It is the cleanest way to price the channel you are actually paying for, not the one on the marketing page.

The niche channels that actually work per function

Off-LinkedIn recruiting is not one channel, it is a function-specific stack. The mistake is trying to source designers on GitHub or infra engineers on Behance. Match the channel to where that role actually publishes work.

• Backend, infra, systems: GitHub org pages, Rust-lang Discord, CNCF Slack, HN "Who is Hiring"
• ML and data: Kaggle, HuggingFace profiles, Stack Overflow contributors
• Design: Behance, Dribbble
• Frontend: GitHub, dev.to authors
• Community-native generalists: r/ExperiencedDevs and equivalent subreddits

The unifying principle: the candidate has done something public on that channel that gives you a legitimate opening line. "I saw your PR on tokio-rs/tokio last month tightening the wakeup loop" is not a template. It cannot be, because you had to read the PR.

This is the exact gap Refolk closes for teams that do not have hours per role to hand-audit GitHub. You describe the person in plain English and get a ranked shortlist with the public artifacts already attached.

The HN September 2026 thread is a live case study

The "Ask HN: Who is Hiring? (September 2026)" thread (item 49522897) is live with 105 jobs, and hnmatchmaker.com is tracking 130 candidates against those roles. Uncountable is hiring full-stack engineers at $130k to $220k. Monumental is hiring robotics engineers in the same band. These are serious salaries flowing through a channel most in-house sourcing teams have never opened.

Two things about HN matter for reply rates:

1. Candidates in the companion "Who wants to be hired" thread have explicitly opted in. You are not cold at all, you are responding to a public "hire me" post.
2. The "Who is Hiring" thread is a competitive intelligence goldmine even if you never source from it. Every company posting there is hiring engineers this month with a stated comp band, which is a cleaner signal than a LinkedIn job post that has been stale for six weeks.

Refolk's index cross-references public GitHub activity with employer history, which is why "who at Cloudflare, NVIDIA, Kraken, or Temporal Technologies just started contributing to a competing project" is a query I can answer in one line. Those four companies employ a large share of the US Rust cohort and all have public GitHub orgs, so the sourcing is entirely doable without loading LinkedIn once.

The scarce-skill rule: the smaller the pool, the bigger the off-LinkedIn payoff

The channel-switch payoff scales inversely with pool size. In Refolk's index, the US Rust pool is 3,498 people versus 16,166 for Go, a 4.6x scarcity ratio. That scarce pool gets hit constantly on LinkedIn with identical templates, which is why template blindness is worst there and why any signal of "I actually read your work" outperforms 10 InMails.

For scarce cohorts, the ordering is inverted from your usual playbook:

1. Identify the pool off-LinkedIn first (GitHub, conference speaker lists, niche Discords).
2. Enrich with LinkedIn only to confirm current employer and tenure.
3. Send on the channel where they actually got noticed.

For abundant pools (generalist backend engineers in the US), LinkedIn is still a defensible starting point if your sequence and personalization are tight. The channel decision is a function of pool scarcity, not a religious position.

What to change on Monday

The action list is short and none of it requires new tools:

1. Pull your last 200 InMails. Compute refund-adjusted cost per reply. If Software and SaaS is your vertical, expect a number that makes GitHub-first look obvious.
2. Add a third touch to every sequence. Ashby's data says you go from ~15% to ~23% for the cost of two more sends.
3. For every scarce-skill role, identify 20 candidates on their native channel (GitHub, Kaggle, Behance) before you open LinkedIn.
4. Rewrite message one to reference one specific public artifact per candidate. Not a template variable, an actual sentence.
5. Monitor the HN "Who is Hiring" thread on the first business day of each month. Ten minutes, free, and it moves faster than any job board.

Off-LinkedIn recruiting is not a rebellion against LinkedIn. It is refund-adjusted math plus the fact that scarce talent lives on the platforms where they built the thing that made them scarce.

FAQ

What is the average LinkedIn InMail reply rate in 2026?

The overall LinkedIn Recruiter average is roughly 13%, but the number varies sharply by vertical. Talent acquisition specifically averages around 12%, Legal and Professional Services leads the tracked verticals at 10.42%, and Software and SaaS sits at the bottom at 4.77%. The 13% number also functions as LinkedIn's throttle threshold: seats that fall below it across 100+ InMails in a 14-day window can trigger an InMail Improvement Period.

Is GitHub sourcing actually better than LinkedIn for engineers?

For scarce technical skills, yes, and the effect is largest for the scarcest pools. Ashby's sourcing benchmarks put personalized email sequences at 35.3% against 4.77% InMail replies in Software and SaaS. The mechanism is not the channel itself, it is that GitHub-first outreach forces you to reference the candidate's actual public work, which defeats the template blindness that has killed LinkedIn response rates for engineers.

How do I compute my real cost per InMail reply?

Pull your last 200 sent InMails from LinkedIn Recruiter, count replies within 90 days (LinkedIn refunds credits for any reply in that window), divide your seat cost by the net unrefunded credits used. Glozo's math shows a sourcer at 30% reply rate pays roughly half the effective per-credit cost of a sourcer at 10%. Run the number before you renew the seat.

Where does Refolk fit in an off-LinkedIn workflow?

Refolk indexes people across GitHub, LinkedIn, and the open web, so you can describe the person you want in plain English and get a shortlist with the public artifacts (PRs, repos, conference talks, published designs) already attached. That removes the biggest friction of GitHub-first sourcing, which is the hours of manual auditing needed to turn "contributes to tokio" into a ranked list of humans with current employers and reachable contact points.