Amazon’s “Project Dawn” cuts 30,000 jobs while AWS loses its community champion

7 min read Original article ↗

An accidental email revealed the scope of Amazon’s workforce purge. For thousands of cloud professionals, the news hit personally.

JP Caparas

Press enter or click to view image in full size

“The world’s largest startup”, AWS, is at it again.

A few hours ago, Jason Dunn posted a single emoji to LinkedIn: 💔

No explanation. No context. Just a broken heart.

Within an hour, hundreds of concerned followers had reacted. About a hundred comments flooded in. The AWS community knew exactly what it meant because they’ve been reading the headlines.

The man who had built and nurtured the AWS Community Builders program, the person who had touched tens of thousands of developers, architects, and cloud professionals the world over (and yes, that includes New Zealand), was gone.

Press enter or click to view image in full size

“I don’t know what to think or feel seeing all the world that you helped to build,” wrote Suzana in the comments, “a world based on respect, friendship, trust, mutual support, and community growth, crumble, and like sand, slip through my fingers.”

This wasn’t just another tech layoff. This was personal.

The accidental reveal

The day before Dunn’s post, something went wrong at Amazon.

Spectacularly wrong.

On January 27, 2026, an internal email about “Project Dawn” was accidentally sent to employees. The message, intended for a small group of executives, revealed the scope of what was coming. Colleen Aubrey, Amazon’s senior vice president of AWS Applied AI Solutions, had sent a calendar invite that wasn’t supposed to go out yet.

The chaos inside the internal Slack channels was immediate, with Business Insider quoting one employee saying:

“Well, if you needed solid proof that tomorrow is legit, the project dawn email is it,” one employee wrote. “Looks like they wanted to use AI to send an email tomorrow and instead it sent a calendar invite today.”

Infuriating if that were the truly case.

The irony was thick. A company betting its future on artificial intelligence had just been embarrassed by what appeared to be an AI scheduling mishap (or accounts of an EA accidentally adding an entire distribution list prematurely). But the real story wasn’t the technical failure. It was what the email confirmed.

Amazon was about to cut 16,000 jobs.

The numbers

Here’s the scale.

In October 2025, Amazon laid off 14,000 workers. Now, just three months later, another 16,000 are being shown the door. That’s roughly 30,000 people since autumn. About 10% of Amazon’s corporate workforce of 350,000.

Press enter or click to view image in full size

This isn’t new territory for Amazon. The company cut 27,000 jobs in 2023 alone: 18,000 in January, another 9,000 in March. Add it all up, and Amazon has eliminated more than 60,000 corporate positions since 2022.

Amazon has eliminated more than 60,000 corporate positions since 2022. At some point, “efficiency” becomes a euphemism for something else entirely.

The scale is staggering.

But numbers don’t capture what’s actually being lost.

The heart of the community

Brian, a longtime AWS community member, put it simply: “Jason has been the heart and soul of the AWS Community Builders program. As such he has touched literally tens of thousands of lives, enriching both them and the larger technical community.”

The AWS Community Builders program isn’t just a marketing initiative: it’s a global network of developers, architects, and cloud practitioners who share knowledge, mentor newcomers, and build the ecosystem that makes AWS valuable. That trust has now eroded.

Jason Dunn ran it. He was, in the words of one commenter, “the alma mater of the AWS community.”

Another wrote: “You built something epic that changed lives around the world.”

An outpouring of support like no other.

This is what gets lost in layoff announcements. The spreadsheet says “headcount reduction.” The reality is that someone who spent years building relationships, fostering talent, and creating genuine community is suddenly gone.

Get JP Caparas’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

And the people who depended on that community feel it immediately.

Press enter or click to view image in full size

The world’s largest startup

Amazon CEO Andy Jassy has been very clear about his vision. In internal communications, he’s described wanting Amazon to “operate like the world’s largest startup. That means having a passion for constantly inventing for customers, strong urgency (for most big opportunities, it’s a race!), high ownership, fast decision-making, scrappiness and frugality.”

Scrappiness and frugality. Those words do a lot of heavy lifting when you’re talking about eliminating tens of thousands of jobs.

The layoffs are part of a broader transformation at Amazon. In January 2025, the company mandated a five-day return-to-office policy, ending the hybrid work arrangements that had become standard during the pandemic. The message was clear: the era of flexibility was over.

And then there’s this. In June 2025, Jassy said something remarkable about AI and Amazon’s workforce: “We expect that this will reduce our total corporate workforce as we get efficiency gains from using AI extensively.”

When a CEO openly admits that AI will reduce headcount, the layoffs that follow aren’t surprises. They’re announcements.

The wider pattern

Amazon isn’t alone in this. The tech industry has been shedding workers at an alarming rate since 2023. Meta, Google, Microsoft: they’ve all made significant cuts.

But Amazon’s scale stands out.

Press enter or click to view image in full size

What’s different now is the framing. These aren’t pandemic corrections. They’re not responses to economic downturns. They’re strategic decisions to run leaner, move faster, and let AI (yes, that AI, if you still haven’t picked up yet) handle work that humans used to do.

Beth Galetti, Amazon’s senior vice president of People Experience and Technology, addressed employee concerns directly: “Some of you might ask if this is the beginning of a new rhythm, where we announce broad reductions every few months. That’s not our plan.”

But here’s the thing about plans. They change. And when a company has cut 60,000 jobs over three years while its CEO talks openly about AI reducing headcount, reassurances ring hollow.

What we lose

I keep coming back to Jason Dunn’s broken heart emoji.

(Steve graciously allowed me to share his post on LinkedIn and anyone is free to engage in that conversation).

There’s something almost unbearably human about it. No corporate statement. No carefully worded LinkedIn post about “new opportunities” and “exciting next chapters.” Just a symbol that everyone understood instantly, especially those in the Oceania region like myself.

The AWS Community Builders program will continue, presumably. Someone else will run it. The Slack channels will stay active. The meetups will happen.

But community isn’t a program. It’s people. And when you lose the person who made thousands of developers feel seen, supported, and connected, you lose something that can’t be replaced by reorganisation.

Community isn’t a program. It’s people. And when you lose the person who made thousands feel seen and connected, you lose something that can’t be replaced by reorganisation.

Amazon will be fine. The company’s market cap will fluctuate. The stock will do whatever stocks do. AWS will remain the dominant cloud platform.

But 30,000 people are looking for new jobs. Tens of thousands of community members just lost someone who championed them. And the message to everyone still employed in tech is unmistakable: efficiency is the priority now. Honestly, everything else (community, culture, the human connections that make work meaningful) is negotiable.

I’m still sad. It’s the end of an era.

References