FC Health Index1,428.60+0.42%Novo NordiskDKK 812.4+1.10%Intuitive SurgicalUSD 546.9−0.30%EU AI Act — Art. 6in forceM+7FDA 510(k) AI clearances (YTD)312+18 w/wNHS AI Diagnostic Fund£123mcommittedKarolinska trials open48+2Reimbursement CPT codes (AI)17+1 QFC Health Index1,428.60+0.42%Novo NordiskDKK 812.4+1.10%Intuitive SurgicalUSD 546.9−0.30%EU AI Act — Art. 6in forceM+7FDA 510(k) AI clearances (YTD)312+18 w/wNHS AI Diagnostic Fund£123mcommittedKarolinska trials open48+2Reimbursement CPT codes (AI)17+1 Q
Thursday, 17 September 2026 · Oslo · London · New York

Future of Work · Analysis

The Missing Class of Software Engineers

Tech companies stopped training entry-level developers two years ago. The structural deficit will become obvious by 2029, when senior ranks run dry.

A high-contrast black and white shot of an empty open-plan office desk with two unlit monitors and an abandoned desk chair.
A high-contrast black and white shot of an empty open-plan office desk with two unlit monitors and an abandoned desk chair.

Independent coverage

A

By Andrew Singer

Contributing Writer — AI / Data / Business · Freelance

Edited by Ingrid Sørensen

Published 6 September 2026

6 min read

Evidence: Analysis

Entry-level software engineering roles declined steeply over the past two years. Tech firms reduced headcounts, cut graduate programmes, and paused campus recruitment. The shift was rapid, quiet, and broadly welcomed by balance-sheet analysts.

The rationale appeared simple at the time. Generative AI tools promised to automate basic code generation. Senior engineers, freed from reviewing novice pull requests, were expected to handle the remaining load on their own.

The apprenticeship model broke quietly

Software engineering was never taught fully in lecture halls. Computer science degrees provide theory, but production systems demand practical experience. New developers learned by breaking small services, fixing minor bugs, and sitting beside veterans.

That informal apprenticeship came at a cost. Senior developers spent significant working hours answering questions, checking edge cases, and guiding architectural instincts. By cutting junior roles, engineering departments removed that overhead and reported immediate efficiency gains.

The illusion of autonomous productivity

Modern coding assistants make individual contributors faster at writing boilerplate. A single developer can produce the output of three junior engineers in a fraction of the time. Yet speed of generation is distinct from system comprehension.

Tools do not explain why an architecture fails under unpredictable load. They do not teach an engineer how to weigh technical debt against product deadlines. When novices do not practice those trade-offs early, they do not develop the judgement required for leadership.

Five years to an architectural vacuum

A career progression in software spans predictable stages. An engineer typically requires five to six years to grow from writing syntax to designing distributed systems. The freeze that began around 2023 will reveal its true cost by 2029.

By then, the current generation of senior staff will begin to age out, retire, or move into management. There will be almost no domestic mid-level cohort ready to replace them. Companies will find themselves bidding aggressively for a shrinking pool of aging specialists.

Treating engineering recruitment as an adjustable quarterly expense ignored the lag time of talent development. Codebases do not maintain themselves. By cutting the bottom rung of the ladder, the industry guaranteed a structural shortage it cannot quickly patch.

"When novices do not practice those trade-offs early, they do not develop the judgement required for leadership."

Published 6 September 2026