Amazon Engineers Become Code Reviewers as AI Reshapes AWS Development
From Code Writers to Code Reviewers
Amazon’s developers are undergoing a fundamental identity shift. According to multiple reports, AWS engineers now spend 55% of their time reviewing AI-generated code rather than writing original code. They’re effectively becoming quality controllers rather than creators. And the company is expecting them to absorb additional responsibilities — including technical writing and documentation — “with AI tools’ assistance.”
Amazon CTO Werner Vogels coined the term “renaissance developer” to describe this new role — professionals who combine AI tools with human judgment, systems thinking, and domain expertise. Engineers must “stop viewing themselves solely as writers of code and start becoming solvers of true human problems,” Vogels wrote. AWS CEO Matt Garman described it as “deconstructing a problem, deciding what to build, pulling it together, looking at the code that comes back and deciding it’s not quite exactly what you want.”
Project Dawn: 30,000 Jobs and Counting
This role transformation is happening against the backdrop of Project Dawn, Amazon’s massive corporate restructuring. The company has cut approximately 30,000 corporate roles in two waves: 14,000 in October 2025 and 16,000 in January 2026. Forty percent of recent cuts targeted engineering roles — software engineers comprised roughly one-third of Washington State’s 2,198 layoffs.
CEO Andy Jassy has been blunt: “In the next few years, we expect that this will reduce our total corporate workforce as we get efficiency gains from using AI extensively across the company.” HR chief Beth Galetti described the goal as “reducing layers, increasing ownership, and removing bureaucracy.” Some analysts predict layoffs could hit 30,000 roles by May 2026.
The Internal AI Mandate
Amazon set a target for 80% of developers to use AI for coding tasks at least once a week, and 89% of engineers now use AI daily. The primary tools are Amazon Q Developer (code completion, reviews, documentation) and Kiro, an “agentic” AI coding tool that can act autonomously. AI tools have reduced original coding time by 40%, while handling unit testing, documentation, and code reviews.
There’s significant internal friction. Engineers revolted over restrictions on third-party tools like Anthropic’s Claude Code, arguing Amazon’s internal tools (Kiro, Q Developer) disrupt workflow. Kiro even caused at least two AWS outages, including a 13-hour disruption in December when the AI decided to “delete and recreate the environment.” Despite this, Amazon pushed ahead.
Engineers Push Back
Over 1,000 Amazon employees signed an open letter warning the company’s AI strategy risks “staggering damage to democracy, to our jobs, and to the earth.” Engineers cited: “Amazon is forcing us to use AI while investing in a future where it’s easier to discard us.” Internal surveys show 42% of engineers worry about losing their architectural design skills.
Some engineers describe the work as feeling “more like warehouse labor than traditional coding” — intense pressure to produce code faster via AI, with implied threats to job security for those who resist. The irony is hard to miss: Amazon, a company whose warehouse workers have long complained about dehumanizing automation, is now applying the same pressure to its white-collar engineers.
The Contradiction at the Top
Here’s the part that doesn’t quite add up. AWS CEO Matt Garman publicly called replacing junior developers with AI “one of the dumbest things I’ve ever heard.” Yet the parent company is aggressively cutting engineering roles while mandating AI adoption. Jassy says “AI will change jobs, not end them” — while 30,000 people lose their jobs. The gap between the rhetoric and the reality is where the anxiety lives.