Between 2022 and 2024, job postings for entry-level developers decreased by 60%. AI wasn't the one to let go of juniors, it just made companies stop hiring them.
A QCon London presentation a couple of weeks ago neatly summed it all up: it's not that the ladder doesn't have steps, it's that we're missing the process of building the steps in the first place.
Here's what happened.
The Numbers Everyone's Quoting
Dario Amodei predicted AI would write 90% of all code within six months. A Redwood Research analysis found the actual number was closer to 50% when you count committed code. Google reports 25% of internal code is AI-generated. Microsoft says around 30%.
Those numbers are real. But they hide something.
The code AI writes best is the same code juniors used to write. Boilerplate. Unit tests. Simple bug fixes. CRUD endpoints. The boring stuff that nobody wanted to do but everybody needed to learn from.
The Hiring Freeze Nobody Talks About
Harvard researchers analyzed 62 million workers across 285,000 U.S. firms. Companies that adopted generative AI saw junior developer employment drop 9-10% within six quarters. Senior employment kept rising.
This isn't a layoff story. It's a hiring story. Companies aren't firing juniors. They're just not replacing the ones who leave.
Big Tech made it worse. New grads represented only 7% of hires in 2025. That's a 78% reduction from 2019. The "junior" title now expects 3+ years of experience and production-ready code on day one.
The Perception Gap
METR ran a proper randomized controlled trial in early 2025. Experienced developers using AI tools took 19% longer on tasks. Before starting, they predicted AI would make them 24% faster. After finishing, they still believed they were 20% faster.
The gap is 43 percentage points.
Then METR tried to run a follow-up study. They couldn't. Between 30% and 50% of developers refused to participate if it meant working without AI. One developer said: "I'd like to help but I really like using AI."
In less than a year, AI went from "makes experienced devs slower but they can't tell" to "developers won't even attempt work without it."
That's the real problem.
The Deleted Curriculum
The tasks AI automated weren't just tasks. Writing that boilerplate is how you learned what the boilerplate does. Debugging that simple bug is how you developed intuition for where bugs hide. Reviewing that CRUD endpoint is how you understood what production code actually looks like.
Nobody designed a replacement for that learning process. We just deleted it.
The QCon speaker nailed the paradox. Amodei himself said programmers still need to specify the overall design, understand how code collaborates, and decide whether a design is secure. He separated the writing from the engineering.
But the writing was how people learned the engineering.
So Now What?
Some companies are trying. IBM and LinkedIn announced they're hiring "AI-native" engineers in 2026. But what does that even mean? You can't be AI-native if you never learned what AI is automating.
We're optimizing for today's output at the cost of tomorrow's talent pipeline. Every senior engineer who exists today learned by doing the work we just handed to machines.
In five years, who reviews the AI's code? 🤔
What's your take — is the junior dev role actually gone, or is it just being redefined into something we haven't named yet? 👇
Top comments (0)