Argues that the 213/132 split between the hiring and candidates threads represents the cleanest labor market reversal since the 2021 ZIRP peak. Unlike BLS data (lagging, sector-blended), LinkedIn (gamed by ghost jobs), or Levels.fyi (FAANG-biased), the HN threads offer a noise-controlled signal with an unambiguously senior engineering audience and consistent boilerplate format since 2011.
Interprets the 213-point hiring thread as evidence that hiring managers believe HN will yield better candidates than their internal referral funnel or LinkedIn InMail. The implication is that the best engineers are currently employed, not job-hunting, so companies must actively fish for them in threads rather than wait for applications.
The whoishiring account has run the same boilerplate template — no recruiting firms, no job boards, one post per company, must be actively hiring — on the first business day of every month since 2011. The strict rules and unchanged prompt are what make the score comparable across years as a noise-controlled signal.
The candidates thread drew 379 comments versus 298 on the hiring thread — more individual engineers actively posting their availability than companies posting openings. This suggests that while upvote sentiment favors employers in June 2026, the supply side of senior engineering talent is still substantial and actively visible.
The monthly Hacker News 'Who is hiring' and 'Who wants to be hired' threads went live on June 2, 2026. Within hours, the hiring thread sat at 213 points. The candidates thread sat at 132. Both are dang's same boilerplate templates that have run, unchanged, on the first business day of every month since 2011 — which is exactly what makes the gap useful.
These threads are the longest continuous noise-controlled signal in tech hiring. Same prompt, same rules ('no recruiting firms, no job boards, one post per company'), same audience. The score isn't a popularity contest — it's how many HN readers thought the post mattered enough to upvote on a day when the rest of the front page was the usual mix of Rust drama and Postgres trivia.
For roughly 18 months — from late 2023 through early 2025 — the candidates thread consistently outscored the hiring thread, sometimes 2:1. That inversion was the most honest labor market read in tech: more engineers wanted you to see they were available than companies wanted you to see they were hiring. June 2026 is the cleanest reversal we've seen since the 2021 ZIRP peak.
Nobody trusts BLS numbers anymore — they're lagging, sector-blended, and the 'tech' bucket includes everyone from Comcast field techs to OpenAI researchers. LinkedIn data is gamed by 'ghost jobs' and recruiter spam. Levels.fyi is biased toward FAANG. The HN threads are one of the few datasets where the *audience* is unambiguously senior software engineers and the *signal* is unambiguous intent.
The 213/132 split isn't just 'hiring is back.' It's 'hiring is back enough that hiring managers think posting on HN will get them better candidates than their internal pipeline.' That's a specific claim. It means the in-house referral funnel is dry. It means LinkedIn InMail is returning garbage. It means the candidates worth hiring are not currently between jobs — they're employed, and you have to go fish them out of a thread on a Y Combinator forum at 9 AM Pacific.
Cross-reference with the other signals: AI infra hiring is visibly up (every Anthropic, OpenAI, and Mistral post in the thread has 30+ replies within an hour). Devtools and dev-platform companies — Vercel, Supabase, Turso, Modal — are back to monthly posts after going dark in 2024. Notably absent: the FAANG-tier compensation posts that defined 2019-2021 threads. Meta, Google, Amazon are barely visible. That tracks with the post-Section-174 reality: big-tech engineering headcount is still flat-to-down even as the broader market opens up.
The candidates thread tells the inverse story. 132 points is not 'nobody needs a job' — it's 'the people who need a job aren't the people HN wants to see hired.' Scroll the top posts and you'll find a pattern: senior backend engineers with 10+ years, ML researchers exiting failed Series A's, ex-FAANG SREs who took the 2024 severance package and are now ready to come back. The junior pipeline is barely present, which matches what bootcamp grads have been saying for two years: entry-level tech hiring is structurally broken and AI-assisted coding is making it worse.
There's also a geographic tell. Three of the top ten hiring posts as of this writing say ONSITE, two say 'REMOTE (US-only)', and only one says fully global remote. That's a meaningful shift from the 2022 thread, where global-remote was the default and ONSITE was the exception that required an apology. The remote-first wave is still cresting, but the 'hire anyone, anywhere' phase is clearly over — partly because of tax/compliance complexity, partly because companies got burned by timezone-arbitrage hires that didn't work out.
If you're hiring: post early in the month, post specific, and reply to every applicant within 48 hours. The thread rewards companies that treat it as a real channel, not a JD dump. The hiring posts that get the most replies are the ones that name the actual engineering challenges in the first paragraph — 'we're rewriting our ingestion pipeline from Kafka to Redpanda and need someone who's done it' beats 'we're a fast-paced fintech disrupting the future of money' every single time.
If you're looking: don't wait for your network. Read the hiring thread top-to-bottom on day one and email 5-10 companies directly. The candidates thread is fine as a passive signal, but the response rate is brutal — most postings get zero replies because hiring managers are reading the *other* thread. Your application has a 10x better hit rate as an outbound email to the hiring post than as a passive listing in the wants-to-be-hired thread.
If you're a founder thinking about your engineering team's market value: assume your senior people are getting outbound emails this week. The competitive offers will start landing within 14 days. The retention move is not a counter-offer when they hand in notice — it's a proactive comp adjustment now, before the offer arrives. The companies winning in this market are the ones that figured out in May that June was going to flip.
One month is not a trend. The July thread will tell us whether June was a real reversal or a dead-cat bounce driven by Q2 budget releases. But the underlying mechanics — AI infra companies burning through Series B's, devtools startups re-staffing after 2024 layoffs, big tech still frozen — point to a labor market that's bifurcating, not uniformly recovering. The 213/132 number won't be the headline anyone writes. It should be.
Please state the location and include REMOTE for remote work, REMOTE (US) or similar if the country is restricted, and ONSITE when remote work is <i>not</i> an option.<p>Please only post if you person
→ read on Hacker NewsShare your information if you are looking for work. Please use this format:<p><pre><code> Location: Remote: Willing to relocate: Technologies: Résumé/CV: Email: </code></pre> Please on
→ read on Hacker NewsTop 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.