The company was choosing machines over people.
In Seattle, the city where Amazon was born, a quiet but significant rupture has emerged between a corporation and its own workforce. Engineers who built the company's systems walked into city council chambers to oppose the very infrastructure their employer was racing to construct — even as 30,000 colleagues were shown the door. The city, moved by both the testimony and its own concerns about power, water, and equitable growth, advanced a moratorium on new data center permits. It is a moment that asks an old question in a new register: when a company chooses capital over people, who gets to say otherwise?
- Amazon engineers publicly broke ranks with their employer, testifying before Seattle's city council against new data center construction while the company was simultaneously laying off 30,000 workers.
- The stark contrast — billions flowing into AI infrastructure while colleagues departed with severance packages — galvanized both workers and city officials around a shared sense of misplaced priorities.
- Seattle's city council, already wary of data centers' heavy demands on electricity, water, and urban infrastructure, seized the moment and moved a permit moratorium forward through chambers.
- The moratorium is not a permanent ban but a deliberate pause — a civic tool to study impact, set boundaries, and reclaim some say over what kind of growth the city will absorb.
- The deeper tension remains unresolved: Amazon could simply redirect its construction to less resistant cities, leaving Seattle with a symbolic win but no restored jobs and no changed corporate calculus.
On a Tuesday evening in Seattle, Amazon engineers did something unusual — they walked into city council chambers to testify against their own employer. Their target was Amazon's aggressive push to build new data centers even as the company was laying off 30,000 workers worldwide. The engineers described watching colleagues lose their jobs while executives approved billions in AI infrastructure spending. It was a rare act of public employee dissent, and it resonated.
The layoffs had been announced in early 2025, sending a shockwave through Seattle's tech economy. Yet Amazon's capital spending never slowed. For workers watching friends leave with severance packages, the message felt clear: the company was choosing machines over people. The engineers brought that feeling into the public record.
Their testimony accelerated something already stirring at city hall. Seattle's council had its own concerns — data centers consume vast amounts of electricity and water, strain the power grid, and employ relatively few people for their footprint. Together, these pressures pushed the council toward a moratorium on new data center permits. By early June, it had advanced — not a permanent ban, but a pause to study impacts and establish clearer rules for future development.
For the engineers who testified, the moratorium felt like proof that speaking up had mattered. But the harder questions lingered. Amazon could build elsewhere, in cities with fewer constraints. The 30,000 lost jobs were not coming back. And the question the engineers had posed in that council chamber — why choose infrastructure over people — remained, for now, unanswered.
On a Tuesday evening in Seattle, Amazon engineers walked into city council chambers to testify against their own employer. They came to oppose new data center construction—the kind of massive, power-hungry infrastructure that Amazon was building even as the company was laying off 30,000 workers worldwide. The engineers didn't mince words. They described watching colleagues lose their jobs while executives green-lit billions in spending on artificial intelligence infrastructure. It was a rare moment of public employee dissent, and it landed hard.
The timing was not accidental. Amazon, headquartered in Seattle, had announced the layoffs in early 2025, a shock that rippled through the city's tech economy. But the company's capital spending plans didn't pause. Instead, Amazon continued to invest heavily in data centers—the sprawling facilities that power cloud computing and AI systems. For employees watching friends and collaborators walk out with severance packages, the contrast felt obscene. The company was choosing machines over people.
The engineers' testimony catalyzed something larger. Seattle's city council, already concerned about the environmental footprint of data center expansion and the strain on the city's power grid, began moving toward a moratorium on new data center permits. The council recognized that the issue wasn't just about Amazon's priorities—it was about what kind of growth the city wanted to accommodate. Data centers consume enormous amounts of electricity and water. They generate heat and demand infrastructure upgrades. And they employ relatively few people compared to their resource consumption.
By early June, the moratorium had advanced through the council. It wasn't a permanent ban, but a pause—a chance for the city to study the impact of data center expansion and set clearer rules about when and where such facilities could be built. The move reflected a broader reckoning in Seattle, a city that had grown wealthy on tech but was increasingly questioning whether that wealth was being distributed fairly or invested wisely.
For Amazon employees, the moratorium felt like vindication. They had spoken up, and the city had listened. But the larger question remained unresolved: Would the company change course? Would it reconsider its investment priorities? Or would it simply build its data centers elsewhere, in cities with fewer constraints and less organized opposition? The moratorium was a local victory, but it didn't restore the 30,000 jobs that were gone. It didn't answer the fundamental question the engineers had posed: Why choose AI infrastructure over people?
Citações Notáveis
Amazon engineers publicly criticized their employer for prioritizing expensive AI infrastructure investments amid mass layoffs— Amazon engineers testifying at Seattle city council
A Conversa do Hearth Outra perspectiva sobre a história
Why did Amazon employees decide to speak up publicly? That's a big risk for people still employed there.
Because the contradiction became impossible to ignore. You're being told your job isn't essential, but the company is spending billions on infrastructure. It forces you to ask what the company actually values.
And the city council responded by proposing a moratorium. But that doesn't bring back the 30,000 jobs.
No, it doesn't. But it does something else—it makes the choice visible. It says: we're not going to let this happen quietly. We're going to make you justify it.
Do you think Amazon will just build the data centers somewhere else?
Almost certainly. But that's not really the point anymore. The point is that Seattle said no. Other cities are watching.
What changes if other cities follow Seattle's lead?
Then the math changes for Amazon. If you can't build where your talent is, where your infrastructure already exists, you have to reconsider the whole strategy. That's when real pressure builds.