HN's Hire-Me Thread Now Averages 9+ YOE. Work It Like a Staff Bench.

Most sourcers still file Hacker News's monthly "Ask HN: Who Wants to Be Hired?" thread under "junior noise, ignore." That was true in 2019. It has not been true for two years, and a HireIndex analysis published January 28, 2026 finally proves it: the average poster now carries 9+ years of experience, and the junior tier has been quietly draining out.

The September 2026 thread is live at news.ycombinator.com/item?id=49522896. If you source staff engineers, it is the highest-signal free surface on the open web right now, and almost none of your competitors are working it.

What HireIndex actually found

HireIndex parsed three years of "Who Wants to Be Hired?" threads and found the average poster's experience rose from roughly 7.5 years in 2022 to 9+ years by December 2025 and January 2026, while junior (0 to 2 YOE) posts steadily declined. The full data is on HN at item 46795761.

Three details from the analysis matter for sourcing:

• The senior shift accelerated in 2023, tracking the tech-downturn layoff wave. New baseline, not a blip.
• The shift is less pronounced in US-only data, meaning international posters skew the average even more senior. The thread is a covert international staff pipeline.
• The declining junior share is a composition change, not just growth at the top. Juniors stopped posting because companies stopped hiring them there.

9+

The numbers side by side

Why the thread went senior

The junior collapse caused the senior shift. Companies stopped hiring 0 to 2 YOE developers, so the juniors who used to post to HN stopped bothering, and the 52,050 engineers laid off in Q1 2026 filled the vacuum with staff-shaped resumes. It is a supply-side story.

There are three specific reasons a laid-off staff engineer picks HN over LinkedIn:

1. Open-To-Work is a career-visibility risk. A staff engineer with a green banner signals "available" to their own leadership, their old manager, and every VC partner in their network. HN is pseudonymous by default.
2. Third-party recruiters ignore niche stacks. If you write Rust, Elixir, OCaml, or maintain a compiler in your spare time, the median LinkedIn InMail is worse than useless. HN filters the audience for you.
3. No algorithm, no middleman. The whoishiring bot posts the thread on the 1st of every month. There is no ranking, no boosted content, no recruiter DM layer. Seniors trust that.

As long as staff engineers keep getting laid off and LinkedIn keeps being LinkedIn, the trend holds.

The 49,437-person context

In Refolk's index, 49,437 professionals in the US currently hold a Staff Software Engineer or Staff Engineer title, concentrated in San Francisco, Austin, and Seattle. That is the shape of the pool the HN thread is starting to resemble, minus the coastal skew (HN posters are more remote-first and more international).

The interesting employers absorbing this cohort are not FAANG. In Refolk's index, the mid-stage infra, security, and health companies showing up repeatedly on the "current employer" line of ex-HN-posters include Vanta, Airbyte, Starburst, Omada Health, and Dragos. If you are a founder in that band, the HN thread is your peer group already, and you are competing with three other companies for each post, not thirty.

49,437

How to work the September 2026 thread this week

Treat the thread as structured data, not a message board. The post format is fixed: Location, Remote, Willing to relocate, Technologies, Résumé/CV, Email. Every field is machine-parseable. Most of your competitors are still using Ctrl+F.

A working outbound loop looks like this:

1. Pull the thread. Use HireIndex (hireindex.xyz) or Hire Hacker News (hirehackernews.com, built by AE Studio) as your parsed feed. Do not scrape by hand.
2. Filter on stack and location. Not on years of experience. The YOE line is often missing or sandbagged; the technologies line is honest.
3. Enrich each post against a professional-profile index. The résumé link plus an email plus a stack line is enough to resolve name, current employer, past titles, and GitHub in seconds.
4. Verify the email before sending. HN posts are 30+ days old by mid-month. Bounce rates climb fast.
5. Reference the post in the first line. "Saw your Sept HN post, the Kafka + Rust combo is why I am writing" outperforms any generic opener.

Step 3 is where the workflow breaks for most teams. You have a name and a stack but no reliable way to resolve them into a current profile at scale. That is the gap Refolk closes: describe the person you want in plain English and Refolk returns the ranked shortlist across GitHub, LinkedIn, and the open web, with current employer and verified email attached.

