HireIndex Just Aged HN's Hiring Thread to 9+ Years. Source It Like Staff-Plus.

The July 2026 "Who wants to be hired?" thread went live on Hacker News this week, and if you're still treating it as a generalist candidate pool you're a year behind the data. HireIndex, a searchable directory built on three years of those threads, published a cut in January 2026 that quietly reframed the whole channel. The median poster is no longer a scrappy mid-level. It's a staff-plus engineer, and the demographic keeps drifting older.

What HireIndex actually found

HireIndex (hireindex.xyz) launched as a Show HN in July 2025 and re-posted with a three-year analytics cut in January 2026. The headline number: average poster experience climbed from roughly 7.5 years in 2022 to 9+ years by December 2025 and January 2026. Junior posters (0 to 2 years of experience) have declined steadily across the same window. Post volume also spiked starting in 2023, tracking the tech downturn almost perfectly.

That last correlation matters. "Who wants to be hired?" is inversely correlated with market health. When posts jump, senior engineers are getting shaken loose, and the thread turns into a buyer's market for anyone hiring Staff+ talent. Volume is a signal, not just supply.

9+

The US-vs-rest gap is the actual story

Buried in HireIndex's Show HN post is the more interesting finding: the seniority skew is muted in US-only data. The global "aging" is disproportionately pulled by European and APAC posters. That reframes HN again. It isn't just a staff-plus channel. It's closer to a global senior remote marketplace, and the sourcing motion for that is very different from "SF startup pipeline."

The February 2026 thread makes this concrete. FUTO posted for a Senior Infrastructure & Platform Engineer. Atomic Tessellator recruited developers within four hours of UTC+12. Charted Sea hired a Senior Product & Platform Engineer requiring four-hour overlap with UTC+8. That's the mix now: senior, remote-heavy, timezone-gated, employer-driven.

Why the thread aged in place

The tempting narrative is "juniors got locked out." The truer story is that HN was never a junior channel, and the core cohort literally aged. Combine that with layoffs pushing 8 to 10 year engineers back into the open market and the median naturally drifts up.

The macro data underneath is brutal for early-career developers:

• Indeed Hiring Lab reported senior tech job titles down 19% versus five years earlier, while standard or junior titles fell 34% as of February 2025.
• Stanford's Digital Economy Lab found software developer employment for ages 22 to 25 fell nearly 20% from the late-2022 peak by July 2025. Workers aged 30 and over in the same AI-exposed category saw employment rise 6% to 12%.
• At least 127,000 U.S. tech workers were laid off in 2025. So far in 2026, TrueUp counts 435 tech layoff events impacting 164,971 people, and the survivors are disproportionately Staff+, platform, infrastructure, and security.

164,971

AI tooling amplifies the effect. Senior developers write code roughly 22% faster with Copilot. Juniors only 4% faster. AI amplifies existing expertise rather than creating it, which is why companies that used to hire two mid-levels now hire one Staff+ engineer. That is precisely the profile HN surfaces, and it's the profile HireIndex is watching age forward.

How to actually source the July 2026 thread

Stop reading top-to-bottom. The thread now behaves like a niche staff-plus board with a strong remote-EU/APAC lean. Treat it that way.

1. Filter for seniority before you filter for skills

If the median is 9+ years, your default filter should be "8+ years, has led a project or team, has shipped in production at scale." Anything below that is noise inside this channel, not signal. Save the mid-level and junior slots for other channels entirely.

2. Read timezone before role

The Feb 2026 examples (Atomic Tessellator at UTC+12±4, Charted Sea at UTC+8±4) tell you that remote-timezone gating is now a first-class field. Extract it from every self-post before you extract the tech stack. If your team is US-only synchronous, half the thread is structurally irrelevant.

3. Cross-reference posters against GitHub and LinkedIn

Every "Who wants to be hired?" self-post is a candidate declaring intent in public. That's rare and valuable. But the post itself is thin. You need the GitHub contribution graph, the LinkedIn tenure history, and any conference talks or blog posts before you reach out. Doing that manually across 400+ posts is where most sourcers give up.

This is the exact friction we built Refolk for: describe the person in plain English ("staff infra engineer, 10+ years, posted in HN July 2026, based in EU, has shipped Kubernetes at scale") and get a ranked shortlist that stitches the HN post to the GitHub profile to the LinkedIn history to any open-web presence. Refolk indexes roughly 178,000 engineers globally at Staff, Principal, and Staff Software Engineer titles, with clusters in NYC, Boulder, Amsterdam, and Bengaluru, which happens to be the exact profile now dominating HN threads.

4. Compare against adjacent HN tooling

HireIndex isn't the only cut of this data. hirehackernews.com by AE Studio, nthesis.ai/public/hn-who-is-hiring (semantic search plus UMAP visualization), dheerajck.github.io/hnwhoishiring, and hnjobs.emilburzo.com all index the same threads with different affordances. Use them as complements. HireIndex is best for the historical seniority cut. nthesis.ai is best for semantic clustering when you're looking for something like "post-quantum cryptography" that doesn't keyword-match cleanly.

Where the juniors went, and where to send yours

If you actually need junior or new-grad engineers, HN is the wrong pond and it has been for at least two years. The juniors didn't vanish. They moved channels.

