Amazon Investigated the Engineers Who Testified

Introduction

On June 9, the Seattle City Council voted 9-0 to put a one-year moratorium on new data centers. The next morning, Amazon summoned each of the three engineers who had testified about that measure to separate Zoom calls and told them they were under internal investigation. Patrick Schloesser had less than 30 minutes before a work presentation when the call landed, and recalls being told the probe could lead to being fired. Amazon says it was checking whether they had followed company procedures for speaking as Amazon representatives. What they actually did was show up to a public government hearing.

What Three Engineers Actually Said at City Hall

Back up to June 3. Schloesser, Darius Irani, and Liesl Wigand testified before Seattle City Council committees during the run-up to the moratorium vote. All three identified themselves the same way, as members of Amazon Employees for Climate Justice, a worker group, not as Amazon spokespeople or company representatives. Amazon's whole investigation hinges on that distinction.

Their testimony went hard against the industry Amazon leads. Wigand told the council, "In my job, I see the consequences of the all-costs-justified AI buildout." Schloesser said he went public "because I got sick of feeling afraid to stand up for my values," and called on developers to stop hiding behind NDAs and shell companies. Irani asked the city to require public reporting of how much water and electricity these facilities consume. None of it sounds like an official Amazon position, and Amazon itself made no formal comment on the measure at all.

According to GeekWire, which reviewed a copy of the complaint, each engineer opened their testimony by noting they were legally protected from retaliation for speaking out. They said it out loud before they got into anything else, and the HR calls came anyway.

The Law That Made This a Case at All

Here's the part most people get wrong about free speech at work. The First Amendment only restrains the government, which means your private employer can fire you for your politics without anyone breaking the Constitution, because there's no state actor in the room. Public-sector employees get some protection, narrowed by cases like Garcetti v. Ceballos. For most American workers in private jobs, federal law has almost nothing to say about employer retaliation for political speech.

Which is why this story exists in Seattle and almost nowhere else. The city's Fair Employment Practices Ordinance makes "political ideology" a protected class, defined as any belief "relating to the purpose, conduct, organization, function or basis of government," including conduct reasonably related to that ideology that doesn't interfere with job performance. Under the ordinance, an employer discriminating on that basis has committed an unfair employment practice. On June 18, AECJ filed a civil rights complaint with Seattle's Office for Civil Rights under that law, asking the city to investigate. Remedies can include reinstatement, back pay, and financial damages.

Attorney Abby Lawlor, representing the engineers, noted that Seattle is one of just a few jurisdictions in the country with this level of protection. The only reason these three have any recourse is a local ordinance that most American cities have never passed. Move this exact fact pattern to almost any other city and there's no complaint to file, no agency to investigate, and the suppression just works quietly while you never hear about it.

They Were Watching Before Anyone Got Called

The detail that turns this from a labor dispute into something colder is in the complaint itself. According to CNBC, which quoted the document directly, the engineers "learned that Amazon was monitoring their political advocacy before the Seattle City Council and was seeking to identify additional employees who had engaged in political activities."

So Amazon wasn't reacting to three people after the fact. It was tracking who showed up to a public hearing and hunting for more names. Wired's reporting backs this up: Irani says the HR representative on his call asked him about other Amazon employees who had attended the council hearings. A compliance review doesn't ask who else was in the room, but a search does, and the engineers were the part of it that became visible.

Then there's the part that's easy to miss. Wired reported that two other Amazon employees who testified at later council meetings have received no investigation notice at all. So out of roughly five Amazon employees who testified across the hearings, the three under investigation are the same three who filed the formal legal complaint. A real communications-policy sweep would have flagged everyone who spoke, not just the three most willing to fight back.

Amazon Has Run This Exact Play Before

Amazon has done this before, which is worth keeping in mind when you weigh its intent. In April 2020, it fired AECJ co-founders Maren Costa and Emily Cunningham after they publicly backed warehouse workers' COVID-19 safety demands. The company said they had repeatedly violated internal policies. The National Labor Relations Board found the firings unlawful, and in 2021 Amazon settled, paid lost wages, and was required to post company-wide notices affirming workers' right to organize.

Then last year. In September 2025, Amazon suspended Ahmed Shahrour, a Whole Foods software engineer in Seattle, for internal Slack posts criticizing Amazon's Project Nimbus contract with the Israeli government. It cited potential policy violations, revoked his email and Slack access, removed his posts, and fired him on October 13, 2025. The mechanism is identical: a policy investigation aimed at employee political expression the company would rather not hear, whether it happens in a Slack channel or at a city council podium.

Who Benefits

Follow the money and the beneficiary is obvious. Amazon has committed roughly $200 billion in capital expenditures for 2026, the bulk of it aimed at AI infrastructure. That's about a 60% jump from the prior year and more than $50 billion past what analysts expected. CEO Andy Jassy put it plainly in his April shareholder letter: "We're not going to be conservative in how we play this." AWS is running at a $142 billion annualized revenue rate, with the AI-specific slice at $15 billion and climbing.

A data center moratorium in Amazon's own headquarters city threatens that strategy directly, even though Amazon doesn't currently have an active facility proposal inside Seattle's limits. What it threatens is the precedent. The Seattle vote produced a model other cities can copy: a unanimous council, more than 98,000 emails from constituents, and not a single speaker in favor of data centers at the final hearing. Somewhere between 60 and 70-plus cities and counties already have some form of ban or restriction, per a database kept by the hedge fund Interconnected Capital, and Seattle is now the largest U.S. city in that group. The national mood is already there: Gallup found 71% of Americans oppose AI data centers being built in their local area, a stronger objection than people register against nuclear power plants.

The real payoff here isn't winning a policy fight, it's the chilling effect, and Amazon doesn't need to fire all three engineers to collect it. An open investigation with termination floated as a possible outcome tells every other Amazon employee that testifying at a government hearing about the company's industry carries real professional risk. Schloesser described a culture where "you're afraid of losing your job just by doing the work that you're expected to do day to day." Add the threat of an HR probe for civic participation on top of that, and most workers will quietly decide it isn't worth it, which costs Amazon almost nothing and protects a $200 billion bet.

The Math Doesn't Favor the Worker

On its surface, Amazon's justification isn't made up. Companies really do have communications policies, and Amazon's spokesperson framed the review as a question of whether the employees "may have been speaking in their capacity as Amazonians and not as private citizens." The catch is that the engineers named themselves as members of a worker group, said things directly opposed to Amazon's interests, and prefaced their remarks by citing their legal protection. A policy written to stop employees from impersonating the company is now pointed at employees who took real pains to make clear they weren't.

The timing, laid end to end, leaves little room for coincidence. The engineers testified June 3, the council voted 9-0 on June 9, and the HR calls went out the next morning. Then on June 11, two days after the vote and one day after summoning the engineers, Amazon published its water-use sustainability data in what multiple outlets read as damage control.

The Bottom Line

The case in front of Seattle's Office for Civil Rights is narrow: did Amazon discriminate against three named engineers based on protected political ideology under one city's ordinance? That question will get answered eventually, with reinstatement and back pay on the table if the city finds reasonable cause. The answer that matters for everyone else was already delivered the morning the calls went out, and it doesn't depend on how the complaint resolves.

Here's what it tells you. If you work for a company that has any business before your local government, and nearly every large employer does, that company can open a disciplinary investigation against you for testifying at a city council meeting about it. In Seattle, there's a law that might reach that conduct, while most of the country has nothing. So the question that actually counts isn't whether three engineers win their complaint. It's how many people in cities without Seattle's ordinance just watched this play out and quietly decided to stay home from their own city's next hearing.