# Only 1 in 2,740 US Engineers Says 'Open to Work.' Read HN Before December

_How to source engineers from Hacker News's November 2026 Who Wants to Be Hired thread: parse posts, verify GitHub claims, and email before December._

- Canonical URL: https://www.refolk.ai/blog/hacker-news-who-wants-to-be-hired-november-2026-sourcing
- Published: 2026-11-04
- Reading time: 9 min
- Keywords: hacker news who wants to be hired, ask hn who is hiring november 2026, source engineers from hacker news, hn hiring thread candidates, find developers open to work

If you need an engineer who has actually said they want a job, a profile search mostly comes back empty, because almost nobody says it where their employer can see. The November 2026 "Ask HN: Who wants to be hired?" thread (item 50338726) is the exception: a list of engineers saying it in their own words, and it starts losing value as soon as December's thread replaces it.

The thread went up on Nov 2 to 3, next to its "Who is hiring?" companion (item 50338728). The same day, a resurfaced Bloomberg story about jobless San Francisco tech workers reached the front page, citing a 42% drop in Bay Area software-engineer demand since 2022. The pool is big right now, and the window is short.

## Why is the HN thread worth more than a profile search?

The HN thread is one of the few places where engineers state publicly, in their own words, that they want a job. On mainstream professional networks almost nobody does.

In Refolk's index of professional profiles, 353,400 people in the US hold the title "Software Engineer." Only 129 of them put "open to work" in their headline. That works out to about 1 in 2,740. In the UK the count is 4, and one of those four is actually a digital marketing executive.

| Segment | Count | Source |
|---|---|---|
| US "Software Engineer" (all) | 353,400 | Refolk's index |
| US SWEs with "open to work" in headline | 129 | Refolk's index |
| UK SWEs with "open to work" in headline | 4 | Refolk's index |
| Share of US SWEs saying it in headline | ~0.04% | 129 ÷ 353,400 |
| US vs UK headline count | ~32x | 129 ÷ 4 |
| Bay Area SWE demand since 2022 | -42% | Lightcast via Bloomberg |

One caveat: this is a keyword match on headlines. It doesn't capture a platform's private open-to-work setting or its green photo frame. It measures who says it out loud, not everyone who is looking.

> **1 in 2,740** US software engineers who say "open to work" in their headline
>
> 129 of 353,400 in Refolk's index of professional profiles.

### Why engineers stay quiet everywhere else

The likely reason is reputational risk. Your current employer and your future employers all read the same professional network, and a headline there is a signal you can't take back. An HN post costs less. It often comes from a pseudonymous handle, and it is buried within a month. When saying it costs less, more people say it, so one thread ends up holding an opt-in list that would be very hard to build anywhere else.

Look at the few who do announce it on their profiles. The most common current employers among the 129 are Amazon/AWS (4 in total), then Google, Oracle, Bank of America, AT&T, Uber, Notion and Walmart Global Tech. These are big-company engineers who are comfortable being seen on the market. Most of their peers aren't.

## Why is the November pool so large?

The pool is large because Bay Area demand for generalist software engineers has fallen sharply while AI work has grown, which leaves many experienced engineers between roles. The figures come from Francesca Maglione's Bloomberg story, which first ran around Sept 17 and returned to HN as item 50337454 under the title "Jobless tech workers are being left out of San Francisco's AI boom."

- **-42%:** Bay Area software-engineer demand since 2022, per Lightcast.
- **+37%:** AI-related IT and CS jobs over the same period.
- **14,500+:** Bay Area workers covered by tech layoff notices in the 12 months to June, nearly double the year before.
- **~600%:** growth in Bay Area forward deployed engineer postings since 2022, at a median advertised salary of $202,300.
- **~20:** OpenAI FDE postings, at $145K to $325K plus equity.

The non-obvious part is that the 42% describes a change in which roles are wanted, not only a drop in how many. You can see the same split in the November threads. Candidates label themselves "AI engineer," "agents" or "RAG." Meanwhile one hiring post asks for a hands-on engineer who has shipped LLM agents to production and names Strands, LangChain, Agno, Google ADK and the Claude Agent SDK. Anyone can add the label. What separates candidates is whether they have actually shipped that work, and that is where you should filter.

> **Remote engineering roles open right now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&remote=1)
>
> The HN thread format leads with Location and Remote, so this is the slice most posts are sorting themselves into.

## What do the thread's rules let recruiters do?

Recruiters can read the thread and email posters about work. They can't post, and they shouldn't email about anything other than a real opportunity. The rules are written at the top of the thread:

- "Please only post if you are personally looking for work."
- "Readers: please only email these addresses to discuss work opportunities."
- Earlier 2026 threads (such as item 47975570) added: "Agencies, recruiters, job boards, and so on, are off topic here."

In practice, that means:

1. Don't reply in the thread with a pitch. Use email.
2. Email only the address the person posted.
3. Pitch one specific role per email.
4. Never add a poster to a newsletter, talent community, CRM drip or automated sequence.

HN readers are known for calling out recruiters who break these rules, and they do it in public. One screenshot of a mass sequence sent to thread addresses can damage your reputation with every engineer who reads it.

## How do you turn a post into a shortlist row?

Break each post into the fields the thread asks for, then add the three it doesn't ask for: notice period, work authorization and an evidence link. The requested format is Location / Remote / Willing to relocate / Technologies / Email, and many posts include more than that.

