Is Rust worth learning?

Short answer: it depends on where you already are. If you work close to the metal — C, C++, embedded, infrastructure — Rust is the most reasonable bet you can make with your time. If you live off web backend or data work and what you want is a new job this quarter, Rust is not the shortest route. Both things are true at once, and mixing them up is how people lose six months.

What follows is the data I would look at before deciding, and what I see in the ads I put in front of candidates.

Why it is growing

Rust is not growing because it is fashionable. It is growing because it fixes something that costs money: memory bugs. In November 2025 Google published the Android numbers, which is where this has been measured best. Memory safety flaws have dropped below 20% of all vulnerabilities for the first time, and the vulnerability density of the Rust code is roughly 1,000 times lower than that of the C and C++ code in the same system — around 0.2 per million lines against something closer to 1,000. It is all in their own write-up, Rust in Android: move fast and fix things.

The part worth taking into an interview is not the security angle, which everyone already repeats, but the cost one. In that same report, Rust changes are rolled back about 4 times less often than C++ changes and spend around 25% less time in code review. That is what convinces a CTO to pay for a migration, and it is the argument you want to have ready if you are going to make the case for Rust inside your own company.

Now the other side of the number. In the 2025 Stack Overflow Developer Survey, with around 49,000 participants, 14.8% had used Rust in the past year, up from roughly 12% the year before. It is rising, but it is still the fourteenth language on the list. Rust is growing fast from a small base, and that single fact explains both why there are few openings and why the ones that exist are hard to fill.

What Rust job ads actually ask for

Open a handful of Rust ads anywhere in Europe and almost none of them are what people picture when they start learning the language:

• Rust almost never travels alone. It comes with C, with C++, or with both. In the searches I run at WATA that is exactly the block: C, C++, Rust and embedded. Someone who arrives at one of those ads knowing only Rust is out after the first technical call.
• Many ads say "Rust, or C++ and willing to learn Rust". That is good news for you. It means the company knows there is almost nobody with five years of Rust in production and is prepared to pay for the ramp-up. It also means your C++ years are not discounted.
• The sectors are specific. Embedded and defence, payments and trading, semiconductors and high-performance computing, network infrastructure. Nobody is hiring Rust to build a CRUD app.
• Average seniority is high. There is far more senior and tech lead than junior, because what gets hired is not "knowing Rust", it is having taken critical systems to production.

So the reliable way in is not "learn Rust, then look for a Rust job". It is reaching Rust from where you already stand: from C++, from firmware, from a game engine, from the lower layers of a platform. Coming from there, the jump takes months. Coming from the web, it takes years.

I am not going to give you a salary figure

Not out of caution, but because there is no Rust salary source with a published method that I could show you. The aggregators contradict each other for the same job title, because they mix embedded roles with blockchain roles, and internships with senior positions. A number like that does not help you negotiate; it helps you be confidently wrong.

What I can tell you is how a small market with real demand behaves: the range is set by the specific role and the sector, not by the language. And a Rust position takes longer to fill than an equivalent Java one, which works in favour of whoever is already inside. If you want actual numbers, every search I publish carries its range: you can see them in the open searches, with the range and the process in plain sight before you ever talk to me.

One note if you are reading this from Spain, which is where most of the people I work with are based: the companies hiring for these roles are often in the UK, Germany, Austria or Switzerland, and the work is remote. That widens the pool of Rust roles you can reach a long way beyond what a local job board shows you.

Who should put the months in

It is worth it for anyone already working close to the metal who does not want their next ten years to depend on their employer keeping a 2009-era C++ codebase alive. And it is worth it for anyone doing infrastructure: command-line tooling, proxies, agents, databases. Rust is no longer exotic there, and knowing it puts you in conversations that used to pass you by.

It is not worth it for anyone looking for the fastest possible job change, or for anyone hoping Rust will spare them the hard part. Rust does not teach you systems; it forces you to understand them. The learning curve everybody complains about is not the syntax, it is that the compiler will not let you move on with a vague mental model of who owns what. For someone coming from C++ that is half the battle already won. For someone who has never thought about memory, it is the whole course.

How to start without wasting the time

A book covers the syntax, and the syntax is not where the difficulty is. The problem is that reading gives you nothing to talk about in an interview. What does is rewriting in Rust something you already built in another language and then comparing: where the compiler pushed back, and which of your assumptions turned out to be wrong. That story is what I am after when I ask you about Rust, the same way I ask a DBA about a real incident — I wrote about that in what is a DBA?

If you read Spanish and want a route already mapped out, my book Curso de programación Rust (Anaya) has its own site at rust-lang.es.

One last thing, and it is the one that really settles this. Before you invest months, open five Rust ads you would like to be able to read without flinching a year from now. If all five want C++ and embedded and that is where you come from, you already have your answer. If none of them looks like the work you want to do, Rust can still be a beautiful language and a bad career decision for you.