# Rust Beat Go in 4 of 5 HN Threads. Only 29 of 3,753 Profiles Say Rust

_Rust hit 8.2% of HN hiring posts, yet only 29 of 3,753 Rust-skilled US profiles say Rust in the title. Find Rust engineers through crates.io and commits._

- Canonical URL: https://www.refolk.ai/blog/hire-rust-developers-crates-io-sourcing
- Published: 2026-11-17
- Reading time: 9 min
- Keywords: hire rust developers, how to find rust engineers, rust developer recruiting, source rust developers github, rust engineer sourcing

If you need to hire Rust developers, a title search will show you under 1% of them. In Refolk's index, only 29 of 3,753 US profiles with the Rust skill put Rust in their current title, and demand for those people is holding up while the rest of the hiring market shrinks.

As of November 14, 2026, November's HN "Who is Hiring?" thread had 244 postings, down 37% from 387 at the same point a year earlier, according to hntrends.com, which had just posted its first update in two and a half years. Rust climbed to #3 at 8.2% of postings. The people who can fill those roles mostly don't say "Rust" anywhere a title search can see it, so you have to find them through their code: crates.io ownership, reverse dependencies and commit history.

## Why did Rust's share of HN hiring posts jump while the thread shrank?

Rust's share rose because the number of Rust postings held steady while everything else fell. Roughly 19 Rust postings in November 2025 (4.9% of 387) became roughly 20 in November 2026 (8.2% of 244), while the thread as a whole lost 143 postings.

That is a different story from "Rust is booming." It means Rust employers kept hiring through a downturn that made other companies stop. And it isn't a one-month blip. Every thread since July landed between 224 and 255 postings, and August's 224 was the fewest since January 2014.

Here is where Rust now sits in the November thread:

- **Python:** 22.1% of postings
- **TypeScript:** 17.6%
- **Rust:** 8.2%, ahead of Go in four of the last five months

The mechanism matters for recruiters. When the total market shrinks and one segment holds, the companies in that segment end up competing for the same small pool of people. Sticky demand plus thin supply is the setup for long searches. So the question isn't whether Rust roles exist. It's where the people are.

## Why does title search miss more than 99% of Rust engineers?

Title search fails because Rust engineers almost never put the language in their title. In Refolk's index of professional profiles, 3,753 US profiles list Rust as a skill, but only 29 have "Rust Engineer," "Rust Developer," or "Rust Software Engineer" as their current title.

> **1 in 129** Rust-skilled US profiles with "Rust" in their current job title
>
> 29 of 3,753 profiles in Refolk's index, so a title search sees under 1% of the supply.

The sample explains why. In a 25-profile sample of those 3,753 Rust-skilled US profiles, the titles were senior or founder-level:

- Co-founder & CTO
- Distinguished Engineer
- Director of Engineering
- VP Engineering
- Chief Architect

None of them said "Rust engineer." Their employers included Kraken, NVIDIA, Temporal Technologies and Footprint. At that level, a title names the job level, not the language. A Distinguished Engineer who writes Rust every day has no reason to put "Rust" in a headline.

The 29 people who do carry a Rust title cluster in a narrow band: crypto, defense and automotive employers such as WalletConnect, Figment, L3Harris, Toyota Connected and Amazon. So a Boolean search for "Rust Engineer" returns a skewed slice. It shows you mostly crypto and contractor profiles and misses the senior people sitting under CTO and Director titles.

Footprint is a useful cross-check. It posted in November's HN thread with "We mostly use Rust, Go, and TypeScript." The company is hiring for Rust work, and the Rust people already in its orbit don't call themselves Rust engineers.

| Metric | Value | Source |
|---|---|---|
| US profiles with Rust skill | 3,753 | Refolk's index |
| US profiles with "Rust" in title | 29 | Refolk's index |
| Rust title-to-skill ratio | 0.77% (about 1 in 129) | Derived |
| US profiles with Go skill | 17,611 (upper bound) | Refolk's index |
| Go-to-Rust skill multiple, US | 4.7x (upper bound) | Derived |
| HN Rust postings, Nov 2025 vs Nov 2026 | about 19 vs about 20 | Derived from hntrends |

One caveat on Go. The "Go" skill tag is ambiguous, and the sample includes non-engineering titles like Banker and VP Product, so 17,611 overstates real Go engineers. Read 4.7x as a ceiling. Even so, the direction is clear: Rust supply runs well behind Go, yet Rust now out-posts Go on HN.

## Who is hiring Rust engineers, and what do they pay?

Rust hiring concentrates in fintech, infrastructure and security, and the pay premium reflects how few experienced people there are. One concrete November data point: Blockrotate posted a Senior Systems / Rust Engineer role, remote with US and EU time zones preferred, at $130k to $170k plus equity.

Named employers from the HN threads and Refolk's index show the shape of the market:

- **Voluntas:** a trading firm written 100% in Rust, which screens with a Rust engineering challenge
- **Radar Labs:** main languages are Rust and TypeScript
- **Footprint:** posting on HN and employing Rust-skilled people in Refolk's index
- **Kraken, NVIDIA, Temporal Technologies:** employers of Rust-skilled senior engineers in Refolk's index

Footprint is the clearest overlap: it is posting for Rust work and already employs Rust-skilled people who don't use the title. When the companies hiring are also where the talent sits, outbound sourcing becomes a contest between a few teams for the same people, and reaching a candidate through their code is the most credible way in.

