HN "Who Is Hiring" Is Down 61%. Agentic Roles Are Up 10,854%.

The July 2026 "Ask HN: Who is hiring?" thread went up on July 1 and landed with a thud. hntrends.com, the canonical keyword-frequency tracker of every HN hiring thread since 2011, now shows the channel roughly 61% below its November 2021 peak and about 30% below its 2022 level. Meanwhile Stanford HAI's 2026 AI Index clocked agentic AI job postings up 10,854% year over year. If you are still treating the monthly thread as your primary sourcing channel for AI-native engineers, you are optimizing for a shrinking audience that no longer overlaps with the pool you need.

The headline gap: 61% down vs. 10,854% up

Hacker News "Who is hiring" has lost about 61% of its 2021 volume at the exact moment the roles founders most want to fill grew four-figure percentages. That is not a rounding-error mismatch. It is the sourcing channel and the hiring demand moving in opposite directions for four straight years.

The two numbers come from different measurement systems, so treat them as directional rather than a clean ratio:

• hntrends.com measures keyword frequency across every "Ask HN: Who is Hiring?" thread. The November 2021 peak reflected the ZIRP-era hiring binge; the July 2026 thread is a fraction of that corpus.
• Stanford HAI 2026 AI Index measures job postings tagged with agentic AI skills across Lightcast's global corpus. The +10,854% figure covers a single year.

Even acknowledging that one is a subreddit-sized text feed and the other is the entire tracked labor market, the direction is unambiguous. The board that used to be the highest-signal tech job feed on the internet, per every scraper builder who ever wrote a monthly pipeline against it, is shedding exactly the audience recruiters need most.

10,854%

The full picture, in one table

Here is the dataset behind the argument, with sources and derivations labeled so you can decide how much weight each number carries.

Two things jump out. First, Lightcast's more conservative framing (skill-cluster share moved from 0.06% to 0.23%, about a 283% jump, representing roughly 90,000 US postings) is probably the number to quote in an executive meeting. Second, the 22-to-25 cohort collapse (-20% from 2024) tells you who is still refreshing HN threads on the first of the month, and it is not the senior AI engineers you are trying to land.

Why the thread cannot index the new work

HN "Who is hiring" is dying because its format cannot support the roles that are actually growing. One comment per company, dense unstructured text, no tags, no filters. That was fine for "Rails backend, remote, competitive salary" in 2015. It is useless for filtering on LangGraph experience or Claude Code fluency.

Look at what Lightcast flagged as the fastest-growing skills in the 2026 index:

• Agentic AI (new cluster added this year)
• AI Agents
• LangGraph

And what declined in the same window:

• ChatGPT
• Conversational AI
• Chatbot

The skills on the way up are toolchain-specific, evolve monthly, and require recruiters to filter with precision. The skills on the way down are the generic "we use GPT for support" work that fit HN's freeform paragraph format perfectly. The audience did not abandon the thread out of boredom. They left because the interface cannot index the new work, so senior candidates do not scan it and senior recruiters no longer bother posting there.

The definitional caveat, because credibility matters

The 10,854% number is inflated by taxonomy expansion. Lightcast added Agentic AI as a new skill cluster in the 2026 index, bringing total AI clusters tracked to 10 and total AI skills monitored past 300, including 24 newly added skills. Some of that four-digit growth is Lightcast catching up to reality rather than the market growing that fast in twelve months. The Lightcast share number (0.06% to 0.23%) is the honest version.

Where the AI-native pool actually lives now

Senior AI engineers in 2026 split attention across a specific set of vendor Discords, applied-AI communities, and long-form platforms, not general job boards. The daily.dev community map for 2026 lays it out plainly: Reddit, YouTube, Discord, Hacker News, Latent Space, X, and daily.dev, each serving a different job.

The six that actually matter for sourcing:

1. Anthropic's Discord - best signal for Claude Code and agentic product builders; staff drop API announcements in-channel.
2. OpenAI's Discord - the largest single AI builder community in the world; engineering channels have real signal.
3. Latent Space (swyx) - the strongest applied-AI-engineering community, with dedicated channels for agents, evaluation, and RAG.
4. Hugging Face Discord - the real-time heart of open-source AI, plus their Agents Course community.
5. Cursor community server - high-signal for agent-mode workflows and rules setups.
6. X - where the same people post benchmark threads and eval takes under real names.

The structural problem: recruiters can lurk in all six, but posting job listings in any of them is either against the rules or a fast way to get muted. The channel where your candidates gather is not a channel where you can broadcast. That inversion is the entire modern sourcing problem in one sentence.

The channel where your candidates gather is not a channel where you can broadcast. </pull> This is the exact gap [Refolk](/) closes. Instead of posting into a community that will not let you post, you describe the person in plain English ("engineers who ship in Cursor's Discord, have contributed to LangGraph or an eval framework, and worked at a Series B AI company in the last 18 months") and get a ranked shortlist pulled across GitHub, LinkedIn, and the open web. The lurking is automated; you spend your time on outreach, not scraping.

