Microsoft says AI is hollowing out junior engineers. The senior shortage lands in the early 2030s.

The warning about junior engineers everyone quoted, and the number everyone skipped

In February 2026, Microsoft’s Azure CTO Mark Russinovich and developer-relations VP Scott Hanselman published a paper in Communications of the ACM titled "Redefining the Software Engineering Profession for AI." Its central claim travelled fast: agentic coding tools give senior engineers a productivity boost while imposing what the authors call "AI drag" on early-in-career engineers, who don’t yet have the judgement to steer, verify, and integrate what the AI produces. Senior engineers get faster. Junior engineers, lacking the experience to catch what’s wrong, get slower, or get cut from headcount plans altogether.

Russinovich told reporters the pattern isn’t theoretical from where he sits: it comes up, he said, in basically every customer conversation Microsoft has. A Harvard study cited in the paper backs the anecdote with a number. After GPT-4 shipped, employment of 22-to-25-year-olds in AI-exposed roles, including software development, fell by roughly 13%, even as senior-role employment kept growing through the same period. Other figures making the rounds say something similar from different angles: entry-level postings down somewhere between 40% and 60% from their 2022 peak, and entry-level hiring at the fifteen largest tech employers down 25% in a single year.

Coverage of the paper (InfoQ, The Register, a clutch of trade newsletters) ran the same two beats: AI helps seniors and hurts juniors, and here’s Microsoft’s proposed fix. None of it answered the question that actually matters to someone running an engineering organisation today: when does this turn into a shortage, and is now the moment to act, or is the alarm premature?

Running the cohort math nobody ran

Hiring junior engineers is, among other things, a supply chain decision with a multi-year lead time. A junior hired this year doesn’t become a senior engineer this year. Career ladders differ by company, but most converge on a similar range: five to eight years from junior to senior, assuming steady growth and no extended break in service. That lead time is the entire mechanism behind the Russinovich-Hanselman warning, and it’s also what turns a vague worry into a dateable one.

Apply it to a worked example. Say an organisation hired 20 junior engineers in 2019 and, following the broader pullback, only 8 in 2023. If that organisation’s ladder runs six years, the 2019 cohort should be reaching senior level around 2025, and the thinner 2023 cohort around 2029. The gap between the size of those two cohorts is the shortage, and it’s visible four years before it shows up as a recruiting pipeline that suddenly can’t fill senior roles from inside.

Now apply the same logic to the actual industry-wide data. The steepest part of the entry-level pullback runs through 2022 to 2025: postings down 40 to 60% from the 2022 peak, with the sharpest cuts concentrated in 2023 and 2024, and the Harvard-measured AI effect layering on top of cuts that were already under way for unrelated reasons, including post-pandemic overhiring corrections and the sudden availability of cheaper remote talent. Run the smallest of those cohorts, roughly the 2023 to 2025 hiring classes, through a five-to-eight-year ladder, and the resulting shortfall window lands at approximately 2028 to 2033.

Why this doesn’t look like an ordinary hiring slowdown

Tech has had hiring slowdowns before: 2001, 2008, the 2022–23 correction. None of them produced this particular shape of argument, because they were demand shocks. Fewer roles, across the board, recovering when demand returned. What’s notable about the current pullback is that it didn’t move uniformly. Coverage of the 2026 job market describes something closer to a split: several of the largest enterprise technology companies kept growing junior headcount even as postings collapsed broadly across smaller companies and startups.

That split is the tell. A pure macro correction would hit large and small employers in roughly the same direction. A substitution effect, where a specific category of task (the kind junior engineers used to cut their teeth on) gets absorbed by tooling, would hit unevenly depending on how exposed each employer’s junior workload actually is, and on whether that employer has decided the long-term pipeline cost is worth paying. The 2026 data looks like the second story, not the first.

Three hiring postures, and only one of them is betting on the shortage

Most organisations, by the data above, have landed on the first posture without quite framing it as a bet. The second posture, hiring as before and hoping the drag is temporary, is arguably the riskiest of the three: it pays the productivity cost of AI drag today without doing anything to shorten the path to senior competence, and without the efficiency gains of posture one.

The third is what Russinovich and Hanselman are actually proposing, borrowed explicitly from medical education: pair early-in-career engineers with senior mentors at ratios of roughly three-to-one to five-to-one, embedded in real product teams rather than a training track, for an engagement meant to run a year or longer. The mechanism isn’t mentorship as a perk. It’s mentorship as the specific, budgeted activity through which a junior engineer builds the judgement needed to eventually verify AI output instead of just producing more of it under supervision.

The detail worth noticing: who’s actually asking for this

A LeadDev write-up of the preceptor proposal makes an observation worth sitting with longer than the headline numbers. Drawing on engineer Charity Majors’ experience across multiple companies, it notes that wherever junior hiring has resumed in the last few years, the push has tended to come from senior engineers asking for it, not from a leadership mandate handed down from above.

That’s a useful signal for anyone deciding which posture their own organisation actually falls into. If the case for hiring juniors again is being made loudest by the people who’d be doing the mentoring, that’s a meaningfully different situation from a recruiting team trying to hit a headcount-diversity metric on a slide, and it tends to produce a different kind of preceptor programme: one with an actual senior sponsor attached, not just a budget line.

What to do with this before the next planning cycle

A few moves follow directly from the math above, rather than from the generic instinct to "invest in junior talent":

• Treat the preceptor ratio as a budget line, not a cultural aspiration. If a senior engineer is expected to mentor three to five early-career engineers as part of their actual job, that needs to show up in their workload planning the same way an on-call rotation does, or it will quietly get deprioritised the first time a deadline slips.
• Track judgement debt the way the team already tracks technical debt. Flag work shipped by a junior engineer with AI assistance where that engineer would not have been able to catch a wrong answer unaided. That’s a countable signal, not a vibe, and it shows exactly where a preceptor pairing needs to focus first.
• Split junior assignments deliberately into two buckets: tasks with low AI-drag exposure that are still genuinely useful first assignments, and tasks that are pure AI-drag right now and should go to a senior, or to a junior paired tightly with one. Treating all junior work as interchangeable produces the worst version of both the first and second postures above.
• Run the organisation’s own cohort math, not the industry’s. What is the actual junior-to-senior ratio today, and what does the specific hiring pattern from 2022 to 2025 imply for the internal promotion pipeline by 2030? The industry-wide window of 2028 to 2033 is a starting estimate; an organisation’s own ladder length and hiring record will move it earlier or later.

The arithmetic is the easy part

The Russinovich-Hanselman paper will likely be remembered as the moment this argument went mainstream inside large engineering organisations. Whether the early 2030s actually arrive short on senior engineers depends less on what Microsoft proposes than on how many engineering leaders bother to run their own version of this arithmetic before then, while there is still enough lead time left for it to change anything.