Here's the deal: companies are firing junior developers and handing their work to AI. But that work doesn't disappear. It just rolls uphill to the most expensive people in the building.

The "replace juniors with AI" strategy sounds brilliant in a board meeting. In practice, it's a false economy that burns out your best engineers.

The Hospital Secretary Problem

There's a well-known pattern in healthcare. Hospitals cut administrative staff to save money. Suddenly, doctors — the highest-paid people in the building — are filling out forms, scheduling appointments, and doing data entry.

The work didn't vanish. It just got redistributed to people who cost 5x more per hour.

That's exactly what's happening in software right now. Multiple companies have publicly reduced junior hiring, citing AI capabilities. The pitch is simple: "Copilot can do what a junior does."

Except it can't. Not without supervision.

Seniors Are Now Babysitting LLMs

Here's what actually happens when you replace a junior with an AI tool. A senior engineer prompts the LLM. They review the output. They catch the subtle bugs. They refactor the weird architectural choices. They fix the hallucinated API calls.

Senior engineers are increasingly reporting that they spend significant time reviewing and fixing AI-generated code. That's not leverage. That's a new job responsibility nobody signed up for. 🫠

→ Before: Senior architects systems, junior implements under guidance, senior reviews.
→ After: Senior architects systems, prompts AI, reviews AI output, fixes AI output, then reviews their own fixes.

You didn't remove the junior's workload. You removed the junior and gave a senior a worse version of the same task — one that looks done but requires forensic inspection.

The Hidden Cost Nobody's Tracking

The real damage isn't just salary arbitrage gone wrong. It's attention.

A senior fixing AI slop isn't designing systems. They're not mentoring. They're not making the architectural calls that actually move the product forward. You're paying principal-engineer rates for code-review grunt work.

And let me get to the real part that keeps me up at night: if the junior roles are the training ground, you cut them off and you're eating your seed corn. In five years, you'll have a generation gap with nobody ready to step into senior roles.

The pipeline doesn't refill itself. 🔥

The Honest Math

If you're a manager considering this trade, do the real math:

→ Junior salary: X
→ Senior time spent babysitting AI: Y hours × senior hourly rate
→ Opportunity cost of senior not doing senior work: enormous and invisible

That second line item never shows up in the "AI savings" spreadsheet. But it's real. Every senior who spends an afternoon debugging AI-generated garbage is an afternoon of system design that didn't happen.

What Actually Works

AI is a great amplifier for juniors, not a replacement for them. Give a junior developer AI tools and senior mentorship? Now you've got acceleration. The junior learns faster. The senior stays focused on high-leverage work. The AI handles boilerplate under human supervision at the appropriate pay grade.

That's the model that makes economic sense. Not "fire the cheap people and make the expensive people do their jobs plus a new meta-job."

---

The companies cutting junior roles aren't saving money. They're hiding costs in senior burnout and pretending the spreadsheet tells the whole story.

What's your experience? Are you a senior spending more time wrangling AI output than you expected? Or a junior watching doors close? I'd love to hear how this is playing out on your team.