HN's June Thread Closed at 359. The Demand Didn't Vanish, It Moved.
June 2026's "Ask HN: Who is Hiring?" hit a January 2015 low of 359 posts. Here's where engineering demand actually went, and how to source it.
If you opened the June 2026 "Ask HN: Who is Hiring?" thread expecting the usual scroll-til-your-thumb-cramps wall of YC startups and infra companies, you got something closer to a ghost town. The thread closed with 359 postings. That number matches January 2015, back when the thread had only crossed 500 once in its life. The instinct is to read this as a hiring collapse. It isn't. It's a channel collapse, and the difference matters if you're trying to hire engineers in the back half of this year.
The number, in context
Ryan Williams' hntrends.com tracker, which has cataloged every "Who is Hiring?" thread for over a decade, flagged 359 as a new modern-era low. January 2026 had already set off the alarm at 285 postings, the lowest in nine years. June's bounce wasn't really a bounce. It was the second-worst print of the modern era, in what should be a seasonal high.
Stack that against what the other side of the market is doing on the same forum. June 2026 also produced the largest gap on record between "Who is hiring?" and "Who wants to be hired?", almost 2x. Candidates are still posting. Companies are not. The HireIndex read on "Who Wants to Be Hired?" shows the average poster's experience climbing from roughly 7.5 years in 2022 to 9+ years by December 2025 and January 2026. The public side of HN is now a board of senior ICs raising their hands into a thread that fewer and fewer companies are reading.
This is not a demand story
Before the layoff-doom narrative takes over, look at the rest of the tape.
Robert Half's mid-year 2026 survey has 78% of technology leaders planning to grow permanent headcount in H2 2026, up from 61% earlier in the year. Tech is the most aggressive hiring sector they survey. The Pragmatic Engineer's 2026 state-of-the-market piece, working off TrueUp data, has top tech companies up roughly 20% year over year in open engineering roles. Apple and Google are hiring more than last year, with Google alone advertising 62% more engineering roles than a year ago. Meta, Oracle, and TikTok are down. The aggregate is up.
So the question isn't "where did the jobs go." It's "where did the postings go."
Indeed has the macro shape
Indeed's Hiring Lab data, as of mid-2025, has US tech postings down 36% from February 2020 levels. Software engineer postings specifically, the single most common tech title, are down 49%. But the composition has shifted hard underneath that average. Android, Java, .NET, iOS, and traditional web roles are down 60% or more from 2020. Machine learning engineer postings are up 59%.
You can predict who keeps using HN from that mix alone. The roles that grew are exactly the roles that companies don't broadcast. ML hiring runs on papers, GitHub repos, conference rosters, and warm intros. It does not run on a public comment thread. The roles that shrunk are the ones HN was historically great at filling, mid-level full-stack at a Series A or B, and they're getting eaten by AI tooling, offshore arbitrage, and consolidation at the top of the market.
Why HN specifically caps out here
The thread has structural ceilings that get ignored in every "is HN dead" take. The pinned rules ban recruiting firms and job boards. They cap companies at one post. They require the poster to be actively hiring. None of that bends with demand. If a company's best three candidates aren't reading the June thread, the company stops posting in July, and the next company sees a thinner thread and decides the same thing. The flywheel runs in reverse.
Look at who actually posted in June 2026. Hatchet. Seeq. Upwave. Adacore. Reef Technologies. Flow Traders. Felt Clinic. Giga. A pile of YC companies, a few deep-niche infra shops, and a couple of trading firms. The channel still works for them because their candidate persona, technically curious, reads HN already, willing to work at a small unknown company, overlaps almost perfectly with the audience. For everyone else, the channel has aged out of its match.
Supply is public. Demand isn't. That is the entire microstructure of the 2026 engineering market in one sentence. </pre>
Actually, scratch the formatting, the point stands on its own:
Supply is public. Demand isn't. That is the entire microstructure of the 2026 engineering market in one sentence.
Where the demand actually went
Demand routed to outbound. SignalHire's 2026 report puts 70% of the global workforce in the passive-candidate bucket. If you're posting jobs and waiting, you're competing for the 27 to 30% who are actively looking, against every other employer doing the same thing. The math of passive candidate sourcing is now table stakes, not an edge.
The teams that are hitting their plans in 2026 are doing three things differently:
- They source by name from GitHub, LinkedIn, publications, and conference talks before a public posting goes up, if one ever does.
- They run tight, role-specific outbound instead of broad job-board spray.
- They treat "Who Wants to Be Hired?" and other public surfaces as input lists for outbound, not as a substitute for it.
The friction in step one is real. Boolean strings on LinkedIn miss anyone whose title doesn't match the buzzword of the quarter, and GitHub search is hostile to anything more nuanced than language plus location. That gap is exactly why we built Refolk: you describe the person you want in plain English ("staff infra engineer with Kubernetes operator experience, currently at a Series B or later, based in NYC or remote US") and get a ranked shortlist drawn from GitHub, LinkedIn, and the open web in one pass. No string gymnastics, no tab juggling between five tools.
The junior squeeze inside the same data
There's a quieter, uglier signal in the HireIndex numbers. As the average "Who Wants to Be Hired?" poster crept from 7.5 to 9+ years of experience, the share of 0 to 2 year candidates dropped. Companies that do still post on HN are increasingly looking for seniors. Forrester is forecasting a 20% drop in CS enrollment by the end of the decade. The juniors who relied on the public board, both to read it and to be read by it, are getting squeezed from both directions at once.
For founders, that's a tactical opportunity. The Copilot-adoption data from earlier this year already showed firms that adopted AI tooling hiring 5% more juniors, not fewer. The supply of strong juniors who can't get a callback through traditional channels is real, and they are findable. They just aren't findable on the channels that used to find them.
What to do in Q3
If you've been benchmarking your sourcing pipeline off public posting volume, the 359 number should reset your priors. Here's the practical reframe.
Stop using HN as a market temperature gauge
It is now a thermometer for "do small YC-style companies want to hire mid-level generalists this month." That's a real signal for a narrow slice of the market. It is not the engineering hiring market. The engineering hiring market is reflected better in TrueUp's open-role counts, Robert Half's intent surveys, and the open-roles pages of the 30 companies you actually compete with for talent.
Treat the public thread as a sourcing input
The 9+ year average experience on "Who Wants to Be Hired?" means that thread is now a small but real list of senior engineers who have publicly raised their hands. Scrape it, score it, and route it into outbound. Same for the "freelancer" thread. Public expressions of intent are rarer in 2026 than they were in 2022, which makes them more valuable, not less.
Build the outbound muscle, or borrow it
The teams hitting plan have a defined motion: a clear ICP per role, a sourcing tool that can express the ICP in plain English, a CRM to track touches, and a writer who can produce a non-generic first message. The cost-per-hire math (SHRM has it at $4,700 average, 44 day time-to-fill) gets worse the more you depend on inbound. Outbound flips both numbers down once the muscle exists.
This is the part where most teams get stuck on the sourcing tool. LinkedIn Recruiter is the default, but anyone who's tried to write a 12-clause Boolean for an AI infra role at 11pm on a Tuesday knows the ceiling. Gem, HireEZ, SeekOut, Juicebox, Fetcher, and Pin all sit on the same broad premise: search 800M+ profiles across the open web. Refolk's bet is that the search interface itself should be plain English, because the constraint on sourcing technical talent in 2026 isn't database size, it's expressing exactly the person you want without flattening them into keywords.
Don't confuse channel decline with market decline
The most expensive mistake a founder can make right now is reading "359" and deciding to slow-walk a hire because "the market is soft." It isn't soft at the top. Google is up 62%. Apple is up. Top companies in aggregate are up 20%. If you delay an offer because HN looks quiet, you are reading a chart of a channel you no longer use against a candidate who has three competing offers from companies that source on GitHub.
The HN thread will probably keep limping along. It still works for the slice of the market it was designed for. But sourcing technical talent in 2026 means treating it as one small node on a much bigger graph, where the highest-signal edges are passive, named, and contacted directly. The 359 isn't an obituary. It's a notification that the market moved, and the public channel is the last place to find out.
FAQ
Is the HN "Who is Hiring?" thread still worth posting in?
If you're a YC-adjacent company, a deep infra or trading shop, or anyone whose ideal candidate genuinely reads HN for fun, yes. The thread still works as a high-signal, low-volume channel for that audience. It is not a substitute for outbound sourcing, and it will not move the needle if your role profile is generic. Treat it as one cheap shot on goal, not a pipeline.
Why is "Who wants to be hired?" growing while "Who is hiring?" shrinks?
Because supply and demand respond to different incentives. Engineers post when they're between roles or testing the water, and that has gotten more common as the junior end of the market tightens and remote opportunities widen. Companies post when they expect a strong return on a single public listing, and that expectation has fallen as the best candidates have moved to passive sourcing channels. The 2x gap is the friction made visible.
Where should I source if not from public job boards?
Outbound across GitHub, LinkedIn, publications, conference rosters, and the open web. The teams hitting plan in 2026 build a clear ICP per role, source named candidates, and run a real outbound motion. Tools like Refolk, Gem, HireEZ, and SeekOut all aim at this problem from different angles. The common thread is moving from "post and pray" to "find and ask."
Does the HN data say anything about junior hiring?
Yes, and it's worth flagging. The average experience level of "Who Wants to Be Hired?" posters climbed from about 7.5 years in 2022 to over 9 years in late 2025 and early 2026. Junior candidates are increasingly squeezed out of the public board on both sides. The opportunity for founders willing to hire and train juniors is real, but it requires deliberate sourcing, because the channels that used to surface them are getting older every quarter.