There’s a lot of noise out there about AI stealing jobs, especially if you’re in tech. Since tools like ChatGPT and GitHub Copilot landed in developer workflows, it’s easy to see why the headlines have been dramatic.
But is AI really replacing developers in the UK? Or are we just seeing a shift in the shape of the role? Let’s dig into the stats, the nuance, and what both devs and hiring teams actually need to know.
But it’s not just because of AI. According to the Office for National Statistics, total job vacancies in the UK fell to 736,000 between March and May 2025. That’s a 7.9% drop from the previous quarter and a 16.9% drop from last year.
Tech and information roles were hit particularly hard.
However, this is the 35th consecutive quarterly vacancy drop, and it started long before generative AI became mainstream. The real causes? A combination of post-pandemic corrections, reduced venture capital funding, and a reshuffle in hiring priorities after the big remote-work boom.
It’s easy to point fingers at AI when we talk about job cuts or industry shake-ups. But there’s a bigger, slower-moving force at play here, and it’s one we’re still underestimating: the lasting impact of COVID-19.
Yes, the pandemic started over five years ago. But its ripple effects are still messing with hiring patterns, business models, and entire industries today. Remote work didn’t just become normal, it flipped the talent market on its head. Budgets shifted, priorities changed, and entire teams were restructured to fit a new way of working.
In tech, we saw huge hiring spikes in 2020–2022 to meet digital demand, followed by the inevitable correction when the world settled. Some of the recent job cuts we’re seeing? They're part of that rebalancing. Not an AI takeover.
Let’s look at how dev productivity is actually changing.
GitHub partnered with Accenture to study enterprise devs using GitHub Copilot. The results? Devs completed tasks up to 55% faster and felt more confident in their code quality - with 85% reporting improved output (GitHub & Accenture, 2024).
Other studies back this up. One trial showed that Copilot users finished tasks in half the time (1h 11m vs 2h 41m), with a 78% completion rate versus 70% for non-Copilot users (Visual Studio Magazine).
And it’s not just about speed. Over 90% of Copilot users in one survey reported greater job satisfaction and less frustration (LinearB).
So no, the robots aren’t replacing you. But they are sitting next to you at the (virtual) desk.
Here’s where things get even more interesting. Developers aren’t being cut as a whole, but their roles are changing shape.
In short: AI can help write code, but it can’t yet understand architecture, nuance, or ethics. It also can’t explain your code to a stakeholder, or debug a cross-functional nightmare. That's where you come in.
Entry-level developers are probably feeling the pressure the most. Bootcamp grads and those without much commercial experience are now competing with AI tools that can scaffold full apps in seconds.
But employers still need junior talent, just with a new mindset. What’s getting hired now is someone who can:
For junior devs, showing that you can work with AI is often more impressive than trying to prove you don’t need it. It’s time to move with the times, not go against it.
If you’re hiring, firing, or reorganising dev teams, here’s the big takeaway:
AI is a tool, not a team.
Companies seeing real value from tools like Copilot aren’t reducing headcount, they’re rethinking how humans and AI work together. That includes:
If you’re worried about job security, here’s your roadmap:
And yes, build cool stuff using AI. It’s not cheating — it’s smart engineering.
Not quite. It’s eating the boring bits, changing what gets hired and raising the bar. The UK dev market is quieter than last year — but not because it’s become obsolete.
The best developers right now? They're the ones treating AI like a superpower, not a threat.