← Back to latest
Essay

Amazon workers against data centres: who speaks for Amazon?

Amazon engineers helped persuade Seattle to pause new large data centres, although Amazon runs none in the city. The company's answer, an inquiry into whether they spoke as "Amazonians", suggests where the real contest lies: over who may speak with an insider's authority about the AI buildout.

Listen to this briefing

Enable JavaScript and use a browser with spoken audio support to listen.

Read aloud by your browser. Voice and availability depend on your device.

5 min readBy McCyber

Amazon engineers went to Seattle City Hall in June to support a pause on the kind of building their employer is spending record sums on, and within about a week Amazon had opened investigations into three of them. The pause passed unanimously, yet it barely touches Amazon’s own data centres, which is why the more revealing fight is the one over the engineers’ right to speak.

The sequence was short. On 3 June, three software engineers from Amazon Employees for Climate Justice (AECJ), an independent group of staff that says it pushed Amazon into its 2019 Climate Pledge, testified before council committees in favour of regulating data centres. Each opened by noting that Seattle law protects workers from retaliation by their employers. AECJ members urged the council to add renewable energy and labour requirements, and accused the industry of adding compute as fast as it can, “before regulations can catch up”.

On 9 June the council voted 9-0 for Ordinance 127447, a 365-day moratorium on applications to build, expand or convert to data centres with more than 20 megavolt-amperes of capacity, renewable in six-month steps. The mayor signed it on 11 June. The trigger was an approach by four companies to Seattle City Light about five large facilities with a combined demand of 369 megawatts.

A pause that barely reaches Amazon

Here is the oddity. Neither Amazon nor Microsoft operates a data centre inside Seattle; Amazon’s facilities cluster in Oregon, and the city’s roughly 30 existing smaller sites are exempt and may each grow by up to 20 megavolt-amperes. Councilmember Eddie Lin said Seattle residents should not be subsidising “record profits of large corporations from the AI boom”, while Councilmember Debora Juarez said the pause “does not stop AI or data centers”. Both statements hold. The ordinance constrains third-party developers in one city. Amazon, meanwhile, expects about $220 billion in cash capital expenditure this year, after a $94.8 billion year-on-year rise in purchases of property and equipment that it says primarily reflects investment in artificial intelligence.

What the engineers brought, then, was the authority of insiders, rather than any power over their employer’s buildings. Their arguments echo AECJ’s open letter to Andy Jassy, which by the group’s own running count carries 1,235 Amazon signatures. It objects to an “all-costs-justified, warp-speed approach to AI development” and asks for every data centre to run on additional, local renewable energy around the clock, for working groups of non-managers with a say over AI-related layoffs, and for limits on AI used for surveillance and deportation. The economic charge gained force from two company announcements: about 14,000 corporate roles cut in October 2025 and about 16,000 more in January 2026.

Shareholders have pressed a version of the same point. In its 2026 proxy statement, Amazon’s board opposed a proposal asking how the company would meet its climate commitments given AI demand, saying its existing reporting “already addresses the specific challenges” the proposal raised.

The question of who is speaking

Amazon’s response moved the argument from megawatts to speech. According to the engineers’ complaint, filed on 18 June with the Seattle Office for Civil Rights, employee relations staff told each of them in separate meetings that they were under investigation for their testimony. Amazon confirmed the inquiries. Its spokesperson, Margaret Callahan, said that “it became clear that they may have been speaking in their capacity as Amazonians and not as private citizens”, and that the company “may or may not take action based on what we find”. Amazon denies threatening dismissal and says it does not tolerate retaliation. The engineers’ lawyers say they never mentioned Amazon and testified on their own time using publicly available information, as reported by the Seattle Times.

The complaint relies on a local peculiarity. Seattle’s Fair Employment Practices Ordinance lists political ideology as a protected class, a protection few American jurisdictions offer. If the civil rights office finds reasonable cause, remedies can include back pay and damages. No finding has been made public.

Amazon’s stated reason is its policy on speaking for the company. One reading, which Amazon has not offered and which cannot be proved from the public record, is that the testimony mattered because of who gave it. Residents can object to noise, water and electricity bills. An Amazon engineer can tell a council that the AI race is moving faster than the rules, and be heard as someone who builds the systems. If an employee who sounds like an Amazonian is treated as speaking for Amazon, that kind of testimony becomes harder to give. It is also what AECJ now says lawmakers want. Its website says policymakers are approaching the group for tech workers’ views on regulating AI, and it held an organising session for current and former staff on 14 November.

Ohio’s votes and Amazon’s own plans

Local resistance to Amazon’s own projects is coming from voters elsewhere. On 3 November, 79% of voters in Sunbury, Ohio, approved a charter amendment prohibiting data centres, after residents had campaigned against a proposed $2 billion Amazon campus with a ban on facilities above 25 megawatts. In Trenton, where a 600-acre Amazon facility is planned, 80% backed a similar ban. Unlike Seattle’s pause, these votes concern Amazon’s own plans. Passing a ban is not the same as stopping a project, though. Whether each amendment reaches a particular Amazon site depends on its wording, on what had already been approved, and on any challenge in the courts, which the votes alone do not settle.

The strongest counter-reading is that the Seattle episode is a small group making a symbolic point. A little over a thousand signatures is a sliver of a very large workforce. Policies against speaking for an employer without authorisation are common, as Amazon says, and an inquiry is not a sanction. A city with no Amazon data centres pausing new ones costs the campaigners little, and local bans may simply push hyperscale projects towards places with dirtier grids and less scrutiny. On that view, the engineers won a gesture and Amazon is enforcing a routine rule.

That view underrates what the buildout depends on. Data centres increasingly need the consent of councils and voters, and some of the people best placed to explain the costs are the engineers who build the systems. Seattle’s civil rights office now has to decide whether three of them spoke as citizens or as Amazonians. Its finding would apply Seattle’s ordinance to one set of facts, and how much weight it carries elsewhere will depend on its reasoning. It will still be read closely by tech workers wondering whether they can say in public what they know.

Sources: Seattle City Council; Office of the City Clerk, City of Seattle; Seattle Office for Civil Rights; Amazon (third-quarter 2026 results, workforce announcements, 2026 proxy statement filed with the SEC); Amazon Employees for Climate Justice; GeekWire; The Seattle Times (as republished by The Spokesman-Review); Fox 8; NBC4 WCMH-TV.