June's HN "Who Wants to Be Hired" Is the Cleanest Senior Pool of 2026
The June 2026 Hacker News "Who wants to be hired?" thread is a live opt-in list of senior engineers, and recruiters are still buying LinkedIn seats.
The June 2026 "Ask HN: Who wants to be hired?" thread went up June 1 and hit the front page on June 6. It is sitting at HN item 48357724 right now, full of senior engineers who explicitly asked for inbound. Most recruiters will not touch it, because it bans them by rule, and because they are already locked into a $10,800 LinkedIn Recruiter seat that the org needs to justify.
That is the trade. The thread is the cleanest opt-in senior pool published this quarter, and the parallel "Who is hiring?" thread (item 48357725) tells you exactly what employers want to see in those candidates: not leetcode, not a whiteboard, but AI-built work you can click on.
The rules of the thread are the moat
If you have not read the post recently, the format is strict: Location, Remote, Willing to relocate, Technologies, Résumé/CV, Email. The moderator instruction is blunt. Agencies, recruiters, and job boards are explicitly off topic. Readers are asked to only email these addresses to discuss work opportunities.
Most sourcing leads read that and close the tab. They should not. The ban is a quality filter, not a gate. It keeps the candidate list from getting drowned in agency reply-alls, which is why the people who post there are still senior, still self-identifying with verifiable emails, and still answering DMs in 2026. Founders who reach out themselves, or in-house recruiters using a real company domain, get a clean inbox conversation. Staffing agencies cannot legitimately work the thread, which is the whole reason it stays useful.
The HNHIRING index, which has been tracking these threads since January 2018, has now cataloged 59,496 job ads. A separate scrape of "Who is hiring?" pulled 6,539 jobs across 17 months. This is not a one-off curiosity. It is a recurring, structured corpus that almost no ATS plugs into.
Why the candidate side is now higher signal than the employer side
There is a quiet inversion happening in the HN hiring pair. For most of the last decade, "Who is hiring?" was the high-value half and "Who wants to be hired?" was treated as the leftover. That has flipped.
In the June 2026 employer thread, the user peterldowns announced he was done posting after what he called "an incredible amount of spam," including fake resumes and names lifted from real developers. His exact framing: inbound hiring for remote teams is "basically cooked at this point, signal is completely hidden in the noise." Other employers echoed it in the comments.
The candidate side does not have that problem. The people posting in "Who wants to be hired?" are publicly accountable through their Show HN history, their GitHub, and their HN comment trail. You can verify a candidate in about ninety seconds before you ever send an email. You cannot verify the resume of someone who emailed your jobs@ inbox at 3 a.m.
The thread bans recruiters, which is exactly why the engineers in it still answer recruiter-style emails.
The "Who is hiring?" thread tells you what to ask for
The other half of the pair is doing free market research for you. Read the June 2026 employer posts back to back and the new hiring bar is unmistakable.
AES (Associated Environmental Systems), posting their June 2026 role out of Chelmsford and Waltham, wrote it plain: "No leetcode. No whiteboard. Show us your best AI-built work, a PR, a deployed app, or a repo." Their required artifact is a track record building with AI tools, ideally a repo with a CLAUDE.md, plus at least one shipped end-to-end project that runs somewhere a stranger can use.
vvd, hiring a Design Engineer, framed AI fluency as the floor: "We're AI-native, but not trying to replace human creativity. We use tools like Cursor and Claude Code as leverage to move faster while keeping a high quality bar." Another employer in the same thread spelled out the guardrail: "We lean hard on AI tooling and expect you to, but the bar is human-reviewed, well-tested code; 'the model said it worked' isn't a defence."
Read those three together and the screen is now: show me a public artifact you built with AI assistance, then show me the tests and the review trail that prove a human owned the output. That is the no leetcode hiring standard for 2026, and HN candidates are pre-qualified for it in a way LinkedIn candidates are not. Show HN, public repos, and visible commit history are the native unit of the platform.
What the candidates are actually showing
The same June 2026 thread had candidates listing projects like MindPad AI, Flowstate, AtlasBrief, GeoRisk, and EchoRoom. The posts described them as not basic portfolio clones but with real auth, payments, persistence, AI-assisted workflows, dashboards, billing logic, team flows, and deployed production-style architecture. That is exactly what AES and vvd just said they want to see. The two sides of the thread map to each other almost line for line.
The dominant technical archetype is also clearer than it was two years ago. Candidates increasingly present as hybrid builders: Python, Go, TypeScript, Kubernetes, AWS, vector systems, OpenAI, Claude, Gemini, Mistral, and RAG-flavored experience packaged together. More generalist, more tool-fluid, more AI-literate. LinkedIn's filter UI was built for a world of single-stack specialists. Free-form HN posts surface this profile naturally, which is part of why AI engineer sourcing through LinkedIn keeps returning the wrong shortlist.
The LinkedIn Recruiter math nobody wants to redo
Here is the line item recruiters are quietly carrying into 2026.
That is not a one-time hike. LinkedIn Recruiter Corporate sits at roughly $8,999 per year for a single seat ($750 per month), a nearly 15% increase from previous years, and most mid-size contracts are landing between $10,800 and $12,000. For a ten-recruiter agency, the line item clears $129,000 per year. The structural read is that this is now a yearly renegotiation, not a one-time shock.
Agencies treating the price increase as a budget problem are renegotiating every twelve months. Agencies treating it as a trigger for an operational change are freeing 30 to 70% of the LinkedIn spend by moving the top of funnel somewhere else. Hacker News threads, GitHub, and the open web are the obvious somewhere else, and the 7.3 hours a week your team is already spending on sourcing is enough to cover all three if the tooling is right.
This is the friction we built Refolk for. You describe the candidate you want in plain English ("senior backend engineer, ships with Claude Code, posted in the last six months of HN Who Wants to Be Hired") and Refolk returns a ranked shortlist drawn across GitHub, LinkedIn, and the open web, including the HN comment history you would otherwise be skimming by hand. The thread is small enough to read. The cross-reference with their repos and LinkedIn is what eats the afternoon.
How to actually work the thread this week
A workable playbook, not a checklist for its own sake.
1. Read the thread end to end once
Yes, by hand. It takes under an hour. You are looking for shape, not names: which stacks are showing up, who is willing to relocate, what the median seniority looks like this month. This is the part that no tool should do for you, because it calibrates everything downstream.
2. Cross-reference, do not just email
For each candidate you flag, pull their GitHub and their LinkedIn before you write. The June 2026 employer bar is "show me your AI-built work," which means your outreach should already reference the repo. If you mention a specific PR or a specific deployed project in the first line, reply rates do not need much else. Refolk's index already covers roughly 4,900 senior AI and ML engineers in the US with titles like Senior Machine Learning Engineer, Senior AI Engineer, and Staff AI Engineer, concentrated in NYC and the Bay Area at Apple, Meta, Google, LinkedIn, and Workday. The HN thread is a hand-raised slice of that same pool, and stitching the two views is the whole point.
3. Send from a real human
The thread rules say email these addresses to discuss work opportunities. Send from a person at a company domain, not a sequencer. Reference the post they wrote. Skip the calendar link in message one. This is passive candidate sourcing where the candidate already raised their hand, so the bar is "do not waste their time," not "convert them."
4. Mirror the employer thread back at them
If you are hiring for the same role shape AES or vvd just posted, say so. "We are also in the no leetcode camp, we want to see the repo." Candidates in the thread read the employer thread. They notice when your pitch matches what the market is actually asking for.
5. Use the aggregators for archive work
HNHIRING (hnhiring.com), nchelluri.github.io/hnjobs, hnjobs.emilburzo.com, Hire Hacker News by AE Studio, and hacker-hirings.com all index the historical threads. For a live month, read HN directly. For backfilling a search ("who posted as a Staff AI Engineer in any thread since January?"), the aggregators are faster than scrolling.
The window
Hacker News threads do not stay live forever. The June 2026 thread will get buried under July's, and the candidates who posted will start taking offers in the next two to four weeks. The June "Who is hiring?" thread already told you the screen is now AI-built work, not leetcode, which means the candidates who posted with public repos are the highest-leverage outreach of the quarter.
LinkedIn will still be there in August. So will the $129,000 invoice. The HN candidate pool will not.
FAQ
Is it actually allowed to recruit from the HN "Who wants to be hired?" thread?
The thread rules ban agencies, recruiters, and job boards from posting, but the candidates themselves explicitly list an email address to receive work inquiries. In-house recruiters and founders emailing from a real company domain are within the spirit of the format. Agencies blasting templates from a sourcing tool are not, and the community will flag them. Treat it as a high-signal inbox the candidate opened on purpose.
Why is the candidate-side thread higher signal than the employer-side thread in 2026?
Employers have been complaining about a surge of resume fraud and bot spam, including fake names stolen from real developers. Candidates posting in "Who wants to be hired?" are publicly accountable through their Show HN history, GitHub, and HN comment trail, so verification takes about ninety seconds. The asymmetry that held for most of the last decade has flipped.
What does "show us your AI-built work" actually mean in a screen?
Based on the June 2026 employer posts, it means a public artifact, ideally a deployed project or a merged PR, that you built with AI tooling like Cursor or Claude Code, plus evidence that a human reviewed and tested the output. AES asks for a repo with a CLAUDE.md. vvd asks for Cursor and Claude Code fluency. The common floor is "the model said it worked is not a defence."
How does Refolk fit into sourcing from Hacker News specifically?
The thread is small enough to read, but cross-referencing each candidate against GitHub, LinkedIn, and prior employers is what burns the day. Refolk takes a plain-English description ("posted in June 2026 HN Who Wants to Be Hired, senior, ships with Claude Code, public deployed project") and returns a ranked shortlist across those sources, so the calibration stays human and the cross-referencing stops costing an afternoon.