Rust vs Go jobs and salaries in 2026:
the honest hiring market.
What is actually published on Rust and Go pay
Start with what nobody publishes. The BLS does not break software developer wages down by programming language, and Stack Overflow, which ran a top-paying-technologies chart as recently as its 2023 survey, has dropped it: the 2025 survey reports compensation by job title only. That leaves exactly two language-specific numbers in the open, both of them Glassdoor self-reported averages on very thin samples. Any table claiming to give you Rust-vs-Go pay by years of experience is not reading a source, because there is no source to read.
The US software developer wage distribution (all languages)
| Percentile | Annual wage | Reads as |
|---|---|---|
| 10th | $82,460 | Bottom of the market |
| 25th | $105,210 | Lower quartile |
| 50th (median) | $135,980 | The typical US developer |
| 75th | $171,980 | Upper quartile |
| 90th | $214,670 | Top of the market |
The only language-specific pay figures published
- 25th
- $115,563
- 75th
- $191,224
- 90th
- $239,372
- 25th
- $108,317
- 75th
- $183,834
- 90th
- $232,703
We used to publish one. It was removed because it could not be sourced: the bands were shaped from the all-levels Glassdoor percentile spread and relabelled as entry, mid, senior and staff, which invents a structure the underlying data does not have. Thirteen anonymous submissions of unknown seniority cannot be resolved into a career curve. What genuinely moves your number is sector (infrastructure and crypto pay above web services), metro (a Bay Area or NYC band runs well above the national percentiles above), company tier, and whether the language is incidental to the role or the reason you were hired. For a specific target, read live postings with disclosed ranges: US pay transparency laws now require them in California, Colorado, New York, Washington and Illinois, which makes real advertised bands easier to find than any survey.
Industry breakdown: where Rust vs Go roles live
The career calculus: expected earnings
What you actually earn over a career is pay per role multiplied by the share of that career you spend in one, so a search that runs long is a real cost, not a rounding error. Rust pays a premium per role on the thin evidence above, but draws from a narrower market. On the Glassdoor figures the premium is around 5%, which is roughly three weeks of pay a year: if a Rust search routinely takes a month longer than a Go search, the premium is gone. That arithmetic is ours and the inputs are both on this page, so you can redo it with your own assumptions. For early-career engineers, Go's larger market means more interview opportunities, faster offers, and more negotiating leverage. For senior specialists in embedded, blockchain, or security, Rust's premium in a narrower market may favour specialisation.
Questions
Which pays more, Rust or Go developer?⌄
Rust edges it on the only language-specific figures anyone publishes, but by far less than is usually claimed. Glassdoor's self-reported US average is $147,717 for a Rust Developer, drawn from just 13 salaries, against $140,360 for a Golang Developer drawn from 96. That is a gap of about 5%, not the 10-20% premium commonly repeated. Neither the BLS nor the Stack Overflow survey publishes pay by programming language at all, and no source publishes a Rust-vs-Go breakdown by experience level. For scale, BLS OEWS put the US median for all software developers at $135,980 in May 2025. Total career earnings may still favour Go, because Go is the more widely used language (16.4% of Stack Overflow 2025 respondents against Rust's 14.8%) and the default across the infrastructure tier, so there are more roles to pick from.
Are there enough Rust jobs?⌄
Yes, but fewer than Go. Rust roles are concentrated in systems programming (Microsoft, Cloudflare, Amazon), blockchain (Solana, Polkadot), and embedded (firmware, automotive). If you want a Rust-specific job, you may need to target specific companies or work remotely. Go has the broader distribution. Neither Indeed nor LinkedIn publishes a stable open-role count by language, so we do not quote a ratio.