The September 2026 "Ask HN: Who wants to be hired?" thread went live on Sept 7, and within 48 hours it was already stacked with resume-dumps that will never get a reply. The reader on the other side is a founder with 30 seconds and Ctrl-F. If your post reads like a LinkedIn bio, you are invisible.
This is a surgical rewrite. Six lines, in the order Hacker News expects them, tuned to what has actually changed about the pool you are competing against.
Why most Sept 2026 posts get zero replies
Most posts fail because they are pitched at 2019's HN reader (a curious CTO scanning for anyone) and land in front of 2026's HN reader (a cautious founder scanning for a specific shipped outcome). The thread itself has aged up around you.
Per HireIndex, the community-built dataset of past "Who wants to be hired" threads, average poster experience has drifted from roughly 7.5 years in 2022 to 9+ years in December 2025 and January 2026. Junior (0 to 2) posts have steadily declined since the 2023 downturn. Your competition is not a bootcamp grad. It is a Staff engineer with a Databricks line on their resume.
Up from ~7.5 years in 2022 per HireIndex's analysis of the monthly thread.
That single shift breaks the old advice. "10 YOE, full-stack, ex-FAANG" is table stakes now. It differentiates nothing. What breaks through is a specific shipped outcome in line one and a scarce technology tag in line four.
The 72-hour timing window nobody respects
Post within five minutes of the thread going live, or accept that your post is buried. The "whoishiring" bot posts both the "Who is Hiring?" and "Who wants to be hired?" threads on the first of each month at 11:00 AM Eastern. The thread rides the front page on day one, and most engagement happens in the first 72 hours.
- Day 1: front page, majority of founder scrolls, most replies.
- Days 2 to 3: still active, Ctrl-F traffic from bookmarked tabs.
- Day 4+: effectively dead. New comments are timestamped low and buried under earlier ones.
If you missed the September 7 window, the honest move is to prep now for October 1 at 11:05 AM ET rather than posting late into a dead thread. Sort your outcomes, pick your scarce keyword, and have the six lines ready to paste on the minute.
The six lines, in order
Mirror the exact template the "whoishiring" bot uses: Location / Remote / Willing to relocate / Technologies / Résumé/CV / Email. The thread rules explicitly ban agencies, recruiters, and job boards, and readers apply the same off-format eye to candidate posts. Formatting is a trust signal, not a preference.
Here is the skeleton, with what each line should actually do:
- Headline line (before Location): One sentence naming a shipped outcome with a number. Not a title.
- Location: City, country. No metro-area euphemisms.
- Remote: Yes/No/Hybrid, plus timezone overlap window if remote.
- Willing to relocate: Specific countries or "No". "Open to the right opportunity" reads as no.
- Technologies: Six tags maximum, front-loaded with your scarcest one.
- Résumé / Email: A working link and a plain email. Not a Calendly.
The two levers that decide whether you get replies are line 1 (the outcome) and line 5 (the scarce tag). Everything else is a hygiene check.
Line 1: the outcome, not the title
Founders scan for verbs and numbers. "Staff Engineer, 12 YOE" tells them nothing. "Cut Postgres p99 from 900ms to 40ms on a 4TB table, migrated 60 services to it" tells them exactly what you do on a Tuesday.
A founder reading the thread is triaging against a specific pain they woke up with. A concrete, numeric outcome pattern-matches to that pain in about two seconds. A title matches to nothing until they read three more lines, which they will not.
If pulling the right shipped outcome out of a decade of work is the part that stalls you, that is the exact work Refolk takes off you. Refolk writes your resume from your own history and pulls the outcome lines that survive a founder's Ctrl-F.
Line 5: the scarcest technology tag first
Lead with your rarest skill, even if it is 20% of your day job. In Refolk's index of professional profiles, US-based Software Engineers listing Rust total roughly 2,177 globally. US Staff Software Engineers total roughly 32,571. That is a ~1:15 scarcity ratio, and Oxide Computer Company alone employs 4x the next-largest Rust employer.
| Segment | Total in Refolk's index | Top employer | Top location |
|---|---|---|---|
| Staff Software Engineer, US | 32,571 | Databricks (2x next) | San Francisco |
| Software Engineer + Rust (global) | 2,177 | Oxide Computer Company (4x next) | Distributed (SF, Paris, Bengaluru tied) |
| Scarcity ratio | ~1 : 15 | ||
| HN "Who is Hiring" comments/month | 400 to 800 | ||
| Poster seniority drift (2022 → 2026) | 7.5 → 9+ yrs |
The practical rule: if your scarcest tag has a ~15:1 scarcity ratio like Rust, one line beats a paragraph. Founders searching Ctrl-F for "Rust" will find you regardless of prose quality. If your stack is generic (React, Python, AWS), you cannot win on scarcity, so you have to win on outcome specificity in line 1.
What "scarce" actually means in Sept 2026
Scarce means the ratio of profiles listing the skill to open roles asking for it is low enough that Ctrl-F does the selling for you. It is not the same as "trendy."
Tags that behave as scarce in Refolk's index and the recent thread data:
- Rust, especially with distributed systems or embedded context.
- CUDA kernels and low-level GPU work, not "used PyTorch."
- Formal verification, TLA+, model checking.
- Postgres internals, not "used Postgres."
- Compilers, LLVM, language runtimes.
Tags that read as scarce but are not, because everyone claims them:
- "LLM" or "GenAI" with no shipped surface. Every third post has this.
- "AI Engineer" as a title. It resolves to nothing on Ctrl-F.
- "Full-stack." Universal, so it filters nothing in.
The macro line to lead with (and the one to kill)
Lead with cost savings or revenue that survives a cautious hiring committee, and kill any phrasing that assumes "hiring is back." The global Net Employment Outlook for Q2 2026 sits at 31%, its strongest reading since Q3 2022, up six points quarter over quarter and seven year over year. But the Information sector NEO is 29% and has cooled slightly, while construction and professional/technical services sit at 27%. Tech is no longer leading.
Founders reading HN in Sept 2026 have been through two years of "efficient teams" messaging from their boards. A candidate line that reads "I made the team smaller and shipped more" clears the committee. A line that reads "I'm passionate about building world-class products" does not.
On HN in 2026, "passionate" is a negative signal. "Cut infra bill 43%" is a positive one.
The LinkedIn "Open to Work" equivalent, and why it's the opposite
An "Open to Work" post on LinkedIn is the reverse job application format for a fundamentally different audience: recruiters and second-degree connections, not founders. The register flips almost entirely.
| Element | HN "Who wants to be hired" | LinkedIn "Open to Work" |
|---|---|---|
| Reader | Founder or hiring engineer | Recruiter, weak-tie connection |
| Scan mode | Ctrl-F for tech tags | Feed scroll, first two lines |
| Best line 1 | Shipped outcome with number | Named role + location + start date |
| Tone | Terse, technical, humble | Warm, specific, still concrete |
| Fatal phrase | "Passionate," "results-driven" | "Any and all leads welcome" (too diffuse) |
| Format signal | Location / Remote / Tech / Email | Photo frame + banner + first-comment detail |
On LinkedIn, "Looking for Senior Backend roles, remote in EST, starting Oct 20, 8 years in payments infra" outperforms the HN-style outcome-first line, because the reader is filtering by role and availability, not by pain. Different audience, different pitch, same underlying resume.
Writing both versions from the same career history without either sounding warmed-over is manual work. Refolk drafts each variant against the specific posting or thread, so the HN version leads with the shipped number and the LinkedIn version leads with the role and start date.
A concrete before/after
Take the daily.dev mirror of an August 2026 poster: data analyst, C/R/Python/SQL, willing to relocate to Canada/US/Germany. The bones are correct. The bones are not enough.
Before (typical):
Data Analyst with 6 years of experience. Passionate about turning data into insights. Skilled in Python, SQL, R, and C. Open to remote or relocation.
Location: Lagos, Nigeria Remote: Yes Willing to relocate: Canada, US, Germany Technologies: Python, SQL, R, C, Tableau, Excel Résumé: [link] Email: [addr]
After (six-line rewrite):
Built the fraud-scoring pipeline that cut chargebacks 31% at a 2M-user fintech (Python + Postgres, 6 YOE).
Location: Lagos, Nigeria Remote: Yes, 4h overlap with US Eastern Willing to relocate: Canada, US, Germany (visa-ready for all three) Technologies: Postgres internals, Python, dbt, SQL, R, causal inference Résumé: [link] Email: [addr]
Same person. Line 1 now names a shipped outcome with a number. Line 3 removes ambiguity about visa status, which is the first thing a founder assumes will be a problem. Line 5 leads with "Postgres internals" (scarce on Ctrl-F) instead of "Python" (universal), and drops Excel/Tableau/C, which add nothing for the roles this candidate actually wants.
Three rules for the reply thread
Getting replies is half the battle. Handling them is the other half.
- Reply within one hour, every time, for 72 hours. Founders often DM two or three candidates at once and go with the first coherent reply. Speed compounds.
- Answer the exact question, not the meta-question. If they ask "are you open to on-site in NYC three days a week," answer that in the first sentence. Do not lead with your background.
- Send the tailored resume in the first reply, not the generic one. If they mention their stack or product, the resume you send back should reflect it. This is the friction Refolk removes: paste the founder's reply and the JD if they linked one, get back a version of your resume aimed at their specific pain and a fit score before you hit send.
What to cut from your current draft
If you already posted, or drafted something, run this checklist and cut mercilessly:
- Any adjective that could apply to anyone ("passionate," "driven," "world-class").
- Any technology in your tag line that is universal in your field.
- Any "open to opportunities" phrasing. Name the countries, or say no.
- Calendly links. Founders want to email, not book.
- More than six technology tags. Six is the ceiling before Ctrl-F stops helping you.
- Any mention of "AI" without a specific shipped surface behind it.
The six-line format is not a straitjacket. It is the shape the reader is trained to skim. Fight it and you lose to the Staff engineer three comments down who mirrored it exactly.
FAQ
When exactly does the next HN "Who wants to be hired?" thread go live?
The "whoishiring" bot posts on the first of each month at 11:00 AM Eastern. October 2026 will land Wednesday, Oct 1 at 11:00 AM ET. The thread stays on the front page for the first day, and most engagement happens in the first 72 hours. Post within five minutes of the drop or expect a small fraction of the reply volume a top-of-thread post gets.
Is it worth posting if my stack is generic (React, Python, AWS)?
Yes, but you cannot win on the Technologies line, so you have to win on line 1. Lead with the most specific shipped outcome you have (a numeric business result, not a title), and pick a niche within your generic stack as your first tag ("Postgres internals" not "SQL," "Next.js App Router" not "React"). Generic tags plus generic outcomes get zero replies. Generic tags plus a concrete revenue or cost number still get a handful.
Should I use the same post on HN and LinkedIn?
No. HN's audience is founders and hiring engineers who Ctrl-F for tech tags and read for shipped outcomes; LinkedIn's audience is recruiters who feed-scroll and filter for role and start date. Same underlying career history, opposite register. On HN, terse and technical wins. On LinkedIn, "passionate" is neutral and "any and all leads welcome" is fatally diffuse. Write both versions, do not cross-post one.
How many replies is a "good" post supposed to get?
There is no public benchmark, but a useful proxy is the "Who is Hiring?" side, which draws 400 to 800 top-level company comments per month. That is the ceiling of founder attention available. A well-formatted, scarce-stack post with a numeric line 1 typically pulls a handful to a dozen serious replies in the first 72 hours. If you get zero, the problem is almost always line 1 (no shipped outcome) or line 5 (no scarce tag), not the market.