The international arbitrage nobody is pricing

HireIndex noted the senior shift is much less pronounced in US-only data, which means non-US posters skew the average even more senior. The HN thread is now a covert international staff pipeline, and it is under-priced because most sourcers reflexively filter LinkedIn Recruiter to US-only.

If your company sponsors, or hires remote in EMEA and LATAM, the arbitrage is real:

• Senior developer unemployment sits near 1% in the US. The pool is thin and expensive.
• The same title in Berlin, Lisbon, São Paulo, or Bangalore posts to HN because there is no equivalent local channel with the same audience quality.
• Time zones and language filter themselves through the "Remote" and "Willing to relocate" fields of each post.

Re-ranking your HN pull on non-US posters first is a five-minute change that most teams will not make. Do it in September.

The HN thread is the only free hiring surface where the supply is more senior than the demand.

The junior counter-example worth naming

The trend has one visible counter-example: IBM, under CHRO Nickle LaMoreaux, has been tripling its junior developer intake while most of the industry cut entry-level. That matters for two reasons.

First, it tells you the junior collapse is a choice, not a market law. Big Tech's junior hire share fell from 32% in 2019 to 7% in 2026, and entry-level postings dropped 67% from 2022 to 2024, because leadership decided AI tooling replaced the junior tier. IBM decided otherwise.

Second, it tells you where the juniors went. If you actually want to source 0 to 2 YOE engineers in 2026, IBM's intake pipeline, the university career centers it recruits from, and the graduate rotational programs at similar counter-cyclical hirers are a better surface than HN. Stop asking the HN thread to be something it stopped being in 2023.

What to do if you are a founder posting, not sourcing

Post to the companion thread. HN's whoishiring bot posts three threads on the 1st of every month: "Who Wants to Be Hired?", "Who Is Hiring?", and "Freelancer? Seeking Freelancer?". If you are a founder, the "Who Is Hiring?" thread is your equivalent surface, and it is read by the same senior cohort that posts across the aisle.

Two things move response rate on a "Who Is Hiring?" post:

• Name a specific person you want, not a job title. "Looking for the person who ran the SRE on-call rotation at a Series C infra company" gets replies. "Senior Software Engineer, 7+ YOE" gets skipped.
• Include a plain email, not a form. The HN reader base actively downranks Greenhouse links.

Both threads reward specificity. That is the same muscle you use in Refolk queries: describe the person, do not describe the requisition.

FAQ

When does the next HN "Who Wants to Be Hired?" thread post?

The whoishiring bot posts a new thread on the 1st of every month, along with "Who Is Hiring?" and "Freelancer? Seeking Freelancer?". The schedule has held for years. If you want to work the October 2026 thread, have your enrichment pipeline ready by end of September, because the highest-quality replies happen in the first 72 hours before the thread falls off the front page.

Is HireIndex or hirehackernews.com the better tool?

Both parse the same underlying threads, so treat them as interchangeable feeds. HireIndex (hireindex.xyz) has the better public analysis, including the three-year YOE trend published January 28, 2026. Hire Hacker News (hirehackernews.com, built by AE Studio) has cleaner filtering by stack and remote status. Neither runs the outbound loop for you, which is where the actual sourcing work happens.

Why not just use LinkedIn Recruiter for staff engineers instead?

Because staff engineers actively avoid the Open-To-Work signal on LinkedIn, and InMail reply rates on senior technical roles run in the low single digits. The HN thread is the reverse: everybody posting has already raised their hand. You are trading a much smaller candidate universe (a few hundred posts per thread) for a much higher intent signal, which is the right trade for a hard-to-fill role.

How do I filter for genuinely senior posters without a YOE field?

Do not rely on the self-reported years line, which is inconsistent. Instead, filter on the Technologies line (compiler work, distributed systems, kernel, cryptography, and infra stacks skew senior) and enrich each post against a profile index to check title history and tenure. A poster whose last two roles were Staff or Principal is a staff engineer regardless of what their HN post claims.