# HN's Hiring Thread Fell to 244 Posts. 11 Mention Junior. Be the 12th

_HN's Who is Hiring thread fell to 244 posts in November 2026. Half mention AI, 3% say junior. How to post the gap and source from Who wants to be hired._

- Canonical URL: https://www.refolk.ai/blog/hn-who-is-hiring-november-2026-post-the-gap
- Published: 2026-11-17
- Reading time: 8 min
- Keywords: Hacker News who is hiring, HN who is hiring November 2026, how to post on HN who is hiring, hire engineers from Hacker News, who wants to be hired HN

If you're deciding whether to post in Hacker News' "Who is Hiring?" thread this month, the headline number looks bad: the thread is at a 12-year low. Read it differently. A smaller thread where most posts say the same thing gives you less competition, as long as your post names what the others leave out.

## Is the Hacker News "Who is Hiring?" thread still worth posting in?

Yes. It's arguably worth more per post than it was a year ago, because there are fewer posts competing for the same readers. As of November 14, the thread had 244 postings, down 37% from 387 at the same point in 2025.

The decline has been steady, not a one-off:

- Every thread since July 2026 has landed between 224 and 255 postings.
- August's 224 was the fewest since January 2014.
- 2026 is averaging 287 postings a month, the lowest yearly average since 2013.

> **37%** Drop in HN "Who is Hiring?" postings, November 2025 to November 2026
>
> 387 postings a year ago, 244 as of November 14, per HNTrends.

The channel still produces hires. One November poster wrote that they had already hired two backend developers through "HN - Who is hiring?" and were back to recruit an Engineering Manager (Ruby on Rails).

## What does HN Who is Hiring look like in November 2026?

It's remote-first, heavy on AI, and top-heavy on seniority. Half the posts mention AI, Staff roles keep growing, and junior roles have almost disappeared. HNTrends' numbers (some are three-month averages) show how similar the posts have become:

- **AI** appears in 51.6% of postings, second only to Remote.
- **AI agents** (including "agentic") appear in 14.8%, ahead of LLMs at 10.7%.
- **MCP** (Model Context Protocol) went from 0.3% to 4.5% in a year.
- **Remote** is in 55.7% of postings, **Onsite** in 26.2%, **Hybrid** in 17.2%. All three are within two points of last November.
- **Senior** has held around 30% for years. **Staff** has roughly quadrupled since 2019 to about 12%. **Junior** sits around 3%.
- **Front End** has fallen further than any other role label, from 27% of postings in early 2022 to 6.6% now.

A separate Show HN analysis of eight years of threads found the same pattern from the other direction. Posts naming staff-level roles rose from 77 in 2019 to 277 in 2026 while the board shrank. Only 41 of 2,932 posts in 2026 explicitly named junior roles, against 163 in 2019.

Copying the thread's dominant vocabulary feels safe. On a board where every post sounds the same, the safe choice is the one readers skip.

## Where does the demand pile up compared with the people who can fill it?

Demand is concentrated where the candidate pool is smallest. The thread's fastest-growing keyword, MCP, has the fewest people behind each post, while junior roles have the most. To check this, I compared November's posting shares with current US profiles in Refolk's index of professional profiles.

| Segment | Share of HN Nov posts | Approx. Nov posts | US profiles (Refolk index) | Profiles per post |
|---|---|---|---|---|
| Junior / Associate / SWE I | ~3% | 11 | 14,332 | ~1,300 |
| Staff | ~12% | ~29 | 50,826 | ~1,750 |
| MCP skill | 4.5% | ~11 | 645 | ~59 |

Post counts are derived from the 244 total. Profile counts are US-only, based on current titles and self-listed skills.

> **~59** US profiles listing MCP as a skill, per HN post asking for it
>
> 645 profiles in Refolk's index against roughly 11 November posts. Junior posts have about 1,300 each.

That works out to roughly 22 times more candidates per junior post than per MCP post. If you add "agentic/MCP" to your post because everyone else did, you're competing with about 11 other posts for a few hundred people.

One caveat: MCP is a self-listed skill, so 645 is a floor, not a census. Anyone who has done the work without typing the acronym into a profile won't show up in a keyword search. In [Refolk](/), you can describe the person, for example "built an MCP server, public repo, US-based", and search across their public work, not only the 645 who listed the skill.

## Why is the junior gap about attention, not supply?

Junior candidates aren't hugely over-supplied compared with Staff. The difference is visibility. Very few posts ask for juniors, so a junior post faces almost no competition from other junior posts.

Compare the ratios:

- **Demand in the thread:** Staff outnumbers Junior about 4 to 1 (12% vs 3%).
- **US supply:** 50,826 Staff profiles vs 14,332 Junior, Associate, and SWE I profiles, about 3.5 to 1.

Those ratios are close. Juniors aren't drowning because there are too many of them. They're drowning because there's nowhere to look. A new grad scanning the thread finds about a dozen posts. A Staff engineer finds about 29 that match their level, plus Senior posts making up roughly 30% of the thread.

There's also some movement. Junior went from 7 of 387 posts last November (1.8%) to 11 of 244 (4.5%). Four extra posts is a small change, so treat it as a signal rather than a trend. Still, fewer than a dozen employers are competing for a pool of more than 14,000 people.

The same logic applies to work location. Onsite appears in 26% of posts against 56% for remote. A reader looking specifically for an onsite role sees far fewer options, so an onsite post faces less competition.

