November 10, 2026·4 min read
Entry-level software hiring is down in the United States, the United Kingdom, Canada, Germany, the Netherlands and Sweden, while senior employment has held up far better. That is the headline of a Financial Times analysis published this week, and it matches what most junior engineers already feel: the first job has become the hardest one to get.
The easy story is that AI took those jobs. The data does not fully support it, and the real story is more useful. This post is for two readers: junior engineers trying to get through the door, and the hiring managers deciding who gets through it. The short version for both is the same. AI did not remove the need for engineers. It removed the need for engineers who can only type code, and it made engineering judgement the thing that gets you hired.
The FT analysis makes four points, and they are worth reading together rather than picking the scariest one.
Independent research points the same way on the first point. Stanford's Digital Economy Lab found that employment of 22 to 25 year olds in the most AI-exposed occupations now sits 19% below where it would be had it kept pace with less exposed peers, with no comparable gap for experienced workers (Brynjolfsson, Chandar and Chen, "Canaries in the Coal Mine?").
Put those together and you get a more precise picture than "AI is eating junior jobs". Companies under cost pressure stopped hiring the people they would have had to train. AI gave them a reason to believe they could get away with it. Whether they actually can is a different question.
A junior hire has always been a bet: you pay for six to twelve months of learning and get an engineer on the other side. When money is expensive, that bet is the first thing a budget cuts. When a team lead can ask an AI assistant to write the boilerplate a junior used to write, the bet looks even worse on a spreadsheet.
The flaw in that logic is in point three above. If AI made teams dramatically more productive, output and revenue would show it. Mostly they do not. What AI removed is the cheapest, most visible part of junior work: writing a function from a clear spec. It did not remove the parts that actually cost senior time: understanding why a service is down, reading a system nobody documented, deciding whether a generated change is safe to ship.
And seniors do not appear from nowhere. Every team that stops hiring juniors today is choosing to have no mid-level engineers in three years. We made the long version of this argument in why hiring junior engineers is still worth it.
Here is the part that is genuinely good news. AI has made it faster than ever to learn the engineering skills that companies still pay for, as long as you use it to understand systems rather than to skip understanding them.
Two juniors can use the same AI assistant very differently. One pastes the error, accepts the fix and moves on. The other asks why the error happened, reads the logs the fix depends on, and checks what else the change touches. After six months the first has a portfolio of code they cannot explain. The second has the judgement of someone with two years of experience. Only the second one gets through a good interview.
What that looks like in practice:
Dockerfile, a failing CI job, a Kubernetes manifest, a systemd unit. Then run it, break it and fix it yourself. Linux, networking, containers and CI are where AI helps a learner most, because the explanation is instant and the feedback from a real machine is honest.The gap the market opened is not "people who can use AI" versus "people who cannot". Everyone can use AI. The gap is between people who can tell when AI is wrong and people who cannot, and that is an engineering skill you can learn faster now than ever before.
If entry-level hiring is down, every junior you do hire matters more, and the old screens are badly suited to finding the right ones. An algorithm puzzle measures exactly the skill AI made cheap. A junior who memorised fifty LeetCode patterns and a junior who can actually debug look identical on that test.
What separates them shows up in a real environment:
This is how EasyEnv runs junior assessments: a real Linux environment built from your stack, AI tools allowed, the session recorded, and a person making the decision. The approach for AI-native candidates specifically is in assessing AI-native junior engineers.
To be fair to the other side: the data is early, and it is mixed. The weak AI link outside the US may simply mean adoption there is a year or two behind. Some routine programming work is genuinely being absorbed by AI tools, and a junior whose only skill is writing simple CRUD code from a ticket is in a worse position than they were in 2021. Learning engineering fundamentals does not guarantee a job in a market with fewer openings. It does put you in the group that companies still hire from when they hire at all.
The first job got harder for reasons that are mostly economic, with AI as the accelerant and the excuse. For junior engineers, the response is not to compete with AI on typing code but to use it to learn the engineering around the code faster than anyone could before. For hiring managers, the response is to test juniors in the conditions they will actually work in, with AI on the desk, and hire the ones who can tell when it is wrong.
If you hire juniors: what does your first-round assessment measure today, and is it something an AI assistant could already pass?
Run live coding sessions and take-home challenges in real production environments. Watch sessions back, score consistently, and hire with confidence.
More posts you might like
EasyEnv now plugs into Pinpoint. Click Send to EasyEnv on a candidate, or let a stage do it for you, and the status and your team's decision come back onto the candidate in Pinpoint.
EasyEnv now works inside Ashby. Add an EasyEnv role to an interview plan, and candidates get a real environment to work in while every step, and your team's final decision, lands back on the candidate in Ashby.
Read more
HackerRank now apologises for LeetCode grinding and sells Chakra, an AI interviewer in a canvas "like a dev environment". Here is what that canvas still cannot show a hiring manager, what a real environment shows instead, and when each one is the right tool.
Read more