> **Open roles with Rust in the title** - [see the open roles](https://www.refolk.ai/jobs/search?q=rust)
>
> Live postings that name Rust in the job title.

## How do you source Rust developers from crates.io?

Start from crates.io, Rust's public package registry, where crate ownership is public. A crate is a Rust package, and owning one that other projects depend on is about the strongest public evidence of production Rust you can find.

The registry is big enough to source from. As of November 2026 it held 369,255 crates with 531.9 billion all-time downloads. Here is the workflow I'd use:

1. **Pick the crates your team depends on.** Open your own `Cargo.toml`. Every dependency there was written by someone who solved a problem you have.
2. **Pull the owners' portfolios.** `/api/v1/crates?user_id=N` lists every crate a given user owns. That turns one maintainer into a portfolio.
3. **Check reverse dependencies.** The `/reverse_dependencies` endpoint shows which published crates rely on a given crate. That is your production signal (more on this below).
4. **Go bulk if you need scale.** crates.io refreshes a full database dump every 24 hours at `static.crates.io/db-dump.tar.gz`. Load it once and you can query owners, crates and dependency edges offline.
5. **Map owners to people.** To source Rust developers on GitHub, follow each owner to their public commit history, and from there to a name, an employer and a way to reach them.

The most-downloaded crates, serde, syn and tokio, are an obvious starting list. Their maintainer and contributor graphs are a ready-made roster of people who write foundational Rust. They are also the first names every other recruiter will find, so go one level down: the authors of mid-tier crates that depend on tokio get fewer messages and are often just as good.

Step 5 is where most sourcing projects stall. Turning a handle into a person with a current employer and an email takes a lot of tab-switching per candidate. That's the gap [Refolk](https://www.refolk.ai/) closes: you describe who you want in plain English, and it searches GitHub and LinkedIn together, so the crate owner and the "Director of Engineering" profile come back as one person.

> **Example search:** "Senior engineers in the US who own or maintain published crates.io crates that depend on tokio, currently at infrastructure or fintech companies" - [run it on Refolk](https://www.refolk.ai/start?q=Senior%20engineers%20in%20the%20US%20who%20own%20or%20maintain%20published%20crates.io%20crates%20that%20depend%20on%20tokio%2C%20currently%20at%20infrastructure%20or%20fintech%20companies)
>
> A ranked shortlist matched across GitHub and LinkedIn, with each person's crates, current title and employer side by side.

## Why are reverse dependencies a better signal than download counts?

Reverse dependencies show whether other people's production code relies on a candidate's work. Download counts mostly show when a crate was released.

One developer's analysis found that 80% of crates.io downloads arrive at release time. A crate with a big number can just be one with frequent releases. Socket notes that since January 2026, download counts include only requests that come from Cargo, which is cleaner but still bursty.

| Signal | What it actually tells you | Reliability for sourcing |
|---|---|---|
| Download count | Release frequency and automated traffic | Weak |
| Crates owned (`user_id`) | Breadth of published work | Medium |
| Reverse dependencies | Other teams trust this code in production | Strong |
| Recent commits to depended-on crates | Still active, still shipping | Strong |

The mechanism is simple. Nobody adds a dependency by accident. When another published crate pulls in a candidate's library, an engineer somewhere read that code, judged it good enough, and staked their own project on it. That is a code review you didn't have to run.

Once reverse dependencies point you at a crate worth caring about, read its commit history:

- **Who touches the hard files?** Contributors who change the unsafe blocks, the async runtime glue or the FFI layer are the ones you want, not the person who fixed a typo in the README.
- **Is the activity recent?** A maintainer who stopped committing two years ago may have moved on.
- **Are they reviewing other people's PRs?** Reviewers on a busy crate are usually the senior people the HN posts are written for.

## How do you pitch Rust engineers who aren't looking?

Pitch the work, not the language. The people worth hiring already write Rust every day, so "the stack is Rust" isn't news to them. The problem domain, the codebase and the team are.

This pool is senior and mostly passive. Only 5% of Rust Foundation 2025 survey respondents have under 3 years of experience, and 40% use Rust for most of their coding work. So there are few juniors to train up, and the experienced people are busy shipping. HN threads show the same pull toward seniority: one analysis found posts naming staff-level roles rose from 77 in 2019 to 277 in 2026.

> A Rust posting that waits for applicants is waiting for people who are already employed and not reading job boards.

That's why posting and waiting stalls. A Rust req at a fintech or infrastructure company sits open because the right candidates are a Chief Architect at one competitor and a Distinguished Engineer at another, and neither is scrolling job listings. Paying an agency doesn't fix it either if the agency is running the same title searches that miss 128 of every 129 Rust-skilled profiles.

When you do reach out, make the first message specific:

- **Name their crate** and what your team uses it for
- **Describe the hard problem** your Rust code is solving, not the stack list
- **State the level and the range** up front. The Blockrotate post's $130k to $170k is the kind of number senior people expect to see
- **Offer a technical conversation first**, not a recruiter screen

## FAQ

### How do I find Rust engineers if they don't list Rust in their title?

Search their code, not their headline. In Refolk's index only 29 of 3,753 US profiles with the Rust skill put Rust in their title. Start with crates.io owners of crates your team depends on, use `/reverse_dependencies` to find crates other projects rely on, then trace the owners' commit history back to a current employer and contact details.

### Are crates.io download counts useful for Rust developer recruiting?

Only loosely. About 80% of downloads arrive at release time, so a high count often means frequent releases rather than wide production use. Reverse dependencies and recent commits are stronger signals, because they show other engineers chose to build on that code and that the author is still active.

### Is Rust demand actually growing, or is the HN thread just shrinking?

Mostly the thread is shrinking. Rust postings held at roughly 19 to 20 while the November thread fell from 387 to 244 postings, which pushed Rust's share from 4.9% to 8.2%. The useful takeaway is that Rust employers kept hiring through a downturn, so competition for the same senior people is getting tighter.

---

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