The pitch sounds airtight. AI writes the boilerplate a junior used to write, so why hire the junior? Skip the ramp-up, skip the reviews that feel like teaching, ship faster with a lean team of seniors and a fleet of models. It’s clean, it’s cheap, and it’s one of the most expensive mistakes a software company can make right now.
Seniors don’t spawn
Every senior engineer you admire was once a junior who was allowed to be slow, allowed to be wrong, allowed to ask the “dumb” question in review. There is no other supply. Stop hiring juniors and you haven’t saved money — you’ve stopped manufacturing the exact people your company will be desperate for in five years, and so has everyone else. The pipeline doesn’t pause politely. It empties.
And someone has to be able to judge the machine’s output. An AI will hand you code that’s confidently, subtly wrong. The person who catches it is a senior — a former junior who earned that instinct by making those mistakes themselves, on purpose, while it was safe.
Juniors are your smoke detector
There’s a less obvious reason to keep hiring them. A sharp newcomer is the best test of whether your systems actually make sense. If a motivated junior armed with the best AI tools still can’t get productive in your codebase, that is not a junior problem. It’s a design smell you’d otherwise never notice, because your seniors memorized their way around the potholes years ago.
The category error
“AI does junior work” confuses tasks with growth. AI does junior tasks — the boilerplate, the first draft, the lookup. It does not do junior development: the messy, compounding process of a person becoming a senior. The value of a junior was never the boilerplate they produced. It was who they were turning into.
The version that actually wins
Here’s the second-order move most companies are too shortsighted to make. The teams that win the next decade won’t be the ones that squeezed the most tokens out of AI this quarter. They’ll be the ones that used AI to make juniors senior faster — turning a two-year ramp into six months by handing a curious person an infinitely patient tutor — instead of using it as a reason to never let that person in the door.
AI didn’t remove the need for junior developers. It removed your excuse for onboarding them badly. One of those is a strategy. The other is eating your own future to make this quarter look lean. Which one are you actually running?
We think hard about the second-order effects of what we build — including who a tool quietly replaces, and who it could be growing instead. That’s what we do at Rebel Studios.