The September 2026 "Ask HN: Who wants to be hired?" thread is live (item 49522896), and it is one of the last inbound channels where founders read your post themselves instead of an ATS filtering you out. The catch: the format is strict, and if you get the labels wrong, four separate third-party parsers silently drop you.
This is a guide to writing the six lines that actually get you email.
Why the September 2026 thread matters right now
The Hacker News "Who wants to be hired" thread is a monthly, inbound-only job channel where founders and hiring managers email candidates directly, with agencies, recruiters, and job boards explicitly off topic. The September 2026 edition (item 49522896) went live Sept 1, and its companion "Who is hiring?" thread sits at 254 points and ~397 comments about two weeks in.
The conversion rate is real. One hiring poster in the September thread disclosed that their August posting pulled 216 applications and produced roughly 10 offers. That is a 4.6% offer rate on a channel with no LinkedIn Easy Apply, no reverse recruiter middleman, and no ATS keyword gate.
10 offers from 216 applications, disclosed by the poster in September's thread.
Compare that to the LinkedIn baseline, where a Workday application to a cold posting effectively goes into a pile the recruiter never opens. HN's channel is different because the audience is founders, the format is uniform, and the reply comes from a human inbox.
The scale mismatch that actually helps you
The catalog looks brutal on paper. In my index, there are roughly 199,018 senior software and ML engineers currently based in the US (Senior SE, Staff Engineer, MLE titles). Against ~397 hiring comments in the September thread, that is a 501:1 candidate-to-demand ratio.
But almost none of those 199,018 engineers post in "Who wants to be hired." The effective competition inside the thread is a few hundred candidate comments, most of them poorly formatted. That is the inversion: LinkedIn's "Open to Work" badge broadcasts to nobody in particular. A well-structured WWTBH post is read by every founder skimming the thread with Cmd-F on a specific stack.
The 6-line format, exactly
The enforced format is six labeled lines, in this order: Location:, Remote:, Willing to relocate:, Technologies:, Résumé/CV:, Email:. Every third-party parser keys off those exact colon labels via regex, so a missing or renamed field removes you from every automated funnel founders use to search the thread.
Here is the minimal template:
Location: Brooklyn, NY
Remote: Yes (US timezones)
Willing to relocate: NYC, London, Berlin
Technologies: Go, Rust, Postgres, Kafka, Kubernetes, Terraform, ClickHouse
Résumé/CV: https://yourdomain.com/resume.pdf
Email: you@yourdomain.com
Then two or three short paragraphs underneath. Not a wall. Not a life story. One specific system you built, one thing you want to work on next, and a signal about the environment you thrive in (early-stage, infra-heavy, product-facing, whatever is true).
Why the labels matter more than the content
The thread header explicitly lists the search tools built on top of it: nthesis.ai/public/hn-who-is-hiring, dheerajck.github.io/hnwhoishiring, nchelluri.github.io/hnjobs, and hnjobs.emilburzo.com, plus hnmatchmaker.com which matches individual WWTBH posters to open roles at hnmatchmaker.com/user/:user_name. All of them parse on the field labels. If you write "Based in:" instead of "Location:", you fall out of at least four indexes at once.
Before you consider your post shipped, load your HN username into hnmatchmaker and confirm it returns rows. If it does not, your labels are wrong.
What the 6 fields should actually say
Each of the six fields has a right answer that most posters get wrong. Location is not a résumé, Technologies is not a skills dump, and "Remote only" costs you a large share of the thread.
| Field | Common mistake | What to write instead |
|---|---|---|
| Location | "SF Bay Area" (default) | The specific metro you actually live in, with country if outside the US |
| Remote | "Yes" | "Yes (US timezones)" or "Yes (EU, up to 2h overlap with US-East)" |
| Willing to relocate | "No" | At least one city, even if reluctant: "NYC, London" |
| Technologies | 30-item skills dump | 6-10 items in the stack you actually want to work in |
| Résumé/CV | Google Doc link with edit permissions | A stable PDF URL on a domain you own |
| Work email | A personal email tied to your domain |
One useful piece of data on the Location line: in my index, Los Angeles, New York, and Greater Boston are tied as the largest concentrations of senior US engineers, ahead of San Francisco. If you live in one of those, write it. Founders posting from NYC or Boston Cmd-F their own city and skip past a wall of "SF Bay Area."
The "Willing to relocate" line is the highest-leverage field
Most posters copy "Remote only" and think they are done. That is the single most expensive mistake in the thread, because a large share of the hiring posts specify ONSITE or HYBRID, and parsers use the relocate field as a filter. Adding even one city to "Willing to relocate" multiplies the number of hiring posts that surface you.
If you are genuinely remote-only, still list the two or three cities you would consider for the right role. You can always decline. You cannot get an email from a founder whose parser never returned you.
The Technologies line is a keyword-match target
HNHIRING has indexed 60,306 job ads dating back to January 2018. Before you write your Technologies line, spend 15 minutes searching hnhiring.com for the exact stack terms hiring managers actually use in the postings you would want. Mirror those. If founders in your space write "Postgres" and you write "PostgreSQL," you lose Cmd-F matches.
This is one of the pieces of work generic resume tools cannot do, because it requires reading the specific market you are targeting. Refolk writes your resume from your own history and tailors it to a specific posting, which is the same discipline you want on your Technologies line: match the phrasing of the roles you actually want, not the phrasing you happened to use at your last job.
The two paragraphs under the labels
Below the six lines, write two short paragraphs. The first names one specific system or engagement. The second says what you want next.
Founders read hundreds of these. The differentiator is specificity: "led the migration of a 40TB Postgres fleet off RDS to self-hosted, cut monthly infra cost 62%" beats "experienced backend engineer with strong AWS skills." Numbers, systems, scale. One paragraph, three sentences.
Founders in the thread do not want a summary. They want one story concrete enough to argue about.
The Sept 2026 hiring poster html5cat explicitly complained about "AI slop" applications and said his goal is to respond to every earnestly submitted application despite the sea of AI slop. That is a signal. A post that reads like it was generated from a prompt loses to a post that name-drops one real engagement, even a small one.
The AI-slop filter is now the differentiator
Founders on WWTBH read posts personally, unlike ATS pipelines that regex on keywords. A generic "passionate about scalable systems" line gets skipped. A line that says "spent 18 months building a rules engine for insurance underwriting at a 12-person startup, the thing processed 400 policies a day" gets an email.
Another example worth studying: Lumen Labs posted a SF robotics role in September's "Who is hiring" at $130k-$200k plus equity, with co-founder Daniel Van Zant writing personally. That is who is on the other side of the thread. Not a coordinator with a checklist.
Reposting is expected, not spammy
The thread runs monthly and hiring posters explicitly invite reposting: "Feel free to submit, even if you already did in the past." Candidates who post once, get no replies, and give up are ignoring that this is a 12-shot-a-year channel.
The 2026 archive so far:
- January: item 46459274
- April companion: item 47601859
- June: item 48357724
- July: item 48747975
- August: item 49156682
- September: item 49522896
Post every month. Iterate the Technologies line based on which hiring posts surfaced in that month's companion thread. If you were job-searching from January through September, that is nine shots at inbound from founders who read HN. Almost nobody uses all nine.
What to change between reposts
Do not paste the same block every month. Change one variable and watch the response rate:
- Swap the specific engagement in your first paragraph, so the same reader sees a new hook.
- Reorder the Technologies line to lead with whatever stack the companion "Who is hiring?" thread was heaviest on that month.
- Add or remove a relocate city based on which metros showed up in that month's hiring posts.
- Rotate the résumé link if you have variants tuned to different role families (infra vs product vs ML).
The last one is where most engineers stall. Maintaining three tailored résumé variants by hand is annoying enough that people stop doing it after month two. Refolk scores how well you actually fit a given posting and rewrites the resume for it, which is the mechanic that keeps reposting sustainable across a nine-month search.
The post-publish checklist
After you hit submit on your comment, do four things in this order:
- Load
hnmatchmaker.com/user/your-hn-usernameand confirm it returns matched roles. If empty, your labels are broken. - Search hnhiring.com for two of your Technologies keywords and confirm your post is indexed within 24 hours.
- Skim the companion "Who is hiring?" thread and directly email 3-5 founders whose posts match your stack. WWTBH is inbound, but nothing stops you from going outbound off the back of it.
- Set a calendar reminder for the first of next month to repost, with one variable changed.
Steps 3 and 4 are where the 4.6% offer rate from that August poster becomes reachable. The thread is inbound by design, but the highest-converting candidates treat it as a directory, not a mailbox.
FAQ
When does the next Hacker News "Who wants to be hired" thread post?
The thread posts on the first of every month by user whoishiring. The September 2026 thread is item 49522896. October's will appear on Oct 1, 2026, and you can subscribe by following the whoishiring account and enabling submission notifications, or by checking news.ycombinator.com/submitted?id=whoishiring on the first of the month.
Do I need a personal domain for the Résumé/CV and Email lines?
Not strictly, but it helps signal. A résumé at yourdomain.com/resume.pdf and an email at you@yourdomain.com reads as a working engineer who owns their own infrastructure, which is the audience HN founders self-select for. A Google Doc link with edit permissions accidentally left on is the most common self-inflicted wound. If you use a Google Doc, set it to "Anyone with the link can view," not edit or comment.
Should I mention salary expectations in the post?
No. The six enforced fields do not include compensation, and adding a "Salary:" line reads as either desperate or entitled depending on the number. Founders who email you will ask, and that conversation happens in email where you can calibrate to the specific role. Putting a range in the public post filters out the founders who would have paid more once they liked you.
Is it worth posting if I am currently employed and only passively looking?
Yes, and it is arguably the best use of the channel. The founders emailing you are pre-qualified: they read HN, they took the time to write a personal message, and they are not going to spam you the way a LinkedIn InMail from a contract recruiter will. Add "(currently employed, exploring)" as a short note in the paragraphs under the labels, keep the résumé link current, and treat the resulting inbox as market research even in months you are not actively interviewing.