The October HN "Who Is Hiring" Thread Is a 400-Row Prospect List

The October 2026 "Ask HN: Who is hiring?" thread went live on Oct 1 as item 49922569, and by day two it already names engineering leaders at Runway, Oklo, FusionAuth, Fredrin, and dozens of YC-funded startups. If you sell to engineering teams or run founder-led sales, that single URL is the cheapest B2B signal of the month. Every post is a company publicly confirming budget, naming a decision maker, and timestamping intent to spend.

Why the HN hiring thread beats a scraped job board

Because every top-level post is written by the hiring manager, not an ATS, and the manager's HN handle usually resolves to a real name. A scraped job board gives you a req ID and a careers URL. The Hacker News "Who is hiring?" thread gives you a human who read the words before posting them, a stack, a comp band, and often a direct email.

The structural difference matters for prospecting engineering hiring managers:

• Named author. Every post has a HN handle attached, and most handles have a bio, a personal site, or a linked GitHub.
• Confirmed budget. Posting on HN takes effort. Nobody does it for a frozen req.
• Freshness. The whoishiring bot posts on the first business day of every month. The data cannot be more than 30 days old.
• Public, not scraped. You are not fighting LinkedIn's rate limiter or a Greenhouse paywall. You are reading a public thread.
• Buyer self-selection. The population that posts on HN skews toward infra, dev tools, and AI-native startups, which is the same population most B2B vendors want to reach.

The sibling counter site hacker-hirings.com has tracked 187 monthly threads since March 2011. That is 15 years of regenerating, timestamped intent data sitting on one domain, free.

What the October 2026 thread actually contains

A representative snapshot of named handles, companies, and roles already visible on day two. Every row is a cold-outbound target with a face attached.

The YC sidebar on hacker-hirings is currently flagging Truemetrics (YC S23), Bild AI (YC W25), Stable (YC W20), QuestDB (YC S20), Supabase (YC S20), Zettascale (YC S24), Kyber (YC W23), Jiga (YC W21), and Lingo.dev (YC F24) as cross-linked hiring posts. If your ICP is "YC-funded engineering team with budget this quarter," that sidebar alone is worth the hour it takes to parse the thread.

The posting template is machine-readable

Most posts follow a Company | Role | Location | Type | Salary | Visa header. That is not a convention HN enforces. It is a convention the audience enforces, because posts that break it get downvoted. Which is why parse quality is now very high: in August and September 2026, 84 to 88% of posts scored 0.8 or higher on parseConfidence on the timmKal01/hn-whos-hiring-parser project.

The math on thread volume

Between 359 posts (June 2023 floor) and 400+ posts (May 2024 ceiling) per month, with AI mentioned in roughly a quarter of them. If your product sells to AI-native startups, one URL per month gives you about 100 pre-qualified accounts.

400+

Why May 2024 matters as the ceiling

May 2024 was the first 400+ posting month since May 2023, a 35% jump over April, with AI now the top technology term across the dataset. The same thread is a de facto registry of companies hiring to build AI products, which is a narrower and more actionable list than "companies hiring engineers."

The buyer pool is smaller than you think

There are only 4,477 US-based Director and VP-level engineering leaders (Head of Engineering, VP Engineering, Engineering Manager) in Refolk's index of professional profiles. If you are selling dev tools or infra, that is your entire US TAM at the decision-maker level. Every resolved HN handle is about 0.02% of it.

That math changes how you should think about the thread. One monthly parse touches 5 to 10% of your addressable buyers over a quarter. This is not an opportunistic skim between other sourcing tasks. It is a dedicated workflow with a calendar invite on the 1st of the month.

The piece most sourcing teams miss: the HN handle is the easy half. Turning ridiculous_fish into a named VP of Engineering at Oklo with a GitHub, a LinkedIn, and a prior employer is the half that eats an afternoon per 50 handles if you do it manually. That is the exact gap Refolk closes. You paste the thread, describe who you want in plain English ("VPEs and heads of engineering at the companies posting in this thread, US-based, Series A or B"), and get a ranked, enriched list back.

Forward Deployed Engineer is now the dominant role

Every third post in the October 2026 thread asks for a Founding Engineer or Forward Deployed Engineer. In Refolk's index, 7,565 US professionals currently hold one of those two titles, with San Francisco (4) and New York (4) tied at the top among visible job posts. Dividing by ~400 monthly posts, the thread names roughly 5% of the companies willing to publicly declare they are hiring for these roles, which is a near-complete sample of AI-native and infra-heavy startups at seed through Series B.

If you are a recruiter working this market, that ratio is the whole argument for treating the HN thread as a dedicated channel. The population is small, the companies are hard to find any other way, and the posters have raised their hand.

