The real risk of skipping the junior tier entirely
Senior engineering judgement is built through years of seeing small decisions go wrong on real systems with real consequences. If that formative experience disappears because entry-level implementation work is fully automated away, organisations are quietly borrowing against their future senior bench with no plan to repay it.
This is a multi-year problem that won't show up on any quarter's balance sheet, which is exactly why it gets deprioritised.
What the redesigned entry-level role looks like
Juniors reviewing and correcting agent-generated code, under close senior mentorship, learn judgement faster than juniors writing boilerplate alone ever did — because they're exposed to a volume and variety of code far beyond what they could write themselves in the same time. The job becomes reviewer-in-training rather than implementer, which is a real redesign, not a demotion.
Stop hiring juniors now, and you're not saving a training cost — you're deferring a staffing crisis to the exact point you'll need senior engineers most.MNB Software Engineering Practice
Key actions
- Redesign the junior role around reviewing agent output, not just writing code
- Pair juniors with close senior mentorship, not isolated agent supervision
- Track judgement development explicitly, not just ticket throughput
- Treat the senior pipeline as a multi-year investment, not a quarterly cost line