AI at Amazon: A case study of brittleness
surfingcomplexity.blog
surfingcomplexity.blog
I remember vividly the challenge of building centralized infra for ML at Amazon: we had to align with our organization's "success metrics" and while our central team got ping ponged around, and our goals had to constantly change. This was exhausting when you're trying to build infra to support scientists across multiple organizations and while your VP is saying the team isn't doing enough for his organization.
Sadly our team got disbanded eventually since Amazon just can't justify funding a team to build infra for their ML.
Sounds like they didn't plan it out correctly. It should have been done in phases, one team at a time, starting with the Alexa team, or the smallest team with the smallest amount of effort as a test bed, while keeping the other teams informed in case they have suggestions or feedback for when their turn comes along.
I remember being in the office when GPT2 dropped and thinking the entire Alexa Engine/skill routing codebase became outmoded overnight. That didn't really happen, but now that MCP servers are so easy to build I'm surprised Alexa doesn't just use tool-calling (unless it does in Alexa+?)
if(tenant == "spotify") { ...
and everything else was downhill from there.The rest of the description on how Amazon operates is quite accurate. Impossible for anyone to do anything meaningful anymore.
If in Q2 2025 a company like AAPL or AMZN decides to invest in a current top of the line neural network model and spend 18 months to develop a product, whatever they develop might be obsolete when it is released. Holds for OpenAI or any incumbent -- first mover advantage may be neutralized.
Secondly there are a lot of problems in ambient computing. Back in the early 00's I often talked with an HCI expert about ideas like "your phone (pre-iPhone) could know it is in your backpack" or "a camera captures an image of your whole room reflected in a mirror and 'knows what is going on'" and she would usually point out missing context that would make something more like a corporation that gives bad customer service than a loyal butler. Some of Alexa's problems are fundamental to what it is trying to do and won't improve with better models, some of why AMZN gave up on Alexa at one point.
That's not to say that Alexa and others can't be useful, but just not to enough people that it justifies the R&D cost.
It would be one thing if they were just adding extra "smart home" features to connect new terminals. I can see benefit of some of the smart screen calendar and weather things. No, they seem dead set to completely kill what they had.
These are obviously what voice assistants should do, the research was just not there. Amazon was unwilling to invest in the long-term research to make that a reality, because of a myopic focus on easy-to-measure KPIs. After pouring billions of dollars into Alexa. A catastrophic management failure.
Edit: Oh, you wrote "verbal" that seems weird to me. Most people I know certainly don't want to talk to their devices.
If I'm alone I don't mind talking if it is faster, but there is no way I'm talking to AI in the office or on the train (yet...)
When is talking faster than text? I only ever use it when my hands are tied (usually for looking up how to do things while playing a video game).
People talk at about 120WPM - 160WPM naturally, few can type that fast which is why stenographers have a special keyboard and notation.
As such I can maintain about five minutes of slow pace before giving up and typing. I have to believe others have similar experiences. But perhaps I'm an outlier.
I explore the ideas more in a post at https://meanderingthoughts.hashnode.dev/lets-do-some-actual-... but the tl;dr is ~24-32GB of VRAM in a server shoved in a basement can do a lot. Imagine a machine that is fully owned by the user with no corporate spying. It can listen 24/7 to everything in the house, using technology like wifi location sensing it knows what room people are in (it is a thing now!) and can relay messages for a person to the closest speaker.
Even 8B parameter LLMs are great at ambiguous inputs, and new TTS models are weighting in under 1B parameters.
Connecting the LLM up to everything a person wants to do is the real issue. Homekit integrations exist, but Homekit isn't exactly a mass consumer technology. What RabbitOS aims to do is IMHO the proper path: Drive an android phone to accomplish tasks.
> And most importantly, there was no immediate story for the team’s PM to make a promotion case through fixing this issue other than “it’s scientifically the right thing to do and could lead to better models for some other team.” No incentive meant no action taken.
Oof!
But in a cut throat environment, you can't afford to not move the corporate metrics in quarterly reviews. Otherwise you will get pipped or fired
sounds like late stage capitalism
If you're going to sell T shirts, then sure, have quarterly goals.
The issue provided in the example is about helping other teams out without an expectation of a reward, not about short term vs long term gains.
The predictable unit production/sales way of management works for duplicatable, repeatable goods.
Yes. Because with socialism and communism the management cares about everyone’s benefits and not their own skin?
Everyone at Amazon is focused on AI right now. Internal and external demand for GPU resources and model access is off the charts. The company's trying to provide enough resources to do research, innovate, and improve business functions, while at the same time keeping AWS customers happy who want us to shut up and take their money so they can run their own GPUs. It's a hard problem to solve that all the hyperscalers share.
That explains the lack of progress on anything else on the other services....
It's pretty clear that LLMs with action hooks were going to take over from the old bespoke request->response methods so i guess they were trying to make sure there was no old guard holding on in the changeover. Only just now are the Alexa+ and Google home Gemini integrations becoming available to pick up where they dropped off in 2023.
Apple had a few Siri layoffs but it seemed to keep the ship steady. It'll be interesting to see which was the better long term approach though.
I'm curious how you came to this conclusion against Assistant and Alexa teams. It isnt like Assistant & Alexa shutdown completely, and Siri was uniquely left alone.
Siri's missteps are well documented. If anything, from the quality & speed with which the product is evolving, it seems like Siri might be more resource constrained.
From my perspective, one of the core issues was cultural. The Alexa teams were often staffed by long-timers with substantial RSU grants, many of whom appeared more focused on preserving internal influence and career security than driving bold external partnerships or innovation. It indeed felt less like a team pushing the envelope, and more like a collection of fiefdoms guarding their territory.
In the end, it was a missed opportunity—not just for Alexa, but for Amazon to play a central role in the connected car revolution.
- two competing orgs via Brain and DeepMind.
- members of those orgs were promoted based on ...? Whatever it was, something not developing consumer or enterprise products, and definitely not for cloud.
- Nvidia is a Very Big Market Cap company based on selling AI accelerators. Google sells USB Coral sticks. And rents accelerators via Cloud. But somehow those are not valued at Very Big Market Cap.
Of course, they're fixing some of those problems: brain and DeepMind merged and Gemini 2.5 pro is a very credible frontier model. But it's also a cautionary tale about unfettered research focus insufficiently grounded in customer focus.I got the exact opposite takeaway: despite Amazon and Google being pioneers in related areas, both failed to capitalize on their headstarts and kickstart the modern AI revolution because they were hobbled by being grounded in customer focus.
The voice recognition is at a whole nother level, much much faster. Controlling lights is easily an entire second faster.
The TTS upgrade is a trip. She sounds younger and speaks faster.
How long time did it used to take VS how long time does it take now? I'm not sure "an entire second faster" is sarcasm here, big improvement or what.
I think the voice recognition is async now. It's streaming the data to a model. Before it would wait until the command was finished then send the .wav file off to a model.
Humans on the other hand start processing the moment there's a response and will [usually] respond immediately without "thinking", or if they are thinking, they will say as much, but still respond quite quickly.
I just use the Clapper from the 1970s.
https://www.amazon.com/Clapper-Activated-Detection-Appliance...
2. I tried landscape lighting once. The local fawna chewed it to bits. I decided I didn't need it.
3. I don't need to control the lights when I'm not home.
4. I have seriously no need to light according to the seasons.
Sure, a more automated system would be great for disabled people. But I'm not disabled, and intend to lift my sorry heiny out of the chair as long as I am able to.
Replaces a phone in many cases.
Every ex-Amazon employee I’ve worked out talked about their burnout culture.
They under-compensate compared to their peers and as this article touches on with the discussion about customer focus, their corporate culture is the most draconian and abnormal.
I did an early stage Amazon interview and they basically wanted me to memorize every detail of their company culture and relate every single one of those aspects to a piece of work I did in the past. They wanted me to demonstrate that I had essentially joined their cult before I even had the opportunity to join it!
I have no idea how someone is supposed to honestly complete that interview process without outright lying.
Probably one of those things which are actually perfectly fine trade-offs, operational challenges and in no way causal to the demise. If Alexa had found a market, the same article would probably be called "AI at Amazon: a case study of <insert management buzzword>" and explain to us how the same processes paved the path to success.
This introduced an almost Darwinian flavor to org dynamics where teams
scrambled to get their work done to avoid getting reorged and subsumed into
a competing team.
To the extent that an organization is so wealthy and vast that it can fund redundant efforts, isn't getting reorged into the "winning" team a good thing?"In the paper Basic Patterns in How Adaptive Systems Fail, the researchers David Woods and Matthieu Branlat note that brittle systems tend to suffer from the following three patterns:
- Decompensation: exhausting capacity to adapt as challenges cascade
- Working at cross-purposes: behavior that is locally adaptive but globally maladaptive
- Getting stuck in outdated behaviors: the world changes but the system remains stuck in what were previously adaptive strategies (over-relying on past successes)"
Painfully apt.
The other 2 it's not clear if there are symptoms universal across economies.