HN "Who Wants to Be Hired" Beats Open-to-Work 3,584:1 at Staff Tier

If you source senior engineers for a living, LinkedIn's Open-to-Work badge resolves to a two-digit number nationwide at the staff tier. The November 2026 Hacker News "Who wants to be hired?" thread, posted on the first business day of the month by the whoishiring account, is a denser, cleaner, better-tiered candidate pool than that badge, and the numbers below say it isn't close.

The common take is that Open-to-Work is "where candidates live" and HN is a nostalgia play. The index tells the opposite story.

The headline number: 69 vs 247,296

In Refolk's index, exactly 69 US-based people with a current title of Senior or Staff Software Engineer carry "open to work" in their current headline, against 247,296 US Senior, Staff, and Principal engineers at Senior+Strategic seniority. That is a 1-in-3,584 public-signal ratio, or 0.028%.

The 220M Open-to-Work figure CNBC cites is real, and it jumped 35% year over year. It is also almost entirely non-engineers and junior to mid ICs. For the staff-tier search you are actually being paid to run, the public OTW flag resolves to a two-digit number nationwide.

0.028%

Meanwhile a single HN "Who wants to be hired?" thread reliably draws 300 to 700 top-level posts, each one a self-authored block with a predictable template. One thread, in one morning, surfaces more actively-looking senior engineers than LinkedIn's public OTW signal yields for the entire United States.

What the thread actually contains

Each top-level comment follows a community template that has been stable for years: Location, Remote, Willing to relocate, Technologies, Résumé/CV, Email, and usually a comp or role preference line. That is seven structured fields per candidate, free, parseable, and consented.

Compare that to what an Open-to-Work profile hands a recruiter through LinkedIn's UI: a job title preference, a location preference, and a work-type preference. Three fields. No stack. No résumé. No email. No code.

The October 2026 thread (item 49922568) has three posters I would put on a staff-tier shortlist on sight: Hello71 (Linux kernel perf, an 800× hot-path throughput win, a QEMU CVE), juliooocon (NeurIPS 2025 presenter, LLM agents plus C++ vision), and Avishy (ex-VP R&D in games, work-authorized in US, CA, and IL). Three staff-tier candidates in one thread, each with a résumé link and an email, in a format a parser handles in under 50 lines of Python.

Why Open-to-Work is a near-empty signal at the senior tier

Senior engineers do not advertise job hunger in public. They have the strongest employer-trust tax, the biggest counter-offer exposure, and the deepest aversion to inbound spam. The HN thread flips the tradeoff by giving them a venue where disclosure is the norm, the audience is self-selected founders and engineering leaders, and the signal expires in 30 days.

Three structural reasons the gap stays wide:

• Employer leakage. LinkedIn's "Recruiters only" OTW mode cannot reliably hide the flag from recruiters at the user's own company. Senior engineers know this, so they do not toggle it.
• Stale flags. LinkedIn quietly disables OTW for inactive users without clear notification. A chunk of the 220M number is zombie.
• Response-rate ceiling. LinkedIn Talent Solutions reports a 14.5% positive response for OTW profiles vs 4.6% for everyone else. The gap is real, but it averages across a pool where senior engineers are statistically absent.

Senior engineers do not advertise job hunger in public. The HN thread is the one venue where disclosure is the norm instead of the tell.

The parsing playbook, in six steps

HN who wants to be hired parsing is a solved problem. You do not need to build a scraper; two open-source Apify actors already do the extraction. The work is the enrichment on top.

1. Grab the thread. The November 2026 item ID is linked from the whoishiring user page. Each monthly post is a static URL, so a Google dork like "Ask HN: Who wants to be hired?" ("November") AND "2026" finds it in one query.
2. Run a parser. m_ctim/hn-whos-hiring-parser extracts location, remote, relocation, stack, résumé URL, and emails as structured rows. solidcode/hackernews-scraper adds a 60-technology dictionary (Python, Rust, React, Kubernetes, Postgres, AWS, and so on) applied per post.
3. Regex the GitHub handles. A github\.com/[\w-]+ sweep over the full comment body converts the thread into a code-portfolio pipeline. This is the move that makes HN beat OTW for sourcing passive candidates GitHub-first: Open-to-Work exposes zero code, the thread exposes a repo list.
4. Enrich the handles. For each GitHub username, pull public repos, primary languages, and recent commit activity. A candidate who lists "Rust, distributed systems" and whose top repo is a 2026 tokio contribution outranks a candidate who lists the same stack with no code trail.
5. De-dupe against your ATS. The HN thread is public, so your competitors are parsing it too. Winning is a function of who contacts first with a message that proves they read the post.
6. Write back in 24 hours. HN meta-threads report roughly 50% apply-to-offer rates for posters who get contacted inside the first day. The signal decays fast.

