The "Ask HN: Who is hiring? (September 2026)" thread went live on Sept 5, 2026, and one poster did something the rest of the market almost never does: he published his funnel. 216 applications in August. Roughly 10 offers. A 4.6% offer rate on a channel with no ATS, where the founder reads every reply personally. If you are about to paste your usual resume-bullet paragraph into a comment, stop.
This is not LinkedIn Easy Apply. The rules are different, the reader is different, and the math is dramatically better if you actually play the channel.
Why the 216-to-10 disclosure matters
A 4.6% offer rate on Hacker News "Who is Hiring" is roughly 5 to 10 times the offer rate on a typical cold ATS application, because a human reads every reply and no keyword filter stands between you and them. That is the single most important fact for anyone deciding how to spend their September application time.
The verbatim disclosure from the September 2026 thread:
We received 216 applications in our August posting, and issued offers to approximately 10. Applicants must meet a high bar. I intend to have a personal relationship with every hire.
Two things are hiding in that quote. First, "personal relationship with every hire" tells you the reader is optimizing for signal, not throughput. Second, 216 is a small enough number that any reply which fails to pattern-match the project in the first three lines gets skimmed and discarded in under ten seconds. The bottleneck on this channel is not scale. It is signal-to-fluff ratio in the opening.
10 offers on 216 August applications, disclosed publicly in the September 2026 thread.
The rules of the thread, in plain English
The September 2026 thread (HN item 49522897) follows the same posting norms it has used since 2018: employers must be personally part of the hiring company, one post per company, and posters commit to replying to applicants. The companion "Who wants to be hired?" thread (item 49522896) uses a fixed schema every candidate should copy verbatim.
The schema:
- Location
- Remote
- Willing to relocate
- Technologies
- Résumé/CV
The HNHIRING index that most job seekers use to search across threads now contains 60,278 job ads dating back to January 2018. That gives you a searchable corpus for filtering by stack, remote status, and city. If you are replying rather than posting, use it in reverse: search the poster's company name to see if they have posted before, and what they have said they want.
Two culture rules matter more than they look:
- HN readers penalize corporate boilerplate. Transparency, humility, and technical depth win. Marketing language loses.
- Several September 2026 employers explicitly ban automated applications. One EU retail-tech poster wrote "we kindly ask for no automated applications." Another: "We are the hiring company and will reply to all genuine applicants. No recruiters, no agencies, please."
That does not mean you cannot use tools to draft. It means the output has to read like a person who read the post wrote it in one sitting.
The addressable pool is bigger than the thread
The 216 applicants who hit that one August post are a tiny slice of the qualified U.S. supply, which is why speed and specificity beat resume polish on this channel. If you fit the profile and you have not applied yet, the competition is thinner than it looks.
Here is the shape of the pool, using Refolk's index of professional profiles alongside the public HN numbers:
| Segment | Count | Source |
|---|---|---|
| U.S. senior engineers with TypeScript + Python (Staff/Founding titles) | 1,662 | Refolk's index |
| U.S. professionals currently titled "Founding Engineer" | 4,352 | Refolk's index |
| HN August 2026 applications, one poster | 216 | Sept 2026 HN thread |
| HN August 2026 offers, same poster | ~10 | Same disclosure |
| Implied offer rate | 4.6% | 10 / 216 |
| Founding Engineers concentrated in SF Bay Area | ~20% | Refolk's index sample |
Read that top row again. There are 1,662 U.S. senior engineers who list TypeScript and Python and hold Staff or Founding titles. Roughly 4,352 people in the U.S. currently carry the "Founding Engineer" title outright. A single HN post pulling 216 replies is capturing well under 10% of the qualified pool. The majority of people the hiring manager wants to hear from never apply.
That is the leverage point. If you are on the fence about replying, the funnel math says apply.
The one-sentence topic match that beats a resume
On a no-ATS channel, the first sentence of your reply must echo the poster's stated project in their exact vocabulary, because a human is scanning for topic match, not keyword density. Get that sentence right and the rest of the reply is almost defensive writing.
The 216-to-10 poster described the ideal candidate as someone who can "design RL benchmarks, red-team model outputs, and create rubrics to evaluate and enhance the agentic coding capabilities of various frontier models." A strong opening lifts that phrase directly:
"I have designed RL benchmarks and evaluation rubrics for agentic coding on Claude and GPT-4 class models. Three examples: [link], [link], [link]. Details below."
That opening does four things in three lines. It matches the exact phrase the reader wrote. It shows three concrete artifacts. It signals seniority without a title. It does not waste a word on why you are excited about the mission.
This is the exact rewrite work that Refolk does for every posting: paste the HN comment, get your own resume rewritten to match the poster's language and project, and get a fit score before you send. On a channel with 216 replies competing for one reader's attention, that first-sentence match is the whole game.
The subject-line filter that quietly kills applications
Several September 2026 HN posters use a literal subject-line format as a first-pass filter, and applicants who ignore it get auto-sorted into a folder the founder never opens. This is the most mechanical, most fixable cause of rejection on the entire channel.
Real examples from the current thread:
- One Dutch employer requires: "E-mail jobs[at]openeducation.foundation met (HN) + de functienaam in het onderwerp." Translation: subject line must contain "(HN)" and the role name.
- Netbird, remote-friendly out of Berlin, asks candidates to "please mention you found us on Hacker News in your application." A one-line signal the reader is measuring.
- Multiple posts require the format
(HN) + role namein the subject line, with no variation.
If a post specifies a subject line, treat it as a compile error. Get it exactly right or the reply does not run. If a post does not specify, use (HN) [Role Name] - [Your Name]. That format is universally readable and sorts cleanly in Gmail.
An engineer application email template that works on HN
The template below is the one to copy for direct-to-founder applications. It works because it front-loads topic match, keeps proof concrete, and respects the founder's time.
Subject: (HN) Staff Engineer, Agentic AI - Jamie Chen
Hi [Name],
Your post mentioned [exact phrase from their post, verbatim].
I have shipped three of these:
1. [Project], [outcome with a number], [link]
2. [Project], [outcome with a number], [link]
3. [Project], [outcome with a number], [link]
Location: [City], [Timezone]
Remote: Yes / hybrid / on-site OK
Comp expectation: $[X]k base, open on structure
Notice: [2 weeks / immediate / 30 days]
Resume: [link]
GitHub: [link]
Happy to do a paid trial task this week.
- Jamie
Why each block earns its place:
- Subject line: matches any explicit format rule, sorts cleanly, and names the role so the founder does not have to guess which posting you mean.
- First sentence: verbatim topic match. This is what a human skim rewards.
- Three proof points with links: not bullets from a resume, but shipped artifacts a reader can click in ten seconds.
- Logistics block: answers every question a founder has to ask before scheduling a call. Removing that back-and-forth is a real courtesy.
- Paid trial offer: signals confidence and matches how a lot of HN founders actually evaluate: a small paid contract, then an offer.
The logistics block also mirrors the "Who wants to be hired?" schema, which the reader is trained to skim. Do not fight the format.
What the resume behind the link should look like
A resume for a direct hiring manager reads nothing like a resume for an ATS: it leads with the specific stack and project type the founder named, cuts anything unrelated, and fits on one page. The link in your HN reply is a proof document, not a career history.
The current September 2026 thread name-checks these stacks. If you match one, name it in your resume in the exact spelling the poster used:
- Ruby, Rails 8.x, StimulusJS, Hotwire, Turbo, AlpineJS, Postgres, Docker, DigitalOcean, OpenAPI, LLMs
- TypeScript, Yjs, React, Python, OpenTofu, Terraform, Scaleway, managed PostgreSQL, managed Kubernetes
Two moves that matter:
- Move the stack line above your work history. The reader is looking for topic match, not chronology.
- Cut every bullet that does not touch the posted stack or the posted problem. A three-bullet Rails role beats a ten-bullet role that buries Rails on line eight.
Tailoring resume by resume is exactly the friction Refolk removes. Paste the HN posting, get a resume rewritten to that posting's stack and vocabulary, and get a fit score so you know whether the reply is worth sending in the first place. On a channel where the reader converts at 4.6%, a resume that actually matches the post is a rate multiplier, not a nice-to-have.
Comp anchors and where to differentiate
Comp signals in the September 2026 thread are unusually explicit, and matching them in your reply builds trust in a way that vague "open to market" language does not. Post a range or a number.
Real anchor from the current thread: Republic Services is hiring a Staff Engineer, Agentic AI, remote US, with "$175k is our salary midpoint + 20% target bonus." Matcha.fm is hiring full-stack, frontend, and growth roles fully remote across US, CA, EU, UK, BR, and LATAM. cloro is hiring Founding Engineer, Data Scientist, Ops, and Marketer roles remote in EU.
Two ways to differentiate without lying about experience:
- Timezone coverage: 20% of Founding Engineers in Refolk's sample cluster in the SF Bay Area. If you are in Lisbon, Chattanooga, or Berlin, you can credibly offer overlap with EU customers that a Bay Area candidate cannot.
- Burn rate math: a $155k engineer in Portland is a lower cash risk than a $220k engineer in San Francisco for a seed-stage founder. Say the number.
One September 2026 employer states outright that they "already hired two backend developers through 'HN - Who is Hiring'" and are now hiring a Lead Product Engineer on Rails. This channel converts. The question is whether your reply looks like the ones that already got offers.
FAQ
How do I find the September 2026 thread and search it?
Go to news.ycombinator.com and search "Who is hiring September 2026" or use item id 49522897 directly. For structured search across the thread and previous months, hnhiring.com indexes 60,278 job ads dating back to January 2018 and lets you filter by technology and location. Search the poster's company name to see whether they have posted before, and what they have said they want in prior threads.
Is it OK to reply with the same template to multiple posts?
No. The topic-match sentence has to change per post, because that is the one thing the reader is scanning for. The logistics block (location, remote, comp expectation, notice period) can stay identical. The three proof points should reorder per post so the most relevant one is on top. If you are applying to more than five posts in the September thread, this is the exact tailoring work Refolk automates: one paste per posting, a rewritten resume and reply, and a fit score before you send.
Should I include a cover letter or just the HN comment?
The HN comment or email body is the cover letter. Do not attach a separate cover letter document. Founders reading the September 2026 thread will not open a second attachment when the first three lines of your comment already answered the question of whether you match. Keep the resume link visible and the email body under 200 words.
What if I do not have three shipped projects to link?
Link what you have and be honest about scope. One production system with real users beats three side projects with no traffic, and founders on HN can tell the difference in about eight seconds. If your best proof is an open-source contribution, a technical writeup, or a paid consulting engagement, link that. The 216-to-10 poster is filtering for signal, not credential count, and a specific writeup on "how I designed an eval rubric for a coding agent" will out-perform a generic FAANG resume for that particular post.