Your reply to a Hacker News "Who is Hiring?" post often goes straight to a founder's inbox, so that short email has to work as your resume, your cover letter, and your first screen. It's also competing harder than it used to, because fewer companies are posting and more engineers are replying.
As of November 14, HN Trends counted 244 postings in November's thread. A year earlier it was 387, so that's down 37%.
How small is Hacker News Who Is Hiring in November 2026?
It's the smallest it has been in more than a decade. November had 244 postings as of the 14th, and 2026 is averaging 287 postings a month, the lowest yearly average since 2013. Every thread since July has landed between 224 and 255 postings. August's 224 was the lowest count since January 2014.
HN Trends (hntrends.com) tracks the thread month by month, and it recently started updating again after a gap of two and a half years.
The mix of postings has changed along with the volume:
- AI appears in 51.6% of postings, up from 30% two years ago.
- "AI agents" / "agentic" is in 14.8% of postings, ahead of "LLMs" at 10.7%.
- MCP went from 0.3% to 4.5% in a year, the biggest climb this month.
- Full Stack fell from 26.2% to 20.1%, and Back End from 23.6% to 18.8%.
Everything else in this piece follows from that. The thread is smaller, agent and tooling language is rising, and generic full-stack and back-end postings make up less of it. If your reply reads like a generic web-engineer pitch, it's aimed at a shrinking share of postings.
Down 37% from 387 at the same point last year, per HN Trends.
Fewer posts means more competition per post
Each posting now draws roughly twice the competition it did a year ago. Company posts fell by about a third while the number of engineers advertising themselves rose by about 44%.
An independent analysis of the thread put the numbers side by side:
| Metric | Earlier | Later |
|---|---|---|
| Company posts per month | ~361 (Q4 2025) | ~240 (Q3 2026) |
| "Who wants to be hired?" posts | 384 (April) | 553 (September) |
| Candidates per hiring company | 2.2 | 2.6 (early October) |
"Who wants to be hired?" is the companion thread where job seekers post their own short profiles. It only covers some of the people replying to postings, since plenty of engineers reply without ever posting there. Still, it shows how crowded the candidate side has become.
The competition is also concentrated in specific places:
- Remote is oversubscribed. 50% to 55% of candidates want remote-only work, but only 33% to 42% of roles are remote-only.
- Seniority is crowded. 57% to 63% of candidates call themselves senior or above.
- Junior roles are scarce. Junior and intern roles make up just 2% to 5% of postings. If you're early-career, treat the thread as a side channel, not your main one.
The usual reaction to a thin market is to send more. You reply to every posting that's close, paste the same paragraph each time, and hear nothing back. Sending more emails into a smaller, more crowded thread mostly gets you more silence.
What works is fit. When 244 companies are reading replies from a growing pool of senior engineers, the email that gets an answer is the one that was obviously written for that specific posting.
The email is the resume: what posters actually ask for
Many posters say directly that they want a short, self-contained email that shows something you built, names the role, and mentions HN. Some say plainly that they don't want AI-written text.
Here is what they've written in the thread:
- January 2025: "Make the email self-contained; no need for resume / the mail is the resume."
- vlm.run, October: "No AI text please, keep it short, shorter emails are more likely to get a response."
- A November poster complained that applicants repeat the job ad back to them: "Leave your AI off for 10 minutes, and give us those spelling mistakes!"
- MiLaboratories CEO Stan P. has asked for months that applicants put "HN" in the subject line and include their GitHub, and says he replies personally.
- Pond, Mesmer, Lumen Research, and BuildQ asked candidates in November to email "something you've built," mention HN, and name the role. BuildQ wants "HN Founding Engineer" in the subject.
Most of these "rules" come down to one thing. A person reads your email, and that person is often someone you'd be working with. In this thread there's often no applicant tracking system (ATS) filtering applications on the way in, so keyword stuffing does nothing and padding gets noticed right away.
In this thread the ATS is often the founder you'd be working with. Write for that person.
Not every posting goes to an inbox, though. Common Prefix (Athens or remote, $80k to $160k) says it only reviews applications submitted through its form, not by email. Many other postings link straight to Ashby or Greenhouse. Read the last line of the posting before you write anything. If it names a form, use the form, and expect your resume to be parsed the way it would be anywhere else.
How to reply to a Who Is Hiring post in 6 to 10 lines
A strong reply fits on one screen. It states your location fit first, names the role, points to one thing you built that matches their stack, backs it with one number you can source, and links to proof. That's the whole template.
- Subject line: "HN" + role + location fit. Example: "HN: Founding Engineer, Bay Area, onsite OK."
- Line 1, work arrangement: where you are and what you'll accept (remote, onsite, hybrid, time zone).
- Line 2, the role and one detail from the posting: show that you read it. Mention a single specific detail, not a summary of the ad.
- Lines 3 to 5, one matched project: what you built, in their vocabulary, with one number you can defend if they ask about it.
- Line 6, the link: GitHub, a demo, a write-up. Posters keep asking for "something you've built."
- Line 7, the close: availability and a plain ask for a call.
A skeleton, with placeholders where your real facts go:
Subject: HN: Senior Backend Engineer, remote (US Eastern)
Hi [name], I'm in [city], remote-only, and can overlap with your Pacific hours.
Your post mentions [specific detail, e.g. "agents that file tickets from support chats"]. I built close to that at [company]: [one sentence on the system, in the posting's terms].
It handled [your real number, from a dashboard or report you can point to].
Code and write-up: [link]. Free for a call [days].
The format is the easy part. The hard part is picking which project and which number fit this particular posting, then doing it all again for the next one. That's the work Refolk takes off your hands. Paste the posting, and Refolk rewrites your resume from your own history to match it and drafts a cover letter, which you then cut down to these few lines. You keep the selection and the facts and throw out the padding.
Lead with location: why line one is remote or onsite
Put your work arrangement in the first line, because it's the first filter a founder applies and it's where the most candidates fail. In November, HN Trends tagged 55.7% of postings Remote, 26.2% Onsite, and 17.2% Hybrid, all within two points of last November.
Meanwhile, half of candidates want remote-only work, but at most 42% of roles are remote-only in the independent count. The gap between HN Trends' 55.7% and that 42% is likely the difference between postings that mention remote and postings that are remote-only. Some onsite posters are strict about it. vlm.run puts "Bay Area only" in the subject line itself.
That cuts both ways:
- If you're remote-only, say so up front so the founder doesn't read eight lines before finding the dealbreaker. hnhiring.com lets you filter the thread by remote and by month, so you can skip postings that were never going to fit.
- If you'll go onsite or hybrid, that's an edge. You're competing with fewer people for the 26.2% of postings that are onsite. Put the city in the subject.
Postings say agents. Your profile says LLM.
Postings now use "AI agents" or "agentic" more than "LLM," while US software engineers still describe themselves with "LLM" far more often. In Refolk's index of professional profiles, 3,470 US Software Engineer headlines mention LLM and only 769 mention "AI agents."
An AI agent here means an LLM-driven system that calls tools, takes actions, and loops on the results instead of returning a single answer.
| Term | % of Nov HN postings | US SWE profiles mentioning it (Refolk's index) |
|---|---|---|
| AI agents / agentic | 14.8% | 769 |
| LLM | 10.7% | 3,470 |
| MCP (Model Context Protocol) | 4.5% | 873 (likely inflated) |
| Agents ÷ LLM ratio | 1.38× | 0.22× |
Divide one ratio by the other and postings lean toward "agents" about 6.3 times more than engineer profiles do.
1.38x in postings vs 0.22x in Refolk's index of US Software Engineer headlines.
A few details from the index:
- The MCP count is an upper bound. The top employers among the 873 matches include Apple (4), Ford (2), Fidelity, and AmEx. That pattern suggests many matches are the old "Microsoft Certified Professional," not Model Context Protocol.
- Agent-language engineers cluster differently. In a 25-profile sample of the "AI agents" set, Google is the most common employer (4 of 25), and New York (5) shows up more than the Bay Area (3). In the LLM set, Meta leads.
Profiles lag behind the work. The systems many engineers built around an LLM turned into tool-calling pipelines, but the headline still says "LLM." Founders write postings in the newer vocabulary, and they're matching phrases, not decoding them.
How to claim AI agents experience without overclaiming
If you built tool-calling, retries, or evals around an LLM, you've done agent work. Use the posting's word once, describe what the system actually did, and link to it. If you only called a completion endpoint, don't call it agents.
One November job seeker in "Who wants to be hired?" got it right: "sole AI engineer, built the company's AI system (RAG, tool-calling agents)." That's one label, then the concrete pieces in parentheses, with no adjectives.
Check yourself before you write "agentic":
- Did the model choose and call tools (APIs, search, code execution), or did your code decide every step?
- Did it loop? Retries, re-planning, or multi-step tasks count. A single prompt and response doesn't.
- Did you evaluate it? Evals, failure tracking, or guardrails show you ran it as a system.
- Can you show it? A repo, a demo, or a write-up the founder can open in one click.
- Can you defend the number? Assume the founder asks where it came from on the first call.
Overclaiming in this thread gets caught, because the reader is often the engineer who would review your code. Expect a question like how you handled a failed tool call, and a reworded LLM wrapper can't answer it. Posters are also telling you they notice when the ad gets pasted back to them. Use their term once, attach one artifact, and stop.
Before you send, check how well you actually match. Refolk scores your fit against each posting from your real history, so you can see where your agent claim is thin before a founder does. Then either back it with a real example or skip that posting and spend the reply on one where you match better.
FAQ
Do I need to attach a resume when replying to a Who Is Hiring post?
Usually not, unless the posting asks for one. At least one poster has said outright that "the mail is the resume," and several want short, self-contained emails. Put the essentials in the body (location fit, one matched project, one sourced number, one link) and offer to send a full resume if they want it. If the posting points to a form, Ashby, or Greenhouse, use that route and attach a tailored resume there.
Should I put "HN" in the subject line?
Yes, when the posting asks for it, and many do. MiLaboratories' CEO has asked for "HN" in the subject for months, and BuildQ wants "HN Founding Engineer." Even when it isn't required, "HN" plus the role plus your location fit tells the founder in one line where you came from and whether you match their setup.
Is it OK to use AI to write the reply?
Use it to find your best matching project, not to write the sentences. Posters including vlm.run have asked for no AI text, and a November poster complained about applicants repeating the job ad back to them. The reader is a person who notices generic phrasing. Write the final few lines yourself, in plain language, with one real number.
How do I list AI agents experience on a resume if my title says LLM engineer?
Describe the system, not the title. If your work involved tool-calling, retries, multi-step tasks, or evals, you can call it agent work, then list the concrete pieces, as in "RAG, tool-calling agents." In Refolk's index, US engineer headlines say "LLM" about 4.5 times more often than "AI agents," while 14.8% of November postings use agent language. Using their word is fine as long as the work behind it is real.