| Field | Example from November posts | What it decides |
|---|---|---|
| Location / Remote | City or "Remote" | Whether the role is even possible |
| Technologies | "Full-stack and AI engineer" | First-pass match only |
| Notice period | "28-day notice" | Earliest realistic start |
| Work authorization | "F-1 OPT (STEM OPT eligible)" | Whether you need a visa plan |
| Evidence link | GitHub repo, e.g. an OWASP LLM red-team suite | What you will verify next |

Two free tools help with the first pass: **hnhiring.com** and **nchelluri's hnjobs filter** (nchelluri.github.io/hnjobs) both parse the threads. Use them. Just remember that they only report what each person wrote. They don't check whether "five years of Go" matches any Go anyone can see.

Notice periods also tell you something about the person. Someone on a "28-day notice" is still employed and has a fixed exit date, so your offer has to arrive before a counteroffer does. Someone who lists no notice period may be between jobs, possibly one of the 14,500+ covered by Bay Area layoff notices, and the timing conversation is different. Record which one you are having.

Doing this by hand for one hard-to-fill role means reading every top-level post, opening every repo, cross-checking handles and building a sheet, all while the thread drops further down the page. A recruiter with four other open roles can lose most of the month to a channel that only lasts a month.

## How do you check a claim against real commits?

Open the linked repo and confirm three things: the poster wrote the commits, the commits are recent, and the code matches the stack and seniority they claimed. Do this before you write a word of outreach.

1. **Authorship.** The commits should be under their handle. A fork with one README edit is not evidence.
2. **Recency.** Look for activity in recent months, not one burst from years ago.
3. **Stack match.** The repo's languages and dependencies should match what they listed under "Technologies."
4. **Depth for the level claimed.** For a "1 YOE, 28-day notice" post, look for a finished project, tests and readable commits. For a "10 years distributed systems" post, look for design decisions in issues, review comments in other people's repos and tradeoffs explained in writing.
5. **Agent claims.** If they say they've shipped agents, check that the code uses a real framework, handles failures and evaluates outputs, rather than wrapping a single API call.

The OWASP LLM red-team suite mentioned in one November post is a good example of a checkable claim. Either the repo has test cases mapped to real attack categories and a runner that executes them, or it doesn't. Ten minutes in the code tells you more than the post's adjective list.

The hard part is usually connecting identities. One post has a GitHub link but no name. Another has an email and no code. Matching a handle to the rest of someone's public footprint is the step where [Refolk](/) saves the most time: you describe the person in plain English and get back their GitHub, LinkedIn and open-web profiles together, so the claim and the evidence are on one screen.

> **Example search:** "Engineers in the US who have shipped LLM agents to production with LangChain or the Claude Agent SDK, with recent GitHub commits, open to remote work." - [run it on Refolk](https://www.refolk.ai/s/m27g88n2y9)
>
> A ranked shortlist with each person's GitHub, LinkedIn and web profiles linked, so you can check the commits before you email.

## Why does the clock matter so much?

A November post shows who was available in early November. Once the December thread goes up around Dec 1, the November posts get buried, and people who find jobs rarely go back and edit their posts.

So the opt-in loses value on a fixed schedule. Work the thread like this:

- **Week one (Nov 3 to 9):** Parse, verify and send the first email to your strongest matches.
- **Weeks two and three:** Send one follow-up to anyone who hasn't replied. Then stop.
- **Around Dec 1:** Open the December thread and compare. People who post again are still looking, so that is your warmest follow-up. People who don't post again may have been hired, so check before you send another email.

That repost check costs nothing. Two consecutive posts tell you more about someone's availability than any profile setting.

> A November post shows who was available in early November. Treat it as perishable.

## How should the first email read?

Write one email per person that mentions their post, names the role, salary range and location, and explains why their code made you write. If it could go to anyone else on the thread unchanged, rewrite it.

A working skeleton:

> Subject: Your HN post, [role] at [company]
>
> Saw your post in November's Who Wants to Be Hired. Your [repo] caught my eye, specifically [one concrete thing in the code]. I'm hiring a [title], [remote/location], [salary range]. Your 28-day notice fits the timeline for this role. Worth a 20-minute call this week?

Include these five things in every email:

- The thread and month, so they know where you found them.
- One specific detail from their repo that proves you read the code.
- The title, location or remote status, and salary range.
- How their notice period or work authorization fits your timeline.
- One clear next step.

The channel works when you treat it as a conversation about work. The CTO of AREO, a company in Bremen, posted in November that the company had "already hired two backend developers through 'HN - Who is hiring?'" and is back to hire a Rails engineering manager. Better Stack is in the same thread looking for full-stack product engineers. The hires come from people who use the thread for what it is for.

## FAQ

### Can recruiters post in Hacker News's "Who wants to be hired?" thread?

No. The thread asks people to post only if they are personally looking for work, and earlier 2026 threads said agencies, recruiters and job boards are off topic. Recruiters can read the thread and email posters about real work opportunities. Companies hiring directly can post in the separate "Who is hiring?" thread, which for November 2026 is item 50338728.

### Is it acceptable to add HN candidates to an outreach sequence?

No. The thread says to email posters only to discuss work opportunities. Newsletters, talent communities and automated drips break that rule, and HN readers tend to call it out publicly. Send one specific email about one role, mention their post, and follow up once at most.

### How do I find developers open to work outside the HN thread?

Expect to dig. In Refolk's index, only 129 of 353,400 US software engineers say "open to work" in their headline, so headline searches miss nearly everyone. A better approach is to search for the evidence (recent commits in the stack you need, shipped projects, a recent move away from a downsizing employer), then confirm interest in the first message.

---

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