Don't Skip Junior Talent Because of AI
Core idea: Eliminating beginner opportunities creates future expertise shortages.
The Temptation to Cut Juniors
When organizations look for quick ROI from their AI investments, junior talent is often the first target. The logic seems straightforward: "AI can do the entry-level work, so why do we need entry-level people?"
This is a dangerous mistake.
What the Data Shows
Anthropic's March 2025 study found that hiring of younger talent into AI-exposed occupations has slowed by about 14%. Not a collapse — but a meaningful slowdown. And it's the juniors who are feeling it first.
Companies see reducing junior talent as the quickest path to ROI targets their boards are mandating from AI investments. At the same time, they're frantically paying top dollar for senior talent and anyone with "AI" in their job title.
The result is the hollowing out of the middle — and the slow erosion of the talent pipeline.
The Four Team Shapes
Steven Brovich outlined four organizational shapes in his AWS leadership talk:
| Shape | Description | Problem |
|---|---|---|
| Pyramid | Lots of juniors at the base, fewer seniors directing | Traditional, but inefficient |
| Diamond | Cut juniors, bulk up middle managers for AI oversight | The trap — no pipeline |
| Inverted Pyramid | 3-5 senior engineers with AI doing execution | Works for execution, but no learning path |
| Hourglass | Seniors at top, lean middle, juniors learning on the way up | The ideal — execution + pipeline |
The hourglass is the learning organization. It has execution at the top, a lean middle, and — critically — juniors learning the craft on the way up.
The 2034 Problem
Matt Garman, CEO of AWS, asked the question that every leader should be asking:
"How's that going to work when 10 years in the future you have no one that has learned anything?"
His answer: "You absolutely want to keep hiring kids out of college."
The companies who stop training juniors today don't have a talent shortage today. They have one in 2034 — which is four CEO cycles from now. No current CEO has to worry about it, which is exactly why this is going to be a massive problem.
Judgment Comes from Experience
AI absorbs the execution layer. What remains is judgment. But judgment only exists because somewhere, someone spent 10 years doing the execution and learning from the mistakes.
If we skip that entirely, we don't just have a talent pipeline problem. We have an expertise pipeline problem. And expertise takes a generation to build.
The Deskilling Trap
Brovich also warned about the deskilling trap:
"Juniors using AI can ship about 17% more code, but they understand 17% less of what they've actually shipped."
The people coming through your pipeline are getting faster and less grounded at the same time. If you're not intentionally building their understanding alongside their productivity, you're creating a generation of developers who can ship but can't debug, can't design, and can't judge.
What This Means for You
- If you're a leader: Protect your junior pipeline. Your competitive advantage in 2034 is the juniors you're hiring today, not the ones you're laying off.
- If you're a senior developer: Mentor juniors intentionally. Help them build the judgment that only comes from experience.
- If you're a junior: Seek out environments where you'll learn the fundamentals, not just ship code fast. The judgment you build now is what will make you valuable in 10 years.
- The hourglass is the goal. Execution at the top, learning at the bottom, and a deliberate path from one to the other.
Portions of this article are based on insights from Steven Brovich's talk "A leader's guide to advanced team structures in an agentic world" at AWS Events. You can watch the full talk here: A leader's guide to advanced team structures in an agentic world.