The October 2026 "Who is hiring?" thread on Hacker News (item 49922569) is live, and the math around it has quietly inverted. Six months ago there were 1.2 candidates for every hiring company; the first week of October clocked 2.56. If you are drafting a "Who wants to be hired?" paragraph or firing off applications into the companies thread, you are writing into a market where more than half the applicants will not get a reply.
The HN hiring thread flipped 2.1x in six months
The ratio of candidate posts to company posts on Hacker News went from 1.2:1 in April 2026 to 2.56:1 in the first week of October 2026, a 2.1x shift in six months. Both sides moved: companies pulled back and candidates stepped forward.
An analysis published on dev.to counted the "Who is hiring?" and "Who wants to be hired?" threads monthly. The headline numbers:
| Metric | April 2026 | October 2026 (first week) | Change |
|---|---|---|---|
| Company posts | ~320 | 221 | −31% |
| Candidate posts | 384 | 566 | +47% |
| Candidates per company | 1.2 | 2.56 | 2.1x |
| Roles listed (monthly) | ~850 | 555 | −35% |
A separate 12-month tracker on solheimsolutions.no corroborates the company-side shrink: 378 to 412 company posts per month a year ago, 232 to 261 now. HNHIRING's index showed 266 jobs for October 2026 as of Oct 14, consistent with the dev.to count.
The non-obvious piece: this is not just "more laid-off engineers posting." Companies are the dominant mover in the ratio. There are roughly a third fewer posters this quarter, and the ones who remain are pickier. Your pitch is competing against 565 other candidates for the attention of 221 hiring managers who already read the thread with a filter on.
Up from 1.2 in April. The thread inverted in six months.
HN is doing work LinkedIn is not
Hacker News "Who wants to be hired?" is one of the few places senior engineers publicly out themselves as job-hunting, which changes who is reading your paragraph. The 566 October candidates are nearly 3x the entire visible pool of "open to work" US software engineers.
In Refolk's index of professional profiles, roughly 182,594 US-based people currently hold a Senior Software Engineer or Software Engineer title at senior level. Of those, only about 199 publicly signal "open to work" in their headline or keywords. That is 0.1% of the senior pool, or one public job-seeker per 917 employed engineers.
| Signal | Count (Refolk's index) |
|---|---|
| US senior software engineers | 182,594 |
| US SWEs publicly flagging "open to work" | 199 |
| Implied ratio | ~917:1 |
| HN "Who wants to be hired?" posts, Oct 2026 | 566 |
Two things follow from that gap:
- The reader of your HN paragraph is almost certainly a hiring manager, not a recruiter running keyword grep. They know the thread is a self-selection filter and they are scanning for signal, not matching to a req.
- You cannot copy a LinkedIn "Open to Work" blurb into HN and expect it to land. LinkedIn blurbs are written to pass automated matching. HN paragraphs are read by one person who already clicked into the thread on purpose.
Write for that one person. Lead with the specific thing you ship, not the generic frame ("experienced full-stack engineer looking for interesting problems"). The frame is the thread itself.
Rewrite the pitch: four lines, in this order
A "Who wants to be hired?" paragraph that gets replies has four lines and roughly 90 words: stack, proof, constraints, contact. Everything else is noise.
- One line of stack and specialization. "Rust + embedded, 7 years, controls systems" beats "polyglot full-stack engineer." Specific pools are thin. In Refolk's index, only 618 US software engineers list Rust as a skill, 0.3% of the senior pool. A credible Rust pitch competes with maybe a dozen others in October's thread. A generalist TypeScript pitch competes with hundreds.
- One line of proof, with a number and a named thing. "Rebuilt the Stripe webhook pipeline, cut p99 from 2.1s to 180ms" is proof. "Passionate about scale" is not. If you cannot name the company publicly, name the system and the magnitude.
- One line of constraints. Remote, hybrid, city, visa status, comp band if you want to filter. Hiring managers love this line because it saves them an email.
- One line of contact. Email, GitHub, a link that renders a real resume, not a LinkedIn URL that bounces into a login wall.
The common failure mode is burying line 2 under three sentences of career narrative. Hiring managers reading the October thread are scanning 566 of these. If your first 15 words do not include a stack and a verb, you lose.
What the October company posts tell you to mirror
The company posts themselves are the cheat sheet for how to write yours. Three to study:
- azaslavsky's October post: lists a Rust controls engineer, a front-end role, a Rust+LabVIEW generalist, plus integration engineers in Kent and Moses Lake. Dense, geographic, specific.
- Mainmatter / EuroRust: hiring a Rust consultant lead, name-drops Google, BMW, and Redis as clients. Uses specialist shop positioning instead of "fast-growing startup."
- Namespace: lists five engineering roles and name-drops SpaceXAI, Ramp, Sierra, Fal, Vanta, Framer, and ElevenLabs as customers in a single paragraph.
The density is the point. Candidates whose paragraph matches the density of the company posts in the sibling thread read as the same species. Candidates who write loose, resume-objective prose read as tourists.
"Agentic coding" is now 4-5% of company posts
The vocabulary in HN company posts has shifted. Mentions of "coding agents," "Codex," and "agentic coding" went from 1-2% of posts through May 2026 to 4-5% in July through October, roughly 4x in a quarter.
Read the sibling thread carefully: these posts are hiring engineers to work with agents, not build agents. That is a different line on your resume.
- Dated: "Shipped feature X in Y weeks."
- Current: "Shipped feature X in Y weeks running a Claude Code + reviewer loop on the service layer."
The hiring manager at a company that just mentioned "we use coding agents heavily" in their post is scanning for whether you have actually done it, not whether you have an opinion about it. One concrete bullet beats a paragraph of philosophy. If your resume still reads like 2023 and you need to update it against a specific posting from the October thread, Refolk will tailor it for you: paste the HN company's post, get your resume back rewritten with the stack and workflow language they just used.
The company posts themselves are the cheat sheet. Candidates who match their density read as the same species.
Zero YC-backed companies in the comp-published subset
A curated subset of October's HN roles with published salary bands shows a median band of $160k to $213k, a top band of $350k, 65% remote, and zero YC-backed companies. If you are tuning your pitch for "YC startup energy," you are miscalibrated for who is actually posting with real comp this month.
The ctaio.dev view of October's thread captured 20 roles that disclosed bands. The breakdown:
| Attribute | Value (Oct 2026 curated subset) |
|---|---|
| Median band | $160k - $213k |
| Top band | $350k |
| Remote-friendly | 65% |
| YC-backed | 0% |
Two reads of the zero:
- The companies with the budget to publish bands this month are post-startup: Series C and up, public, or bootstrapped-profitable (Mainmatter and Namespace in the broader thread, alongside Skydio's robotics roles in San Mateo and Zurich posted by a Senior Director of Engineering).
- YC companies are still posting, but either without bands or in a different comp band entirely. Either way, mirroring their vibe in your pitch does not match the readers who disclose.
For the candidate pitch, this is a cue to drop phrases like "want to join early-stage" if you actually want responses from the posters publishing comp. "Open to Series B and up, remote US" filters correctly.
Three monitoring moves while the thread runs
Checking news.ycombinator.com/item?id=49922569 fifteen times a day is the wrong workflow. There are three better moves for the four weeks a monthly thread stays warm.
- Subscribe to HNHIRING.com's filter for your stack. It indexes the thread continuously and lets you watch Rust, Elixir, Scala, or whatever thin pool matches your profile, instead of ctrl-F on 266 jobs.
- Use ctaio.dev's salary-band view to see which posters disclosed comp. If a company is in that view, you can tune your cover note to their band rather than guessing.
- Keep a tailored resume per posting, not per thread. The company posts in the October thread range from Skydio robotics roles to Rust consulting at Mainmatter to infra at Namespace. One resume will not land across them. This is what Refolk does automatically: paste the HN company post, get your resume rewritten to the stack and seniority and location they named, with a fit score so you know whether to send it at all.
The follow-up that outperforms a second application
If you post in "Who wants to be hired?" and a company replies, do not respond with "attached is my resume." Reply with a three-line note that references the specific role in their "Who is hiring?" post (Rust controls engineer, not "the role you mentioned"), one proof point from your paragraph expanded with a number, and a single question about scope.
That is the exchange that converts. The companies posting in October are reading maybe 50 inbound replies per role. The ones that read like a continuation of a conversation, not a cold application, get a call.
The bottom line for October 2026
Write for a thread that has 2.56x more candidates than companies, where the companies are a third fewer than a year ago, where "agentic coding" is now standard vocabulary, and where the readers are hiring managers who already know this is a self-selection pool. Specialization wins, density wins, and the first 15 words carry the paragraph.
The October thread closes when the November one opens, around Nov 1. That is four weeks to post, iterate, and reply. Rewrite the pitch tonight.
FAQ
How many candidates are in October 2026's HN "Who wants to be hired?" thread?
The dev.to analysis counted 566 candidate posts in the first week of October 2026, against 221 hiring company posts in the sibling "Who is hiring?" thread. That is a 2.56:1 candidates-to-company ratio, up from 1.2:1 in April and 2.2:1 in September. Both the candidate count rising (+47% in six months) and the company count falling (−31% in six months) drive the ratio.
Should I post in "Who wants to be hired?" or just apply to "Who is hiring?"
Do both, but spend more time on the applications. The "Who is hiring?" thread has 221 companies you can email directly this month, and a tailored reply to a specific role will outperform a generic self-pitch read by hiring managers scanning 566 candidate paragraphs. Posting in "Who wants to be hired?" is cheap insurance; applying to specific roles is where the responses come from.
What should I put in my HN pitch paragraph?
Four lines, roughly 90 words: stack and specialization, one proof point with a number and a named system, your constraints (remote, visa, comp floor), and contact. Skip the career narrative and the "passionate about" opener. The hiring managers reading the thread are scanning for signal density, and your first 15 words should include a stack and a verb.
Is agentic coding really expected on a 2026 engineering resume?
For companies whose October HN posts mention coding agents or Codex (now 4-5% of posts, up from 1-2% in May), yes, but as a workflow bullet, not a philosophy. "Shipped feature X running a Claude Code plus reviewer loop" lands. "Enthusiastic about AI-augmented development" does not. The posting itself tells you which companies care; mirror the vocabulary they used.