What this means for sourcing Rust developers
Rust work concentrates around San Francisco, which is where a search returns depth rather than a handful of profiles. Asking for Python, TypeScript alongside Rust keeps the pool realistic; requirements outside that set narrow it quickly. 34% can be contacted directly, but only 20% signal they are open to work, so most outreach here starts cold.
Where are Rust developers concentrated?
Cities ranked by their share of the Rust developers whose location we can read, so you can see where a search is likely to return depth rather than a handful of profiles.
| # | City | Share of located developers |
|---|---|---|
| 1 | San Francisco | 8% |
| 2 | London | 5% |
| 3 | Seattle | 5% |
| 4 | New York | 4% |
| 5 | Tokyo | 4% |
| 6 | Berlin | 3% |
No single city dominates, so a search limited to one location will miss most of this pool.
By country, the pool is led by United States, Germany, United Kingdom.
What else do Rust developers work with?
The technologies that most often appear alongside Rust in their repositories. Useful when writing the job spec: asking for Python, TypeScript, AWS alongside Rust keeps the pool realistic, asking for something absent from this list will shrink it fast.
What roles do they actually hold?
Rust is not a single job. The roles detected across their public work, ranked by share of the pool:
| # | Role | Share of pool |
|---|---|---|
| 1 | Software engineering | 72% |
| 2 | Ai product engineering | 27% |
| 3 | Infrastructure, devops and sre | 16% |
| 4 | Ai research | 13% |
How reachable are they?
70% pushed code within the last 90 days. Recency matters more than follower counts here: an account with a large following but no recent commits is a worse lead than a quiet contributor shipping every week.
Who employs Rust developers today?
The employers most represented in this pool, from what developers state publicly on GitHub. Read it two ways: a target list, and the companies you will be competing against for the same people.
| # | Company |
|---|---|
| 1 | NVIDIA |
| 2 | Microsoft |
| 3 | Red Hat |
| 4 | DataDog |
| 5 | |
| 6 | zed-industries |
| 7 | AWS |
| 8 | bitwarden |
What they build themselves
The most-starred repositories these developers created, as opposed to the ecosystem projects they contribute to. A shortcut to the people who ship rather than the people who list the language.
| # | Project | Stars |
|---|---|---|
| 1 | avelino/awesome-go | ★ 180,975 |
| 2 | rustdesk/rustdesk | ★ 121,975 |
| 3 | ruvnet/RuView | ★ 91,001 |
| 4 | BurntSushi/ripgrep | ★ 67,282 |
| 5 | sharkdp/bat | ★ 60,225 |
Which projects do they contribute to?
35% of the pool contributes to a reference project in the Rust ecosystem. Those contributions are the strongest signal available: they are reviewed by maintainers, unlike a self-reported CV line.
| # | Project | Share of pool |
|---|---|---|
| 1 | MystenLabs/sui | 1% |
| 2 | zed-industries/zed | 1% |
| 3 | BurntSushi/ripgrep | 1% |
| 4 | SeaQL/sea-orm | 1% |
Frequently asked questions
Where can I find Rust developers?
They are most concentrated in San Francisco, and the deepest national pool is United States, based on StarHunt's index as of September 2026.
Can you contact Rust developers directly?
34% of the active Rust developers StarHunt surfaces list a public email address on their GitHub profile, so a large share can be reached without an introduction.
What skills usually go with Rust?
Most commonly Python, TypeScript, AWS, based on the technologies present across their public repositories.
What roles do Rust developers hold?
The most common is software engineering, ahead of the other roles detected across their public work.
Filter Rust developers by city, complementary stack and availability, and get the contactable ones in seconds.
Find Rust developers