1,200 Amazon Engineers Just Signed a Public Flight-Risk List
The AECJ open letter and June 3 Seattle City Council testimony turned 1,200+ Amazon engineers into a self-declared sourcing shortlist. Move now.
Amazon confirmed 16,000 more corporate cuts on Wednesday, bringing the total to 30,000 since October and making this the largest workforce reduction in company history. In the same fiscal window, Amazon committed $200 billion to AI infrastructure for 2026. The gap between those two numbers is where your next hire lives, and 1,200 of them just raised their hands in public.
The letter is a roster, not a protest
Amazon Employees for Climate Justice (AECJ) has been organizing inside the company since at least 2020, when it staged a walkout over climate policy. The group has since folded AI governance and labor practices into its mandate, which turns out to be the same fight: the data centers being built are the physical substrate of the AI push, and the AI push is what Andy Jassy is using to justify shrinking the corporate workforce.
In late 2025, AECJ circulated an open letter criticizing Amazon's AI strategy and demanding worker input on how AI-driven layoffs and headcount freezes are implemented. As of the June hearings, more than 1,200 Amazon employees had signed it internally. AECJ published partial role lists including SDE and AWS Software Development Engineer titles across S3, EC2, Rufus, AWS Agentic AI, Amazon Robotics, Data Center Automation, and Amazon Ads.
That last sentence is the one recruiters should tape to the wall. Those are not peripheral orgs. Those are the teams every AI lab, hyperscaler competitor, and climate-tech Series B in your pipeline is trying to hire from right now.
What actually happened on June 3
Three engineers, Patrick Schloesser, Darius Irani, and Liesl Wigand, testified in front of Seattle City Council subcommittees on June 3, 2026, in support of regulating new mega data center development. Each of them opened their testimony by noting they were legally protected from retaliation for speaking out. The council then unanimously passed a proposal restricting new mega data center developments for one year.
A week later, Amazon's Employee Relations team called all three into separate meetings and told them they were under a disciplinary investigation. Irani later described it as feeling like he had committed a crime. The three subsequently filed a civil rights complaint with the Seattle Office for Civil Rights.
Their public identities are already indexed:
- Patrick Schloesser, AWS software engineer since 2020.
- Liesl Wigand, Amazon senior software engineer.
- Darius Irani, 5+ years at Amazon.
If you are sourcing Amazon engineers this quarter and those three names are not already in your outreach queue, you are not paying attention. They are the tip of a 1,200-person iceberg that AECJ has, for organizing reasons, agreed to make partially visible.
Jassy wrote the outreach script for you
Here is the part where the CEO helps.
In remarks to analysts, Jassy said the quiet part on tape: "The announcement that we made a few days ago was not really financially driven, and it's not even really AI-driven, not right now at least. It's culture."
Culture. Not performance. Not revenue. Not even the AI transition he keeps citing when he tells employees the corporate workforce will shrink over time due to efficiency gains from AI.
When a CEO tells analysts the cuts are about culture, every values-driven engineer on staff just heard the exit door unlock. </pull> If you signed a letter demanding worker input on AI deployment, and your CEO then told Wall Street the resulting layoffs were a culture cleanup, you are not going to spend Q3 pretending nothing happened. You are going to take the call. ## This is a flight signal, not a values letter The instinct with employee-activism moments is to file them under "principled workers doing principled things" and move on. That reads the situation wrong. Engineers who publicly criticize their employer's flagship $200B strategy, then testify against it at city council, then get pulled into HR investigations, have already emotionally offboarded. Your job is not persuasion. Your job is timing and psychological safety. The recruiter who lands a coffee with Schloesser, Wigand, or Irani in the next 60 days is not competing on comp. They are offering a workplace where testifying at a city council meeting does not trigger an internal probe. That is a very cheap advantage to hold. The same logic extends to the other 1,197 signatories AECJ has not named individually. They know who they are. They also know their employer is looking for them. ## The org chart AECJ accidentally published AECJ said publicly that it would only release role and org data after collecting 1,000 signatures. It has since done so, at least in part. The published slice covers: - S3 - EC2 - Rufus - AWS Agentic AI - Amazon Robotics - Data Center Automation - Amazon Ads That is not a random cross-section of Amazon. That is a map of where the AI infrastructure work actually happens. Data Center Automation engineers know exactly what $200B buys and how fast it can be brought online. AWS Agentic AI engineers are the people your foundation-model portfolio company has been trying to reach for eight months. S3 and EC2 engineers are the load-bearing walls of the entire hyperscaler business. The letter turned an internal Amazon org chart into a values-filtered public directory. Refolk's index shows roughly 400,000 US-based senior-and-above software engineering profiles, with Seattle as a top concentration region. The ~1,200 AECJ signatories are a very small, very specific slice of that pool, and they have pre-selected themselves on the axis that matters most for retention: they care about what they are building.
refolk prompt: Senior AWS engineers in Seattle on S3, EC2, or Agentic AI teams who have publicly supported climate or AI-ethics organizing since 2024. note: Refolk cross-references GitHub, LinkedIn, and open-web signals like petition signatures, city council testimony, and organizing group affiliations to surface the AECJ-adjacent shortlist without you rebuilding it by hand. slug: dfx2s3s7rm
## The solidarity list widens the pool by 4x
AECJ's solidarity page has picked up more than 4,000 signers from adjacent companies, including Microsoft, Google, Meta, Apple, Uber, Salesforce, Cisco, SpaceX, Boeing, Washington Post, and Oracle. Over 2,400 of those are tech workers.
If you are recruiting for a climate-tech infra company or an AI lab with a public-benefit charter, the solidarity list is arguably a better sourcing pool than the internal letter. These are people who publicly co-signed a critique of another company's AI strategy. They are already comfortable putting their name on things. They also work at your actual competitors.
This is the kind of signal that is trivially findable if you know what to look for and effectively invisible if you don't. Which is why we built [Refolk](/): you describe the person in plain English ("Google or Microsoft engineers who signed the AECJ solidarity letter and have committed to a Kubernetes or Ray project in the last year") and get a ranked shortlist without spending a week grinding through petition PDFs.
## The macro backs the micro
Two data points to keep in mind while you are triaging outreach:
```stat
number: 92,000
label: Tech workers laid off in the first half of 2026
note: GPU orders and data center construction contracts kept climbing over the same period.
</stat>
TD Cowen calculated that Amazon's workforce eliminations could generate $8 to $10 billion in incremental free cash flow that flows directly into GPU purchases and infrastructure construction. That is the trade the AECJ letter is protesting: headcount converted into H100s. Every engineer who signed the letter understands that trade with more precision than you do, because they are the ones being converted.
At the same time, grassroots groups blocked or delayed 75 data-center projects worth $130 billion in Q1 2026 alone. Active campaign groups more than doubled to 833 across 49 states. Which means the AECJ signatories are not lonely internal dissidents. They have external allies, external legal muscle, and external political wins to point to. That changes the psychological calculus of leaving.
### Why HR retaliation is the sourcing accelerant
Amazon's investigation of the three named engineers is the single most useful development for recruiters trying to reach the other 1,197. Every signatory now watches those three cases and asks themselves whether they are next. That is not a state anyone stays in for long.
If you have ever wondered when to send the "I saw what happened, we would love to talk" message, this is the window. Not next quarter. Not after Q4 earnings. This month.
How to actually source into this
A few practical notes for anyone building the list this week:
- Start with the three named engineers. They are on record, they are protected, and they are the most likely to talk about the broader group without violating anyone's confidence.
- Cross-reference AECJ's role list with LinkedIn tenure filters. AWS Software Development Engineers on S3, EC2, and Agentic AI who joined between 2019 and 2022 are the sweet spot: senior enough to matter, not so vested that leaving is impossible.
- Pull the solidarity signatures. More than 2,400 tech workers at Microsoft, Google, Meta, Apple, Oracle, SpaceX, and Boeing have already put their names on a document criticizing Amazon's AI strategy. That is a values filter you would otherwise have to manufacture through six weeks of DMs.
- Watch the Seattle Office for Civil Rights docket. The civil rights complaint Irani and colleagues filed will produce additional named individuals as the case moves.
For AWS engineer poaching specifically, the trick is not finding the names. It is finding the ones whose values are already public, because those are the ones who will respond to a values-based pitch and stay long enough to justify the recruiting spend. Plain-English sourcing tools like Refolk make that cross-reference cheap: you ask for "Amazon SDEs in Seattle who signed the AECJ letter and contribute to open-source infra projects", and you get a shortlist instead of a spreadsheet.
The window closes when the news cycle does
AI dissent tech workers are having a moment because the layoffs, the $200B, and the Seattle hearing landed in the same six weeks. That moment does not last. Jassy has already signaled that Amazon's corporate workforce will shrink over time. The next round of cuts will produce a new news cycle, and the AECJ signatories will either have already left or will have made peace with staying.
The 1,200 names on that letter are not a permanent list. They are a live one, and the half-life is short.
FAQ
Is it legal to source engineers based on their signature on an activism letter?
Yes. Public signatures on open letters are public information, and reaching out to a professional about a role at another company is standard recruiting practice. What you cannot do is discriminate based on protected activity within their current employer. Seattle in particular has a political-ideology ordinance, which is part of why the AECJ engineers filed the civil rights complaint against Amazon. As a recruiter contacting them, you are on the opposite side of that risk.
Should I reach out to Schloesser, Irani, and Wigand directly?
If you have a role that fits and a message that respects the moment, yes. They are named publicly, they have spoken to national press, and they are under active HR investigation. A short, specific note that acknowledges the situation and offers a genuine alternative is not tacky, it is useful. A generic "great opportunity at a Series B" blast is tacky.
How do I find AECJ signatories who are not named publicly?
Cross-reference AECJ's published role and org list (S3, EC2, Rufus, AWS Agentic AI, Amazon Robotics, Data Center Automation, Amazon Ads) with LinkedIn, GitHub commit history, and open-web signals like petition signatures and conference talks on AI ethics or sustainability. Tools that unify those signals into one query, like Refolk, compress what used to be a week of manual work into an afternoon.
What about the solidarity signers at Google, Microsoft, and Meta?
They are arguably a warmer pool than the Amazon list, because their current employer has not (yet) launched an HR investigation of them. If you are recruiting for climate-tech infrastructure, responsible-AI labs, or any company whose story involves not being Amazon, the 2,400+ solidarity signers are the shortlist you should be building first.