Maybe AI Didn't Kill the Junior Developer Job. Maybe Remote Work Did.

Walk into any conversation about the tech job market right now and you’ll hear the same line: AI ate the entry-level jobs. In software it’s gone from theory to near-consensus. So it’s worth pausing on a recent Financial Times argument that points the finger somewhere else entirely — at the remote work habits we’ve all grown comfortable with.

The story everyone already believes

Start with the conventional wisdom, because it’s genuinely persuasive. Over the past year or two, junior hiring across tech has visibly frozen. As code-completion tools got sharper, the logic wrote itself: if AI can do the grunt work, why pay a newbie to do it?

And the grunt work fits the story perfectly. A junior developer’s early days are mostly boilerplate, bug fixes, and documentation cleanup — exactly the tasks generative AI handles best. So the math looks obvious. Why hire and train a beginner when you can hand one senior engineer an AI assistant and call it even?

Hard to argue with, on its face. But the FT says this picture is missing a piece.

The FT’s counter: the timing doesn’t add up

The core of the FT’s argument is timing. The moment junior hiring started to cool and the moment AI tools actually embedded themselves in real workflows don’t line up.

Entry-level hiring began softening before generative AI had any meaningful footprint on the job. So what changed in that window? The FT’s candidate is the remote and hybrid work culture that hardened after COVID-19.

Once you see it, the connection feels natural. The office had already been transformed long before the first AI coding assistant showed up.

Why remote work is uniquely brutal for beginners

This counter-argument lands because remote work doesn’t hit every seniority level the same way. The hinge is the cost of learning.

Senior engineers already know how to work. Put them at a kitchen table and productivity barely dips. Juniors are a different animal. A beginner’s growth comes largely from learning by osmosis — watching the person next to you untangle a problem, leaning over to ask a quick question, picking up context in the hallway after a meeting breaks up.

Almost all of those informal channels evaporate over a remote connection. A video call won’t transmit the muttered, half-articulated thought process of a senior debugging stuck code in real time.

For the employer, that rewrites the spreadsheet. Training a junior remotely got more expensive, and the time it takes that junior to start pulling their weight got longer. Harder to teach, slower to pay off — so companies drift toward the “already finished” option, the experienced hire. It wasn’t AI that squeezed out the beginner. It was the collapse of the onboarding pipeline.

So is AI off the hook?

Not so fast. Reading this as “the AI blame was wrong” misses the point — and it’s not what the FT claims either. These two forces aren’t mutually exclusive.

The likelier reality is that they stacked, hitting juniors from both sides. While remote work drove up the cost of teaching and growing beginners, AI shrank the entry-level work those beginners used to own. One pressure said “hard to train.” The other said “less to assign.” They arrived at the same time.

One honest caveat: this isn’t a topic that’s been chewed over much in the community over the past month. So the right posture is to treat the FT’s view as a working hypothesis, not a settled finding backed by hard data.

What would actually have to change

This reframe matters because the diagnosis dictates the prescription. If AI is the culprit, there isn’t much we can do — you can’t legislate progress away.

But if the onboarding structure is the problem, the picture opens up. How a junior spends their first year or two, what mentorship looks like, where the line falls between office and home — those are all things a company can design. It means you can flip the act of growing junior talent back from a cost into an investment.

Which turns the question on its head. Are we really failing to hire juniors because of AI? Or have we simply forgotten how to raise one? Ask yourself which one your company looks like.