refolk prompt: Find senior engineers active in Anthropic's Discord or Latent Space who have shipped agentic features in the last 12 months and worked at a Series B+ AI startup. note: Returns a ranked list with GitHub activity, current employer, and public signals across X, Discord participation, and open-source contributions.

## Forward-deployed engineer is the leading indicator

The single most important role in AI hiring right now is forward-deployed engineer, and it is the one HN "Who is hiring" indexed least. FDE postings grew over 800% in 2025 alone, and a live July 2026 HN listing from Confido offered $200,000 to $270,000 base for the role. That is a category that essentially did not exist three years ago now commanding senior-backend comp.

Why FDE matters for sourcing strategy:

- The role sits inside customer environments, which means the candidate profile blends applied engineering with the customer-facing instincts of a solutions architect. Standard "backend engineer" boolean strings miss them entirely.
- FDE listings show up on company careers pages and in AI-focused Slack/Discord referral channels far more than on general job boards. HN captures a fraction.
- Comp is high enough ($200k-$270k+ base at Confido, higher at larger AI labs) that these candidates are not casually browsing hiring threads. They are being pulled directly.

If a founder in July 2026 is only watching HN, they are not just missing volume. They are missing the single fastest-growing engineering job category in the market. This is where [Refolk](/) earns its keep on FDE searches specifically: the description-to-shortlist model handles hybrid role definitions ("engineer who has done customer-facing deployment work, comfortable in enterprise environments, has shipped an agent to production") that boolean sourcing simply cannot express.

800%

What actually works for technical recruiting channels in 2026

Effective sourcing in 2026 combines three motions: passive listening in the communities where AI engineers already gather, active enrichment across GitHub and the open web, and precise outreach that references the candidate's actual work. HN "Who is hiring" is not on the list.

A concrete playbook:

1. Listen, do not post. Lurk in Latent Space, Anthropic's and Cursor's Discords, and the r/LocalLLaMA and r/MachineLearning subreddits. Track handles that answer technical questions well, not the ones that ask them.
2. Enrich against GitHub and the open web. A Discord handle plus a GitHub username plus a LinkedIn profile is a candidate. Any one of those alone is a name.
3. Reach out with role-specific references. Reference the eval library they contributed to, not "your impressive background." AI engineers scan for this instantly.
4. Skip channels that select for the wrong seniority. HN threads over-index on the 22-to-25 cohort whose employment is down 20% from 2024 peak. Great for junior hires, wrong for staff-level agentic work.
5. Track vendor-community activity as a first-class signal. Cursor rules contributions, LangGraph example PRs, and Anthropic cookbook forks are as revealing as commit history on a main employer's repo.

The founders and recruiters who will win the next 18 months of AI hiring will not be the ones with the best HN post. They will be the ones with the tightest description-to-shortlist loop across GitHub, LinkedIn, and the vendor communities, which is exactly the surface area Refolk indexes.

FAQ

Is Hacker News "Who is hiring" completely dead as a sourcing channel?

No, but its use case has narrowed. It still surfaces early-stage founders who prefer text-first hiring and some strong forward-deployed engineer listings, as the July 2026 Confido post shows. It is a fine top-of-funnel signal for what companies are hiring publicly, and a poor primary channel for reaching senior AI engineers. Use it as a scan for competitor hiring signals, not as your outreach list.

How reliable is the 10,854% agentic AI growth figure?

Directionally very reliable, precisely less so. Lightcast added Agentic AI as a new skill cluster in the 2026 Stanford AI Index, so part of that growth reflects taxonomy catching up to a category that existed but was previously uncategorized. The cleaner Lightcast framing (skill-cluster share moved from 0.06% to 0.23%, about a 283% jump, representing roughly 90,000 US postings) is what to quote in a serious conversation. Both point the same direction.

Where should I actually reach senior AI engineers in 2026?

Not through cold InMail alone. The highest-signal surfaces are Latent Space, Anthropic's Discord, OpenAI's Discord, Hugging Face's Discord, and the Cursor community server, paired with GitHub activity and X presence. You cannot post jobs in most of these, so the model is: identify candidates from their public participation, enrich to a full profile across GitHub and LinkedIn, then reach out with specific references to their work. That identify-enrich-reach loop is exactly what Refolk automates.

Does the 22-to-25 developer employment drop mean I should stop hiring junior engineers?

The opposite, if you have a training plan. The 20% employment drop in that cohort means the junior labor market is soft, so senior recruiters willing to invest in structured onboarding can hire above their weight class right now. The HN thread is a reasonable channel for that specific pool. Just do not confuse it with the senior agentic AI pool, which has effectively left the building.