The Rust and Go talent market has gone absolutely mental.
I'm sitting here looking at offers for mid-level Rust developers hitting £130k in London, and I still can't get candidates to return my bloody calls. Three years ago, these roles were commanding maybe £85-90k. The landscape has fundamentally changed.
But before you blame "AI" or "the talent shortage" or whatever recruitment platitude is making the rounds this month, there's actually something much more interesting happening. After spending 8 years writing code and now 4 years hiring people who write it, I've got some thoughts on why these languages specifically have created such a bizarre market dynamic.
Why are Rust and Go commanding such ridiculous premiums?
The most obvious answer is performance and safety. But that's not the whole story.
Rust's memory safety guarantees have essentially killed off entire categories of security vulnerabilities. When the 2025 Cloudflare post-mortem revealed they'd rewritten their edge infrastructure in Rust and eliminated 87% of their runtime exceptions, even the most conservative CTOs started paying attention. Memory safety without garbage collection isn't just an engineering preference anymore. Following joint security advisories from the UK NCSC and CISA urging the migration away from memory-unsafe languages, adopting Rust is now tied directly to data governance under the UK's Data (Use and Access) Act 2025 (DUAA).
I placed a Rust team lead at a London fintech last month who told me something fascinating during our post-placement beer. "It's not that Rust is magic. It's that it forces developers to confront the hard problems up front instead of pushing them to production." That mindset shift is what companies are actually paying for.
Go, on the other hand, has absolutely dominated the cloud-native ecosystem. With the containerisation mandate that swept through enterprise in 2024-25, Go went from "that language Google made" to "the only practical way to build cloud infrastructure." The explosion of FinOps tools written in Go has only accelerated this trend.
The supply problem nobody talks about
There's not actually a shortage of people who can code in Rust or Go. There's a shortage of people who can architect systems in Rust or Go.
I see dozens of CVs every week from developers who've done the tutorials and built a side project. What's missing are the engineers who've:
- Debugged Rust in production environments
- Made architectural decisions around ownership models
- Optimised Go's garbage collector for specific workloads
- Built robust error handling patterns across microservices
These aren't skills you can pick up in a weekend hackathon. They require battle scars.
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
Where to actually find Rust & Go talent in the UK
Your instinct is probably wrong. GitHub profiles and Stack Overflow aren't where the best talent hangs out anymore.
The best Rust developers I've placed in the last year have come from:
- The Rust London User Group (yes, physical meetups still exist in 2026)
- Infrastructure teams at major banks who've been quietly rewriting critical components
- Security-focused startups, especially those working in supply chain security
- Ex-gaming engine developers who've crossed over to enterprise
For Go developers, the landscape looks different:
- The Kubernetes UK community is absolutely packed with Go talent
- SRE teams at any company running significant cloud workloads
- Former Python developers who hit scaling issues and made the switch
- Financial services automation teams
What doesn't work anymore: posting a generic job ad on The OHub and hoping someone applies. You need to go where these developers actually hang out and speak their language.
Interview techniques that actually assess real proficiency
Tossing LeetCode problems at Rust and Go candidates is about as useful as asking a Formula 1 driver to parallel park. You're testing the wrong skills.
Here's what I've seen work:
For Rust candidates
Skip the syntax questions. Anyone can learn syntax. Instead:
- Present them with a multithreaded problem and ask about ownership strategies
- Show them code with subtle lifetime annotation issues
- Ask them to explain when they'd use unsafe code (this one separates the theorists from practitioners)
- Have them review actual code from your codebase with deliberate anti-patterns
If they can articulate the tradeoffs between performance and safety, you've probably got someone who's actually used Rust in anger.
For Go candidates
- Focus on concurrency patterns beyond basic goroutines
- Present problems around error handling strategies (this is where Go projects often fail)
- Ask them to critique an existing API design
- Discuss how they'd instrument and profile a production service
The candidates worth hiring will have opinions. Strong ones. They won't just tell you how to do something in Go or Rust - they'll tell you whether you should be doing it at all.
The salary reality check
Brace yourself. Current UK rates for experienced Rust and Go developers:
- Junior (1-2 years): £65-80k
- Mid-level (3-5 years): £90-130k
- Senior/Lead: £120-170k
- Architects who can design entire systems: £150-200k+
These numbers are significantly higher outside the financial services sector than I've ever seen for specialist language skills. Even higher if you need security clearance.
What's wild is that these rates are still climbing. The gap between what companies are willing to pay and what candidates are expecting has actually narrowed in the last 6 months.
Will this bubble burst?
I don't think so. Not in the short term anyway.
The underlying drivers aren't hype-based like some previous tech bubbles. They're based on real engineering constraints and business problems that these languages genuinely solve better than alternatives.
The complexity of modern distributed systems isn't decreasing. The security requirements aren't getting any less stringent. The performance demands aren't easing up.
Rust and Go aren't just languages - they're responses to the fundamental challenges of building software in 2026. And until those challenges change dramatically, the demand isn't going anywhere.
But don't just take my word for it. Talk to your engineering teams. Ask them where their pain points are. See if Rust or Go might actually solve real problems instead of just ticking a "modernisation" box.
And when you do decide to hire, remember: the best candidates aren't looking for just another job. They're looking for interesting problems to solve. Lead with that, not just the salary.
Alex Dragomir spent 8 years as a software engineer before moving into technical recruitment. He now leads engineering hiring for a UK SaaS company and writes regularly on software engineering talent trends.