The whole flow is a weekend script, or an afternoon if you lean on an off-the-shelf parser. The hard part is deciding which 40 of the 500 posters match the role you are actually sourcing for.

That is the gap Refolk closes for this workflow: describe the slice of the thread you want in plain English, and the ranked shortlist comes back with the GitHub signal already joined.

The thread aged 1.5 years in 36 months

HireIndex, a Show HN project from January 2026, parsed three years of "Who wants to be hired?" threads and found the average poster now carries 9+ years of experience, up from roughly 7.5 YOE. The thread aged a year and a half in three calendar years.

Two things drove it:

• Juniors left. The entry-level crunch pushed junior ICs to Discord servers, Wellfound, and university job boards. The thread's floor rose with them gone.
• The Freelancer thread sunset. HN discontinued "Freelancer? Seeking freelancer?" after October 2025, concentrating contractors and fractional staff engineers into "Who wants to be hired?". That population is senior by definition.

The practical consequence: a 2019 sourcing playbook that treated HN as a junior pool systematically mis-tiers the modern thread. If you have not re-read the format since 2022, you are leaving staff candidates on the table every month.

Alternatives to LinkedIn Open-to-Work, ranked

The cleanest alternatives to LinkedIn Open-to-Work for staff-tier sourcing, in order of signal density:

1. HN "Who wants to be hired?" monthly thread. Highest density per candidate, GitHub-linked, consented, 30-day freshness.
2. GitHub contribution graphs on actively maintained repos. No stated availability, but a stale-check against a 90-day commit window plus a company-change signal is the strongest passive filter available.
3. Conference speaker lists (NeurIPS, Strange Loop, PlatformCon, QCon). Lower volume, extremely high tier, no disclosed availability.
4. Open-source Discords and language-specific Slacks (Rust, Zig, Elixir). Context-rich, but a messy export.
5. LinkedIn Open-to-Work. Useful at mid-level and for non-engineering roles. Near-empty for staff+ engineering.

Each tier down costs you volume. Each tier up costs you noise. The thread is the one row that gives you both density and tier at the same time.

What to do with the November 2026 thread this week

Pull the November item ID, run a parser, and do three passes:

• Pass 1, 30 minutes: filter for your stack keywords and your timezone. This drops the pool from ~500 to ~80.
• Pass 2, 1 hour: read every GitHub link in the remaining 80. Keep the 20 whose public code matches the role's actual work, not the title.
• Pass 3, 2 hours: write 20 personal replies that quote the poster's own repo. First-touch quality is the entire game.

10:1

FAQ

When does the HN "Who wants to be hired?" thread post?

The whoishiring account posts on the first business day of every month, usually between 11:00 and 15:00 UTC. The companion "Who is hiring?" thread posts the same morning. Both are static URLs you can bookmark by item ID, and the full year of 2026 threads is reachable from the account's submission history.

Is scraping HN threads allowed?

Yes. HN exposes a public API (hn.algolia.com and the official Firebase endpoint) that returns every comment as JSON. The threads themselves are public and consented posts, and multiple commercial parsers (Apify's m_ctim/hn-whos-hiring-parser, solidcode/hackernews-scraper) have been live for years without issue. Respect rate limits and do not spam the posters.

How is this different from "Who is hiring?"

"Who is hiring?" is the employer-posting thread; "Who wants to be hired?" is the candidate-posting thread. They run on the same morning. For sourcers, the second one is the asset: 300 to 700 self-described candidates per month with stack, location, GitHub, and email, in a template that has been stable for years.

What about Open-to-Work for non-engineering roles?

For mid-level ICs in sales, support, design, operations, and marketing, Open-to-Work still carries real signal and the 14.5% response-rate lift is reproducible. The argument in this piece is scoped to senior and staff engineers, where the public OTW headline resolves to 69 US profiles and the HN thread is the better pool by multiple orders of magnitude.