Up to 250 people in the division that builds the Kindle, the Echo and Alexa were told by text message before sunrise on Wednesday that their jobs were gone, and most of them wrote software for a living. The day before, Amazon had circulated an internal memo telling its engineers to embrace AI or risk being left behind. The company never announced any of it. It confirmed the cuts only after a Reuters reporter asked, then declined to say how many people were affected.
Twenty-four hours. That is the entire distance between the memo and the message.
On Tuesday, 27 October, Amazon put an internal September note in front of its software development engineers. On the morning of Wednesday, 28 October, the notifications went out. Reuters reported the cuts and the way they were delivered: up to 250 roles in Devices and Services, most of them software development, dispatched by text and email at an hour when nobody is awake to argue. Amazon confirmed the reductions only after being asked about them, and a spokesperson would say only that a small number of roles had been eliminated for efficiency and to align with the product roadmap.
The same Wednesday, the unit unveiled five new Alexa-powered products: a redesigned Echo Show 16, a photo frame, and a bedside clock among them. In the weeks before, it shipped new Kindle e-readers and tablets. The business was healthy enough to keep announcing hardware and lean enough, in the same news cycle, to cut the people who build the software that runs on it. The Next Web noted the timing: this was a layoff that arrived in the middle of the unit’s best launch season, not at the end of a bad quarter.
Cherie Robinson — The Only Name on the Message Belonged to the Person Sending It
The notice carried a signature. Cherie Robinson, a vice president of human resources inside devices and services, wrote to staff that Amazon had completed what she described as a thorough review of its structure. That is the whole official account: a review, a small number of roles, a product roadmap. No team list, no project count, no explanation of why the review landed on software developers in the one unit whose software had just shipped.
The 250 do not have names, because nobody published them. The figure itself is a ceiling, and it came from a person familiar with the matter rather than from the company. The Federal logged the mechanics: the notices went out by email and text early on Wednesday morning, the confirmation came only after the wire asked, and no number was attached to it.
A review is what a company calls a decision after the decision has been made. The review is the receipt, not the reasoning.
The September Memo — Amazon Named the Risk Correctly and Handed It to the Wrong People
Business Today obtained the memo’s substance, and it is a more interesting document than the layoff notice. Sent to software engineers in September and published by the company the day before the cuts, it tells them to adopt AI in service of real customer problems rather than to inflate usage numbers. Its warning is blunt: learn this or risk being left behind. It also concedes something most AI mandates deny, which is that token consumption, adoption rates and the sheer volume of code changes prove nothing about productivity, and can raise costs while adding complexity.
Read those two ideas together and the company’s logic becomes visible. AI adoption is a professional obligation, a thing engineers owe the business. And the efficiency it produces is a reason the business needs fewer of them. The people who complied fastest wrote the strongest case for their own removal, and then the removal arrived by text.
Note what the memo does not say. It never promises that adopting AI protects a job. It only promises that refusing it carries a penalty. Those are different sentences, and every engineer who read the first meaning into the second one now has a phone full of evidence.
Embrace the change, the memo said. The change embraced back, briefly, and then moved on.
Andy Jassy — You Cannot Remove Fifty-Seven Thousand Corporate Jobs and Keep Calling Each Batch Small
Andy Jassy runs a company that has now cut more than 57,000 corporate roles since 2022, roughly 16 percent of its corporate workforce. Fourteen thousand went in October last year. Sixteen thousand followed in January. Fewer than a thousand came out of the retail side earlier this month, hitting customer service and marketplace support staff in the United States, Britain and India. Now 250 more, in hardware.
Each tranche has its own reasonable-sounding sentence. Small number of roles. Structural review. Better alignment. Individually, any one of them can be defended in a shareholder letter. In aggregate they describe a reclassification: a company that once sold software expertise as its future is steadily converting the people who held that expertise into a line item it no longer wants to carry.
The retail cuts landed during Prime Big Deal Days. The devices cuts landed during a launch week. There is no quiet month left to schedule a layoff into, which is precisely why companies have stopped scheduling them at all.
Three Hundred Thousand — Amazon Still Wants Human Hands, Just Not the Ones That Write Code
Amazon said this month that it will hire more than 300,000 people in the United States for the holiday season, up from 250,000 a year earlier. Almost all of those jobs sit in warehouses and delivery, where a human body is still the cheapest option for picking, packing and driving the last mile.
The company is, by the same reporting, on course to put as much as 220 billion dollars into AI this year. That is the trade in one sentence: a quarter of a thousand software salaries out, a nine-figure sum a day into the systems that are supposed to make the next quarter of a thousand unnecessary.
That is the actual shape of this transition, and it is worth saying plainly. The labour Amazon is adding is physical. The labour it is subtracting is cognitive and well paid. A company can do both in the same month without a hint of embarrassment, because the two workforces have never been in the same budget conversation.
The warehouse worker should not take comfort from this. The classification “too physical to automate” is a temporary status, not a protected one. It is the same assurance that software testers once received, and customer service representatives after them, and marketplace support staff earlier this month.
The safe job is only ever the job nobody has gotten around to automating.
The Disclosure — A Layoff You Have to Ask About Is Not an Announcement
There was no press release for the devices cuts. No all-hands, no blog post from a chief executive, no investor note. There was a wire service asking a question and a spokesperson confirming the answer. The Next Web’s account makes the sequence plain: the cuts were confirmed after Reuters inquired, and no number was offered even then.
This is now standard practice, and it deserves to be named as such. Layoffs are disclosed the way security breaches are disclosed: quietly, incompletely, and only to the party who noticed. The public learns the ceiling from an anonymous source and the company learned to call the floor a roadmap decision. Meanwhile the third-quarter results were due after Thursday’s closing bell, which is a fine week to have a number arrive without a headline attached to it.
A company that will not say how many people it let go has not been transparent with a smaller font. It has simply declined to answer and let a reporter carry the question.
The 250 — Their Severance Is a Number and Their Visa Clock Is Not
For the engineers involved, the arithmetic is domestic and immediate. Seattle and Bellevue rents do not adjust to a severance schedule. A mortgage does not read an email. And for the ones working in the United States on an employer-sponsored visa, the real clock is measured in weeks, not months: lose the sponsor, and the search for a new one becomes the only job that matters.
Industry-wide, more than 135,000 technology jobs have been cut this year. Those people spent the past year being told that the technology they were building would change everything, and they were right. It changed their status from employee to line item in under a day, in a text message, before the coffee was on. The company’s official position is that this was a small number of roles. It was, from the company’s side of the ledger. From the other side it was the whole number.
The memo said the risk was being left behind. The risk, it turns out, was being early.
Sources: Reuters, The Federal, Business Today, The Next Web.