If you are job hunting as an engineer right now, the August 2026 Hacker News "Who wants to be hired?" thread (item 49156682) is a channel where six lines of plain text outperform a polished PDF. Almost nobody writes those six lines like ad copy, and it costs them the reply.
The thread went live on Aug 4, 2026, alongside a "Who is Hiring?" companion (item 49156683) stuffed with Anduril, Proxima Fusion, Chainguard, and Bucket Robotics roles. This is a teardown of how to write the candidate post so those specific employers email you back.
Why the August 2026 thread is worth 15 minutes of your day
The HN hiring threads are a thin, high-signal market where a well-written candidate post gets read by founders and staff engineers directly, not by an ATS. Monthly threads draw 400 to 800 top-level employer comments across every discipline, and employers explicitly Ctrl+F them for stack tokens.
The August 2026 pair is unusually strong on the employer side:
- Anduril posted 16 roles, including Senior Full-Stack Software Engineer, SIG in Santa Ana, CA. It is the highest-volume single poster in the thread.
- Proxima Fusion posted a Munich ONSITE Senior SWE (Dev Platform) role at 07:29 UTC on Aug 4. It is the first commercial stellarator spin-out from the Max Planck Institute for Plasma Physics, based on Wendelstein 7-X, with €650M+ raised and teams in Munich, Zurich and Oxford.
- Chainguard (whose hardened images ship inside Anduril, Canva, OpenAI, Snap, and Snowflake) is hiring a PM for its malware/greyware scanning engine.
- Crunchyroll (13), DoiT (10), and Encora (10) round out the top five posters.
- Bucket Robotics and Atom Computing (Boulder, Austin, Berkeley) fill the ONSITE-in-multiple-cities category.
One employer in the same thread reports 170 responses to their July post, 3 offers made, and a plan to hire ~5 people before Aug 31. That is a 1.8% offer rate from the employer's side. Your job is to invert it.
The six fields, and what each one is actually for
The "Who wants to be hired?" template is six labeled fields: Location, Remote, Willing to relocate, Technologies, Résumé/CV, Email. Each one has a different job, and treating them all as "biography" is the single biggest mistake in the thread.
Here is what each line is really doing:
- Location. A geographic Ctrl+F token. Write the city and metro area the way employers search for it ("Austin, TX" not "ATX", "London, UK" not "N1").
- Remote. A yes/no filter. If you will do hybrid, say the days ("Remote, or hybrid 2 days/week in NYC").
- Willing to relocate. A yes/no filter. If yes, list the cities you would actually move to. Anduril, Bucket Robotics, and Atom Computing all operate ONSITE in multiple cities and will skip vague "open to relocation" posts.
- Technologies. This is the ad. It is not a bio. It is a keyword collision surface for Ctrl+F.
- Résumé/CV. A link, not a paragraph. PDF or a personal page. No Google Doc "request access" walls.
- Email. Not the address on your CV. A separate inbox you check hourly on Aug 4 and 5.
The rule at the top of item 49156682 is strict: "Please only post if you are personally looking for work. Agencies, recruiters, job boards, and so on, are off topic here." Comments that ignore it get flagged.
The Technologies line is a Ctrl+F ad, not a bio
The single highest-leverage edit is the Technologies line, because employers search the thread the same way you search theirs: with Ctrl+F for specific stack tokens. Eloquence loses to keyword collision.
Compare two versions of the same engineer:
| Version | Technologies line | Result |
|---|---|---|
| Naive | Python, distributed systems, cloud, ML | Invisible to Ctrl+F for "Ray", "Dask", "K8s", "PyTorch" |
| Targeted | Python, Ray, Dask, Kubernetes, HPC, PyTorch, Linux, CI/CD | Matches Proxima Fusion's Aug 4 post verbatim |
Proxima Fusion's Aug 4 stack is literally "K8s, Ray, Dask, CI/CD, IaC, observability, Python and Linux." If your Technologies line contains those tokens, a Proxima engineer skimming candidate posts at lunch will stop on yours. If it says "cloud native, ML infra," they will not.
The mechanism is boring: Ctrl+F does not do synonyms. "K8s" and "Kubernetes" are different strings. Include both. "Postgres" and "PostgreSQL" are different strings. Include both. This is not stuffing, it is the format the channel demands.
Tailoring the Technologies line to the specific companies in the sibling "Who is Hiring?" thread is exactly the kind of grunt work Refolk automates: paste the "Who is Hiring?" comment for Proxima or Anduril, and I rewrite your six-line post and resume to collide with the exact tokens they used.
The hidden supply shock: fewer competitors than you think
The perceived crowdedness of HN is an illusion created by 400 to 800 employer posts, not candidate posts. On the candidate side, the pool of visible, self-declared "open to work" senior engineers is small enough to name.
Refolk's index of Software / Senior / Staff Engineers self-tagging open-to-work in their public headline, across the entire United States.
The supply side, from Refolk's index of professional profiles:
| Segment | Self-signaling "open to work" | Top hub |
|---|---|---|
| U.S. Software / Senior / Staff Engineers | 190 | New York and Seattle (tie, 4 each) |
| Rust + Kubernetes engineers, global | 165 | Bengaluru (4) |
| ML/AI engineers with Python + PyTorch, U.S. | 3 | U.S. (unspecified) |
| Anduril's Aug 2026 HN roles | 16 | Santa Ana, CA (SIG) |
Top current employers of that 190-engineer U.S. pool: AWS (4), Amazon (3), Google (2). That is the entire visible passive-to-active senior-engineer market in the country. A well-written HN post is disproportionately visible against that backdrop.
The ML/AI number is the one to sit with. Only three U.S. engineers currently pair Python, PyTorch, an ML title, and an "open to work" flag in their public headline. The August 2026 thread is stacked with AI-first startups. If you are a competent MLE, you are bidding into an empty market.
Only three U.S. MLEs currently signal open to work with Python, PyTorch, and an ML title. The AI-first HN posters are bidding on an empty room.
Speed of reply beats resume polish
Employers on HN explicitly say candidates go with the first reply. That inverts what a candidate should optimize: not a prettier PDF, but a faster inbox.
Concretely, for the August 2026 thread:
- Post within the first four hours of item 49156682 going live. Top comments compound; late posts stay at the bottom.
- Use a dedicated inbox (a Gmail alias is fine) and check it every hour on Aug 4 and 5. Do not use the address on your resume; you will miss threads inside a shared family inbox.
- Reply to employers within 60 minutes during business hours in their timezone. A 12-hour delay loses to a peer who was three seats down in the thread.
- Ship one paragraph of "why you", not a cover letter. Two sentences on the specific system you built that matches their stack, one sentence on availability, one sentence on comp band.
The "why you" paragraph is the part that eats the most time when you are replying to five employers in an evening. That is exactly what Refolk drafts: paste the employer's HN comment and my draft comes back tuned to their stack and title, with a two-line pitch you can send verbatim or edit in 30 seconds.
The unofficial 7th line: comp band
Adding an unofficial 7th line for salary or day-rate expectations pre-filters out employers who cannot pay you, and it turns a 20-email negotiation into a 2-email yes/no. Employer-side guidance already tells companies that salary ranges build trust and filter mismatched expectations. The same math works for candidates.
Format it as a range, in the currency the employer posts in, and be explicit about base vs. total comp:
Comp: $220-260k base + equity, US remoteComp: €95-115k base, Munich onsite or EU remoteRate: £650-800/day, UK contract, inside or outside IR35
Two effects:
- Founder-led startups self-select in or out in 30 seconds. You stop wasting reply cycles on companies that top out $80k below your floor.
- Serious employers treat your post as more credible, because most candidate posts hide comp and force the employer to guess.
One HN commenter reports an 80 to 90% response rate with a tuned template versus 10 to 20% with a naive one, a 4x to 8x delta. Comp transparency and Ctrl+F collision are the two changes that produce that delta.
A worked example: the 6 lines that would win Aug 2026
Here is a candidate post targeting Proxima Fusion, Anduril, and the AI-first cohort on the same day the thread opens. Copy the shape, not the specifics.
Location: Austin, TX, USA
Remote: Yes (US or EU timezones), or hybrid in Austin
Willing to relocate: Yes - Munich, Santa Ana CA, Boulder, Berkeley
Technologies: Python, Rust, Ray, Dask, Kubernetes (K8s), PyTorch, CUDA, Linux, Postgres, Terraform, CI/CD, HPC, distributed systems, observability
Résumé/CV: https://[yourdomain].com/resume.pdf
Email: hn-aug26@[yourdomain].com
Comp: $210-250k base + equity, or €95-115k base in EU
Why this works, line by line:
- Location names both city and country; a Munich engineer scanning for US candidates who might relocate does not need to guess.
- Remote specifies timezones, which is the actual constraint employers care about.
- Willing to relocate names the exact cities the top employers in the sibling thread operate in. Anduril reads "Santa Ana" and stops.
- Technologies contains "K8s" and "Kubernetes" (both strings), "Ray" and "Dask" (Proxima's exact tokens), "PyTorch" and "CUDA" (the AI cohort), and "Rust" (the systems cohort). Fourteen tokens, all Ctrl+F targets.
- CV is a stable URL on your own domain, not a shortener, not a Doc.
- Email is a dedicated alias, not personal, easy to filter and archive after the month closes.
- Comp ranges in both currencies you are willing to be paid in, pre-filtering the employer pool.
If assembling that post from your existing history feels like more work than it should be, that is the exact seam Refolk fills. Paste the six-field template plus the three or four "Who is Hiring?" comments you actually care about, and I return a candidate post with the right tokens, plus a tailored resume PDF and a cover letter for each employer, scored against how well you actually fit.
The tools worth using this weekend
Two sites turn the HN threads into searchable databases and cost nothing:
- hnhiring.com aggregates every "Who is Hiring?" thread by month, company, technology, and location. Search "august-2026" plus your stack tokens to build your Ctrl+F target list before you post.
- hn.algolia.com searches past "Who wants to be hired?" threads for template exemplars. Search for engineers in your stack who posted three to twelve months ago, then look at which of their lines survived.
Use both before you write your six lines. The candidate posts that get replies almost always share structural DNA with a post from three months earlier that also got replies.
FAQ
When exactly does the August 2026 HN "Who wants to be hired?" thread go live?
Item 49156682 posted on Aug 4, 2026, alongside the "Who is Hiring? (August 2026)" thread (item 49156683). Both stay open through the month, but top-level ordering favors posts made in the first four hours. If you are reading this after Aug 4, post anyway; late posts still get replies, just fewer, and the comp-band line matters more when you are further down the page.
How is "Who wants to be hired?" different from "Who is Hiring?" on HN?
"Who is Hiring?" is the employer thread: one top-level comment per company, with an explain-what-you-do requirement for non-household names. "Who wants to be hired?" is the candidate thread with the six-field template (Location, Remote, Willing to relocate, Technologies, Résumé/CV, Email), and the rule that only individuals looking for work can post. Recruiters, agencies, and job boards are off-topic in both. You want to post in the candidate thread and reply in the employer thread.
What response rate should I expect from an HN candidate post?
The public data point on the employer side is 170 responses producing 3 offers, a 1.8% offer rate per response. On the candidate side, one HN commenter reports an 80 to 90% response rate with a tuned template versus 10 to 20% with a naive one, a 4x to 8x delta driven almost entirely by keyword collision and comp transparency. Expect five to fifteen employer emails in the first week if your Technologies line matches the stacks employers actually posted that month.
Should I still send my resume through the company's ATS if they reply on HN?
No. If a founder or engineering manager emails you off an HN post, keep the conversation in email until you have a scheduled call. Routing back through the ATS restarts the clock, drops you into a reviewer queue that has never seen your HN post, and often triggers automated screening on the resume PDF alone. The whole point of the channel is that you skipped the ATS. Do not walk back into it.