The public narrative is starting to catch up. OpenAI and Anthropic are hiring juniors for the first time. Netflix started onboarding new grads after 25 years of senior-only hiring. Shopify takes on 1,000 interns per year, and Cloudflare plans to onboard over 1,100 in 2026. Those pipelines don't run through "Who wants to be hired?"

They run through:

• GitHub open-source PR history. Contribution graphs are now the living resume for early-career engineers. Look at consistent commits to non-trivial repos, not stars.
• Discord tech communities and daily.dev. These are where juniors talk to each other and where hiring managers who understand this generation actually recruit.
• r/cscareerquestions "Mentor Monday" threads and Frontend Mentor community. Bloomberry's data shows entry-level remote roles are only 2.48% of postings versus 5.35% for senior, so juniors compete brutally on any open board. Communities where they can demonstrate work over weeks beat cold applications.
• Stack Overflow tag activity. Still underrated for finding juniors who genuinely know a niche.

HN was never a junior channel. It just aged in place, and the demographic never renewed. </pull>

If you're a founder with one junior slot and one Staff+ slot, run two different motions. The Staff+ slot lives on HN, HireIndex, and inbound from your own network. The junior slot lives on GitHub, Discord, and mentorship-adjacent communities. Refolk handles both, but the queries look completely different. "Find me a Staff platform engineer who posted in the last three HN threads" is a very different search from "Find me a self-taught junior with 18 months of consistent open-source PRs to a Rust project I care about."

The technical recruiting channels stack in mid-2026

Zoom out. HireIndex is a symptom of a larger reorganization of technical recruiting channels. Here's what the stack actually looks like now:

• Staff+ inbound and passive: HN "Who wants to be hired?" (via HireIndex, hirehackernews.com, nthesis.ai), LinkedIn Recruiter for tenure history, GitHub for shipped work.
• Mid-level active search: LinkedIn plus GitHub cross-reference, plus targeted outbound to specific companies that just had layoffs.
• Junior and new-grad: GitHub contribution graphs, Discord, daily.dev, Frontend Mentor, targeted university and bootcamp partnerships.
• Niche specialists (ZK, monokernel, post-quantum, ML infra): Semantic search across GitHub, arXiv author lists, and conference speaker rosters. LinkedIn boolean falls apart here.

The common thread across all four is that keyword boolean is dying. The signal has moved to what people actually ship, where they show up in public, and how their tenure and interests cluster. That's why a plain-English query beats a 40-line boolean string in 2026, and why we keep pushing Refolk in that direction: you describe the person, the tool finds them across GitHub, LinkedIn, and the open web.

The next 12 months of HN threads

Two predictions from the HireIndex data:

1. The US-vs-rest gap will widen. As US layoffs slow and hiring returns, the strongest US Staff+ candidates will get placed through networks and stop posting. The thread's global median will keep drifting up because EU and APAC senior engineers will keep using it as a remote-work marketplace.

2. Junior posts will approach zero. Not because juniors don't exist, but because the return on posting in a staff-heavy thread is negative. They'll self-select out and the thread will complete its transition to a senior-only channel.

If both predictions hold, "Who wants to be hired?" becomes one of the cleanest signals in senior technical recruiting: high-intent, self-declared, timezone-tagged, and public. HireIndex will keep being the right lens on it. And the sourcers who adapt their motion (Staff+ filters, timezone-first, GitHub cross-reference) will pull ahead of the ones still copy-pasting the whole thread into a spreadsheet.

FAQ

Is Hacker News's "Who wants to be hired?" thread worth sourcing from at all in 2026?

Yes, but only for Staff+ and senior specialist roles, and only if you're comfortable with a remote and often non-US candidate pool. HireIndex's three-year data shows the median poster is 9+ years experienced and the thread skews heavily toward EU and APAC remote engineers. If your open reqs are mid-level or junior, or if you need US-timezone synchronous work, you'll get better yield from GitHub, LinkedIn, and community channels instead.

What is HireIndex and how is it different from other HN sourcing tools?

HireIndex (hireindex.xyz) is a searchable directory built on the Ask HN "Who wants to be hired?" threads, launched in July 2025 and updated with a three-year analytics cut in January 2026. Its edge is the historical seniority and geography analysis. Alternatives like hirehackernews.com by AE Studio, nthesis.ai/public/hn-who-is-hiring, and hnjobs.emilburzo.com offer different affordances: semantic search, UMAP clustering, or simple filtered browsing. Most serious sourcers use two or three of them together.

Where should I actually source junior engineers now?

GitHub contribution graphs, Discord tech communities, daily.dev, Frontend Mentor, and r/cscareerquestions "Mentor Monday" threads are where juniors demonstrate work and get discovered in 2026. Companies like OpenAI, Anthropic, Netflix, Shopify, and Cloudflare have all restarted or expanded junior pipelines, and none of those pipelines run through HN. Bloomberry's data on remote posting mix (2.48% entry-level versus 5.35% senior) explains why juniors can't compete on open boards and need community-based discovery instead.

How do I efficiently cross-reference HN posters against LinkedIn and GitHub?

Doing it manually across a 400-post thread is where most sourcers give up. A plain-English query tool that stitches HN posts to GitHub commits and LinkedIn tenure in one pass is now the practical answer. Refolk was built for exactly this: you describe the person ("Staff infra engineer, posted July 2026 HN, EU-based, Kubernetes in production") and get a ranked shortlist with the three profiles already linked, so you can go straight to outreach instead of tab-juggling.