Downrank the Greenhouse links

A plain email in a HN hiring post beats a Greenhouse link, because the audience itself downranks the form. For a prospector, that signal flips: posts that include a direct personal email are run by a hiring manager who personally handles replies. Those are the warmest targets in the thread. Posts that only link to Greenhouse are usually run by an in-house recruiter, which means the hiring manager is one layer removed and your reply time doubles.

Rank the thread accordingly. Direct email first, personal domain second, Ashby third, Greenhouse fourth, Workday last.

How to actually parse the thread in under an hour

Pick one of three paths. All of them use the public Hacker News Search API at hn.algolia.com/api, which does not rate-limit normal use.

1. The off-the-shelf scraper. Apify's parseforge/hn-whoishiring-scraper auto-detects company, role, salary, remote, visa, and 60+ tech stacks per posting. Point it at the thread ID, get a CSV back.
2. The open-source Python parser. AlexeyYurko/whoishiring on GitHub uses BeautifulSoup against the thread HTML and spits out structured rows. Good if you want to control the output schema.
3. The confidence-weighted parser. timmKal01/hn-whos-hiring-parser scores each row and lets you filter at 0.8+ confidence, which is the 84-88% of posts clean enough to use without manual review.

Once you have the CSV, the workflow is:

1. Resolve HN handles to real names. The handle's HN profile often links to a personal site. If it does not, cross-reference the company and role against LinkedIn.
2. Enrich with GitHub. The forward deployed and founding engineer roles especially skew to candidates with public code, and the hiring manager usually has a repo list that tells you what they actually care about.
3. Segment by stage. Series A/B companies posting a Principal role are a different buyer than a seed company posting a Founding Engineer. Split them into two campaigns.
4. Draft one message per segment. Reference the post. "Saw your October HN post for a Principal SWE at FusionAuth" is the whole opener.

Every HN hiring post is a company raising its hand. The expensive part is turning 400 raised hands into 400 real names.

Treat the 1st of the month as a lead-gen window

Put it on the calendar. The whoishiring bot posts the thread on the first business day of the month. The first 48 hours get the heaviest posting volume and the cleanest templates. By day five, late posters are using inconsistent formats and parse confidence drops.

The operational cadence that works:

• Day 1, afternoon UTC. Confirm the thread is live. Grab the item ID.
• Day 2 to 3. Run the parser. Filter to 0.8+ confidence. Dedupe against last month.
• Day 3 to 5. Resolve handles, enrich, segment. Push to CRM with a source=hn_whoishiring_oct2026 tag so you can measure reply rates against your other channels.
• Day 5 to 10. Send. HN posters are hiring now, not next quarter. Reply within a week or the budget conversation is already happening with someone else.
• Day 30. Repeat.

One commenter has reported hiring about 12 developers over 5 years from these threads. On the demand side, a candidate reported being contacted by 14 companies cumulatively across two monthly posts, of which 2 were interesting. Both numbers tell you the same thing. The thread works. It just works slowly if you treat it as a one-off.

FAQ

How many companies post in a typical HN "Who is hiring?" thread?

Between 359 and 400+ monthly, based on the June 2023 floor and the May 2024 ceiling. The October 2026 thread is tracking toward the upper end of that range based on its day-two count of 41 posts. If you need a planning number, assume ~400 companies per thread and ~100 of them are AI-focused.

Can I legally scrape the HN hiring thread?

The thread is a public page and the Hacker News Search API run by Algolia is explicitly offered for third-party use. Parsers like AlexeyYurko/whoishiring and timmKal01/hn-whos-hiring-parser have been running on it for years. The ethical line is reply volume, not scraping. Blasting 400 identical cold emails will burn your domain reputation and the thread's goodwill. Segment and personalize.

Which startups actually post, versus using LinkedIn?

HN posters skew heavily toward infra, dev tools, AI-native products, and YC-funded companies at seed through Series B. The October 2026 thread includes Oklo, Runway, FusionAuth, and Fredrin, plus YC sidebar names like Truemetrics, Bild AI, Stable, QuestDB, Supabase, Zettascale, Kyber, Jiga, and Lingo.dev. If that profile matches your ICP, the HN thread is a better source than LinkedIn. If you sell to Fortune 500, it is not.

How do I resolve a HN handle to a real person?

Start with the handle's HN profile page, which often has a personal site, email, or GitHub linked. Cross-reference the company and role against LinkedIn to narrow it to one candidate. For handles that reveal nothing, the fastest path is to run the resolved company plus role against an index that already stitches GitHub and LinkedIn together. Doing it manually for 50 handles is a half-day. Doing it for 400 is a week you do not have.