Say you write Rust, you love it, and you would like someone to pay you for it. The usual advice is that you will write Go or Python at work and keep Rust for the weekends. The board says that is half true, and the half that is false is interesting.
On October 6, 2026 we counted 11,704 open tech roles at 762 companies (distinct roles, so one role posted in ten cities counts once). 858 of them name Rust. That is about one role in fourteen, at 156 companies. Not nothing.
But one company has a fifth of them.
Who is hiring for Rust
| Company | Rust roles |
|---|---|
| Anduril Industries | 168 |
| OpenAI | 60 |
| Cloudflare | 51 |
| Anthropic | 49 |
| Proton | 27 |
| Perplexity | 25 |
| Roblox | 22 |
| Canonical | 21 |
| Deepgram | 19 |
| GitLab | 15 |
| Grafana Labs | 15 |
| MongoDB | 14 |
Anduril alone is 19.6% of every open Rust role we track. The top twelve together hold 486, which is 57%.
For comparison, the top twelve Go employers hold 29% of Go roles, and the top twelve Python employers hold 30% of Python roles. Rust is twice as concentrated as either.
The long tail is long but thin: 114 of the 156 companies have only one to three Rust roles open. So the honest version of "is there Rust work out there" is: yes, at a handful of big employers, and then a scattering of single roles everywhere else. If defence work is not for you, take Anduril out and you are left with 690 roles at 155 companies, which is a very different market.
Companies are unusually honest about it
One thing stands out. Rust is the language companies are most likely to put in the job title.
| Language | Roles naming it | Roles with it in the title | Ratio |
|---|---|---|---|
| Rust | 858 | 33 | 26 to 1 |
| Go | 2,251 | 61 | 37 to 1 |
| Python | 4,799 | 56 | 86 to 1 |
| TypeScript | 1,747 | 10 | 175 to 1 |
Twenty six to one still means a title search misses almost everything (search by stack, always). But Rust lands in the title more often than Go, Python or TypeScript do, which is at least a hint that a Rust role is more often a Rust job.
Rust is rarely alone
Now the less tidy part. Half of all Rust roles (427 of 858) name four or more programming languages in total. Only 49 name Rust and nothing else.
That is the most crowded stack of any language we have measured. For Go it is about a third of roles with four or more, for Python under a fifth.
The company Rust usually keeps:
Go, in 511 Rust roles (60%)
Python, in 493
C++, in 404 (47%)
Kubernetes, in 293
Read that as two different jobs wearing the same tag. Rust next to C++ is systems work: runtimes, embedded, performance. Rust next to Go and Kubernetes is infrastructure, where Rust is one of the languages the platform happens to be written in.
For newer roles we can also tell whether Rust is in the core of the job or just mentioned. Of the 368 Rust roles where that split exists, Rust is core in 214. That is 58%, against 73% for Python and 75% for TypeScript. So a Rust tag is more often "we use this somewhere" than a Python tag is.
The money
Among roles that publish a yearly US dollar band, the median bottom of the band is:
| Language | Median salary floor | Roles with a band |
|---|---|---|
| Rust | $191,000 | 553 |
| C++ | $190,000 | 707 |
| Python | $168,650 | 2,805 |
| Go | $168,000 | 1,300 |
| TypeScript | $168,000 | 1,022 |
That is $22,000 to $23,000 above Go, Python and TypeScript. We would love to tell you Rust skills command a premium, and maybe they do. But look at who is hiring: frontier AI labs and a large defence company. Some of that gap is the language, some of it is who pays for the language, and we cannot separate the two from this data. (C++ sitting right next to Rust suggests the systems-work explanation carries a good part of it.)
Harder to get in
21 of the 858 Rust roles are junior. That is 2.4%, about half the 4.6% across all open tech roles, and the lowest junior share of any language here. 563 are senior (66%).
Remote is also thinner than average. 37 Rust roles are labelled remote from anywhere (treat that as a ceiling, our anywhere labels still run generous), 221 are remote within a country or region, 293 are hybrid and 307 are onsite. Onsite is 36% of Rust roles against about 25% for the board as a whole.
If Rust is your language
Search by stack, but expect to filter a lot. Half the matches list four or more languages.
Decide which Rust you want. Systems (pair it with C++) and infrastructure (pair it with Go and Kubernetes) are different job hunts.
If you are early in your career, Rust as a second language next to Go or Python is the realistic entry. Rust-first junior roles barely exist on the board right now.
Know the concentration. A handful of employers move this market, so if one of them pauses hiring, the board will look very different. Starring the companies you care about on remoet.dev means their new roles come to you instead of the other way round.
Caveats
Stacks are extracted from the post text by a model, so "Rust or Go" and "Rust and Go" look the same, and a post that mentions the company's wider stack in passing gets tagged with it. The title count is a plain word match on "Rust", so in principle it could catch a title that is not about the language (we would enjoy finding a rustic furniture designer in there, but we have not looked role by role). Salaries cover only roles that publish a band, and we used the bottom of each band, so every figure understates the band. All of it is one day, October 6, 2026.
If you write Rust for a living and this does not match what you see out there, we want to hear it. Come tell us in Discord.
