Why AI will create more engineers, not fewer

Fundamental shifts in software engineering are expected within 12–18 months, transforming industries that rely on software. The software profession is not defined by typing or writing code; it is defined by solving problems while reducing complexity, minimizing maintenance, and delivering useful outcomes. AI can generate code, tests, scaffolding, API wiring, and boilerplate at high speed, but it cannot yet decide what to build, explain why it matters, or manage real-world tradeoffs. Engineers will increasingly act as generalist orchestrators who supervise AI agents that implement business logic, analyze logs, and propose architectural changes. Daily work will focus on mapping constraints and ensuring systems survive real-world conditions.

"Anyone who claims otherwise may have a bridge to sell you. But it's clear that fundamental shifts in software engineering will happen within that time, and that they will transform every industry that runs on software in the process. I've led software engineering at big tech companies like Microsoft, Snap and Google over the span of two decades. AI's always been in the conversation and the innovation lab, but the changes happening now are truly unprecedented in both speed and scale. We have the opportunity to achieve more in the next year than we have in the last 10."

"Many people who believe AI marks the end of software engineering misunderstand what the role actually is. The job has never been about writing code. It has always been about solving problems-and doing it in a way that reduces complexity, minimizes maintenance burden, and delivers something useful to the person on the other end. Code was the medium, not the purpose. That distinction matters now more than ever. AI agents can write code. They can generate tests, scaffold services, wire up APIs, and produce boilerplate at a pace no human can match."

"What they cannot do-at least not yet-is decide what to build, understand why it matters, or navigate the tradeoffs that determine whether a system survives contact with the real world. That remains the engineer's job. It always has been. The era of the specialist coder-fluent in one language, deeply embedded in one stack-is giving way to the generalist orchestrator. Engineers will increasingly supervise fleets of agents that write business logic, generate tests, analyze logs, and suggest architectural changes."

Read at Fast Company