Amazon’s cloud chief says AI won’t kill software engineering jobs, company plans to hire...

As fears mount across the technology industry that artificial intelligence could hollow out white-collar employment, Amazon AWS CEO Matt Garman is projecting a different message: software engineers are not becoming obsolete, but the nature of their work is undergoing one of the most significant transformations in decades.

Speaking at Amazon Web Services' "What's Next with AWS" event, Matt Garman rejected the growing narrative that AI coding systems will sharply reduce the need for developers.

"I can tell you we are hiring just as many software developers as we ever had inside of Amazon," he said. "And in fact, I see the demand for that really accelerating."

The comments come when debate about the future of software is at an all-time high, as the adoption of artificial intelligence accelerates. Across Silicon Valley, executives are pouring hundreds of billions of dollars into AI infrastructure while simultaneously cutting jobs, flattening management structures, and automating functions once handled by humans. The contradiction has fueled deep unease among workers who increasingly see AI not merely as a productivity tool, but as a direct competitive force.

That anxiety has intensified in recent months as several members of the Magnificent Seven, including Meta Platforms and Microsoft, announced significant workforce reductions while increasing AI spending. Earlier this year, Amazon itself carried out layoffs affecting roughly 16,000 corporate employees, even as it expanded investments in generative AI, cloud infrastructure, and automation technologies.

Against that backdrop, Amazon's decision to maintain its software engineering recruitment pipeline is notable. The company said it plans to bring in more than 11,000 software engineering interns and early-career developers globally in 2026, a figure the company said aligns with previous years.

"Amazon remains committed to our internship program as an important pathway to finding the next generation of leaders and builders," a company spokesperson said.

Yet even as Amazon insists that demand for developers remains strong, Garman acknowledged that the definition of software engineering is rapidly changing.

"The jobs will be a little bit different," he said. "Being an expert at being able to author a Java code snippet is going to be less valuable in the future than it was maybe a couple of years ago."

That statement captures a broader structural shift underway across the industry. For decades, technical expertise was often measured by a developer's ability to manually write, optimize, and debug code. AI systems are now automating a growing share of those tasks. Tools from companies such as Anthropic, OpenAI, and GitHub can already generate large blocks of functional code, identify vulnerabilities, and even build simple applications with limited human intervention.

That has triggered increasingly blunt warnings from industry insiders. Boris Cherny said earlier this year that the title "software engineer" could eventually disappear altogether. Martin Casado argued that software engineering is being "disrupted as a discipline," while venture capital firms are increasingly backing startups built by remarkably small teams using AI-assisted development.

The emergence of so-called "10-person unicorns" and lean AI-native startups has reinforced fears that large engineering teams may eventually become economically unnecessary for many software products. Investors increasingly view AI-assisted coding as a way to compress labor costs while accelerating development cycles.

Still, Amazon's stance reflects a competing view gaining traction among major cloud providers and enterprise technology companies: that AI changes the hierarchy of engineering skills rather than eliminating the profession itself.

Under this framework, routine coding becomes less valuable, while higher-order skills become more important. Engineers are expected to spend less time manually writing code and more time designing systems, orchestrating AI tools, managing infrastructure, and solving complex business problems.

Garman pointed directly to that evolution, arguing that broader problem-solving ability and customer understanding will matter more than narrow programming expertise. That shift is especially critical for Amazon Web Services, where enterprise customers increasingly depend on complex cloud environments integrating AI workloads, cybersecurity systems, and distributed computing infrastructure.

In such environments, AI can generate code, but human engineers are still needed to verify reliability, manage risk, optimize architecture, and understand the operational consequences of failure. The growing complexity of enterprise AI systems may, paradoxically, increase demand for highly specialized technical talent even as lower-level coding tasks are automated.

The labor market is already beginning to reflect that divide. Hiring for entry-level and generalist software roles has slowed across parts of the industry, while demand for engineers with expertise in AI infrastructure, machine learning operations, distributed systems and cloud security remains elevated.

That divergence could reshape the economics of technology employment. Instead of eliminating engineering jobs outright, AI may reduce the number of junior developers required while concentrating value among more experienced engineers capable of overseeing increasingly autonomous systems.

The timing is also strategically significant for Amazon. AWS remains locked in an escalating competition with rivals such as Microsoft and Alphabet Inc. to dominate enterprise AI infrastructure. Maintaining a strong engineering pipeline is therefore not only about labor needs, but also about sustaining innovation capacity in a market where speed of execution is becoming critical.

There is also a reputational dimension. As layoffs spread across the sector and AI-driven efficiency becomes a dominant corporate theme, companies face growing scrutiny over whether their public assurances about workers align with internal priorities. By publicly reaffirming its commitment to hiring engineers, Amazon is attempting to distinguish augmentation from replacement, even as automation becomes more deeply embedded across its operations.

Still, the broader trajectory appears increasingly irreversible. AI is steadily commoditizing portions of software development that once required years of specialized training. The profession is not disappearing, but it is becoming more strategic, more systems-oriented, and potentially smaller at the entry level.

For software engineers, the implication is becoming clearer: future value may depend less on writing code line by line and more on directing, validating, and integrating systems where AI increasingly performs much of the coding itself.