Memo: Amazon SVP Dave Treadwell says junior and mid-level engineers now require more senior engineers to sign off any AI-assisted code changes, after outages
Financial TimesRafe Rosner-Uddin
Context & Ripple Effects
Amazon had already been pushing engineers toward AI use while raising output expectations, according to reports of increased pressure to use AI tools. More recently, AWS developers were reportedly being asked to take on new roles with AI assistance and complete technical-writing work, extending AI's role beyond code generation.
The new sign-off rule is therefore a corrective to an AI-adoption push, not a retreat from it: Amazon is adding a human control point after outages exposed the operational cost of insufficient review.
First-order effects
Junior and mid-level engineers must route AI-assisted code changes through more senior engineers, making senior review an explicit release gate for those changes.
Senior engineers take on greater accountability and review workload, while affected developers lose some autonomy and may face slower deployment cycles.
Second-order effects
Teams will need to rebalance engineering capacity toward code review, testing, and incident prevention; the practical speed gains from AI-assisted coding may narrow where senior review is scarce.
The policy reinforces demand for AI coding workflows that make provenance, testing, and reviewability easier to establish, rather than optimizing only for generated-code volume.
Third-order effects
If replicated across large engineering organizations, AI coding adoption is likely to be governed as an operational-risk process: faster authoring paired with stronger human approval and audit controls.
This points to a more differentiated engineering labor model in which senior judgment becomes a limiting resource for scaling AI-assisted development, though the durability of that constraint depends on whether assurance tooling improves.
The trend: Enterprise software teams are shifting from measuring AI coding by output alone to embedding it in controlled, accountable production workflows.
Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is “part of normal business.” The briefing note describes a trend of incidents with “high blast radius” caused by “Gen-AI assisted changes” for which “best practices and safeguards are not […
after this went wide, Amazon vociferously shat upon this story — which detailed the company's internal issues with humans using AI tools and accidentally taking down some of its services now they're making changes to deal with the problems that comms said they werent having
Maybe it's my bad luck, but in the last week I hit major bugs on LinkedIn, Instagram, Amazon, Chrome, VS Code, TikTok, Slack, WhatsApp, and more. It feels the SDLC of yesteryear is not fit for the age of AI.
genie is out of the bottle everyone hitting the magic button button puts your brain in a state of laziness that seeps into all your processes and they get skipped we talk about this all the time and still our team is struggling with it
AI code is breaking Amazon systems at an increasing rate and it's such a problem that junior and mid-level engineers now aren't allowed to commit AI-assisted code without a senior engineer reviewing it. Is anyone surprised?
more #hugops to my Amazon counterparts maybe this is the moment to invest properly in reliability engineering and stop putting SDEs oncall overnight for mission critical services
You thought the alignment problem was the real problem of the AI era. It was always the verification problem. Do you have the skills to know if the output is correct? If not, you FUBAR.
> Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. Looks like Code Review tools are going to be a good business, and not the version Anthropic is shipping. You want something more like a precision knife vs a hammer. Command is a …
there will be a cultural change at many software organizations soon where people declare bankruptcy on understanding the code they're committing. sooner or later this will cause a systems failure that will be harder to debug than most, but will be resolved anyways
Many of my commenters are probably saying I told you so right about now. — The reality is that increasing coding velocity without also increasing your ability to review and test the code at that scale is a recipe for disaster.
Great reporting from @rafeuddin.ft.com on Amazon's misadventures with AI coding (which have coincided with big headcount reductions) www.ft.com/content/7cab... [image]
Amazon holds engineering meeting following AI-related outages: — Ecommerce giant says there has been a ‘trend of incidents’ linked to ‘Gen-AI assisted changes’ — www.ft.com/content/7cab... archive: archive.is/wXvF3 — l o l
RE: https://social.coop/... Lmao. Gen AI is causing outages at AWS and Amazon causing business income loss. So now all AI created code needs senior developers to check it twice. So how is this saving time? #ai #llm #aws