Rust topped the 2025 Stack Overflow Developer Survey as the most admired programming language yet again, with 72% of developers who use it saying they want to keep using it — ahead of Gleam (70%), Elixir (66%), and Zig (64%). Its package manager, Cargo, led its own category too, with 71% admiration among infrastructure tools. For a language that regularly tops "most loved" rankings, it's worth asking a more practical question: does that admiration translate into career value?

Admired Doesn't Mean In-Demand — Yet

Admiration surveys measure developer satisfaction, not hiring volume. Rust job postings remain a small fraction of what Python, JavaScript, or Java generate — commentary among developers following the survey has described current Rust job demand as closer to niche than mainstream. That gap between how much developers enjoy a language and how many companies are hiring for it specifically is real, and it's the first thing to understand before deciding to prioritize learning it.

Where Rust Actually Gets Used

Rust's real strength is in systems and performance-critical work: components of browser engines, parts of the Linux kernel and Android's lower-level stack, cloud infrastructure tooling, and backend services at companies that need predictable low-latency performance at scale. If your target roles are in systems programming, infrastructure/platform engineering, embedded systems, or performance-sensitive backend work, Rust is a genuinely strong differentiator — not a trend to chase, but a real skill gap many of these teams report struggling to fill.

Who Should (and Shouldn't) Prioritize It

• Learn it if: you're targeting infrastructure, platform, embedded, or performance-critical backend roles, or you already know C/C++ and want memory safety without sacrificing performance.
• Hold off if: you're early in your career and haven't yet built strong fundamentals in a widely-hired language like Python, JavaScript/TypeScript, or Java — those will open far more doors in the near term, and Rust is easier to pick up later once you have a systems-level problem that actually calls for it.

The Practical Takeaway

Treat Rust as a specialization to add on top of a marketable primary stack, not a default first language. The developers getting real career value from it are mostly the ones who already had a systems or infrastructure role and added Rust to solve a specific performance or safety problem — not those who learned it speculatively because it tops admiration surveys. See the full breakdown on the Stack Overflow 2025 Developer Survey.