The 14,332 junior profiles aren't spread evenly. The biggest employers in that group include Capital One, Goldman Sachs, ServiceNow, and Bubble, which gives you a concrete place to start looking before your post goes up.

> **Example search:** "Find US software engineers with Junior, Associate, or Engineer I titles at Capital One, Goldman Sachs, ServiceNow, or Bubble who have public GitHub projects in Go, Rust, or C++." - [run it on Refolk](https://www.refolk.ai/start?q=Find%20US%20software%20engineers%20with%20Junior%2C%20Associate%2C%20or%20Engineer%20I%20titles%20at%20Capital%20One%2C%20Goldman%20Sachs%2C%20ServiceNow%2C%20or%20Bubble%20who%20have%20public%20GitHub%20projects%20in%20Go%2C%20Rust%2C%20or%20C%2B%2B.)
>
> A ranked shortlist of early-career engineers with linked GitHub and LinkedIn profiles, ready to message before your HN post goes up.

## How to post on HN Who is Hiring so your post stands out

Put the thing the other 243 posts don't say in your first line. Readers skim the header, so it has to say why your post is different, and the posts that stand out this month use it to show something the rest of the thread lacks.

Before you write, look at what other employers are advertising for the level you're hiring. That's your competition, even outside HN.

> **Entry-level engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&seniority=entry)
>
> Other employers hiring at the junior level, for comparison with your HN post.

Then write the post:

1. **Name the gap in the header.** If you hire juniors, write "Junior" or "New grad" in the role field. Don't bury it as "all levels" in paragraph three.
2. **Say onsite plainly if it's onsite.** Thunder Compute (YC S24) is hiring a C++ systems engineer, onsite in SF, with visa sponsorship. That's three uncommon traits in one line: non-AI systems work, onsite, and visa sponsorship.
3. **Publish the salary band.** Fly.io's remote role lists $190k USD plus equity. Nirvana Robotics writes `New York, NY | ONSITE | Full-time | $220K-$300K` for mechanical, electrical, and controls engineers, hardware work in a thread dominated by AI.
4. **Describe the work, not the buzzword.** If your product uses an LLM but the job is Postgres replication, say Postgres replication. Half the thread already says "AI". Nobody else is writing about your replication lag.
5. **Use Front End if that's the job.** At 6.6% of postings, it's no longer a crowded label.
6. **Post every month.** The next section explains why this matters most.

> Half the thread already says AI. Nobody else is writing about your replication lag.

## Why do 53% of employers disappear after one month?

Most employers post once and never follow up, so the channel never gets a fair test. Across all 94 monthly threads in the eight-year Show HN analysis, 53% of identified employers appeared in only one month.

The mechanism is simple. A single post goes up whenever someone happens to remember the thread, nobody reads the candidate thread that month, and nobody posts again the next. That's a single try, not a process.

Hiring through HN works like any sourcing channel: results come from showing up every month and reaching out yourself. On a small team where nobody has time to post monthly and read every candidate comment, that's exactly the work that gets dropped, and the role stays open while the team decides the channel is dead.

## How do you hire engineers from Hacker News through "Who wants to be hired?"

Read the candidate thread before you write your post, and message the people who fit. In "Who wants to be hired?", experienced engineers say publicly that they're looking, and there are now more of them than there are companies posting jobs.

The numbers have flipped:

- "Who wants to be hired?" grew from 384 posts in April to 553 in September (+44%), about 2.2 candidates for every hiring company.
- An early-November scraper run counted 504 candidate posts against 205 hiring posts, about 2.5 to 1.
- Averaged over January to July, 2021 had 961 hiring comments a month against 219 from job seekers. In 2026 it's 488 against 502.
- 57% to 63% of candidates describe themselves as senior or above, with a median of 10 years' experience when they state it.

Most of LinkedIn won't show you who's actively looking. These people put it in writing. In the November thread (item 50338726), one poster said their acquired six-person team wants to find a new home together. A founder could hire a whole working team from one comment.

A workable monthly routine:

1. **Day the thread opens:** Post your hiring comment early, with the gap in the header.
2. **Same week:** Read "Who wants to be hired?" from the top and shortlist anyone whose stack and location fit.
3. **Check before messaging:** Candidate comments are brief. Look at their public work and recent roles so your first message mentions something real.
4. **Message within 48 hours:** Speed and specificity beat a polished but generic message.
5. **Repeat next month.** Some candidates who passed in November will be ready in December.

## FAQ

### Should I mention AI in my HN Who is Hiring post?

Only if the job is actually AI work. AI appears in 51.6% of November 2026 postings, so the word no longer sets you apart. If your role is AI-adjacent but mostly systems, data, or front-end work, describe that work. You'll stand out more, and you won't be competing with the roughly 11 MCP posts for the 645 US profiles that list the skill.

### Is "Who wants to be hired?" on HN full of junior candidates?

No. Between 57% and 63% of candidates describe themselves as senior or above, with a median of 10 years' experience when stated. The candidate thread is a good source for senior and Staff roles, and since it now has about 2.2 to 2.5 candidates per hiring company, sending messages yourself usually beats waiting for applications.

### How long should I post before deciding HN doesn't work?

Several consecutive months, with direct messages in the candidate thread each time. 53% of employers in eight years of threads posted only once, and that's the main reason the channel seems not to work for them. Employers who keep showing up, like the November poster who had already made two backend hires, are the ones who get results.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_
