August 26, 2026
Who Trains the Next Senior Engineer?
Entry-level developer postings dropped roughly 60% between 2022 and 2024. Entry-level employment for people aged 22 to 25 fell around 16% in the fields most exposed to AI. Senior engineers at Microsoft have publicly warned that the junior pipeline is being hollowed out.
Now hold that next to a number nothing has changed about: it takes five to nine years to turn a graduate into a genuine senior engineer.
Stop hiring juniors for three years and you haven't saved money. You've scheduled a senior shortage for five to ten years out, in an industry where the one thing AI has unambiguously increased demand for is people who can judge whether generated work is actually correct.
The training disappeared, the requirement didn't
Juniors never learned primarily from being taught. They learned from doing work that was economically marginal, which is exactly why it was safe to give them.
The small bug fix that forced them to read an unfamiliar module. The boilerplate that taught them the codebase's conventions through repetition. The tedious refactor that revealed why the architecture was shaped the way it was. None of it was glamorous. All of it was the apprenticeship.
That is precisely the work AI now does best.
So we removed the tasks people learned from while keeping the expectation that they arrive competent. Worse, the junior's actual job has shifted to reviewing, validating, and integrating AI-generated work, which is a harder skill than writing the original code was. Judgment is the thing you develop last. We've made it the entry requirement.
Why this is your problem specifically
It's tempting to file this under industry trends, or hiring policy, or someone else's budget. Two reasons it lands on engineering leaders.
The pipeline is a local decision. Some large enterprises have quietly increased junior hiring after doing exactly this arithmetic and concluding that future seniors have to come from somewhere. Others cut. Both are choices being made by people running engineering teams, and the consequences land on whoever runs that team in five years.
And nobody else can fix the learning half. Even organizations that keep hiring juniors have to answer a question the old apprenticeship answered by itself: if the entry-level work is gone, how does anyone build judgment now? No hiring requisition solves that. It's a management design problem.
What seems to work
The most promising model looks like a preceptorship. Pair an early-career engineer with an experienced one on real production work, and have them use AI tools together, with the senior watching how the junior works.
The critical detail is what the senior watches for. Not whether the code is correct. Whether the junior's evaluation is correct. What did they accept, what did they reject, and why? Where did their understanding quietly break down while the output still looked plausible?
That's a different activity from reviewing a finished pull request, and it maps onto delegation more than onto code review. You aren't delegating a task. You're building the judgment that makes someone worth delegating to later.
There's an encouraging finding alongside this: IBM's research suggests juniors may benefit more from AI tools than seniors do, in both productivity and learning speed, provided they get proper guidance. The technology isn't inherently hostile to developing people. Unsupervised use is.
The self-interested argument
If the developmental case doesn't move your organization, try the operational one.
All-senior teams have a specific pathology: nobody asks the naive question. Juniors surface assumptions everyone else stopped noticing, and in an AI-assisted codebase, unexamined assumptions are exactly what piles up.
Seniors also grow most through teaching. Explaining an architectural decision forces you to actually understand it. Remove the juniors and your seniors quietly stop developing too.
Then there's the market. If the whole industry underinvests in juniors for several years, seniors become scarcer and more expensive at exactly the moment demand for judgment peaks. Being one of the few organizations that still knows how to grow them stops being a cost and starts being an advantage.
This is the final session of the Leading Through AI Adoption module I teach. The full lesson, and the four before it, are free to read: Careers When the Junior Work Is Automated.