Amazon Project Dawn 2: Blind Named 4 Orgs Before the WARN Hit

A Blind thread titled "Another round of layoffs at Amazon next month?" surfaced in early September 2026 and named Stores, Prime Video, AWS and PXT as the hardest-hit orgs, pointing at a Washington ESD WARN entry dated 10/1/2026. Days later, the state's Employment Security Department confirmed 121 Amazon roles across Seattle, Bellevue and Sumner. If you waited for the GeekWire headline, you were already 60 days behind the people on the inside.

What the Blind thread actually said, and when

The thread flagged a new round of Amazon layoffs effective October 1, 2026 and claimed "Stores, PV, AWS, PXT will be hit the hardest" roughly two weeks before Washington State's ESD paperwork went public with 121 roles. That gap is the whole game.

Here is the public timeline, pieced from Blind, ESD and GeekWire:

• Early September 2026: Blind thread names four orgs and points at the 10/1/2026 ESD entry.
• August 31, 2026: Washington ESD receives Amazon's WARN notice covering 121 workers across Seattle, Bellevue and Sumner, classified as permanent.
• October 1, 2026: First employee separated.
• October 2, 2026: 32 employees separated.
• October 20, 2026: 66 separated.
• October 27, 2026: Final separation in this batch.

The WARN letter is signed by Vani Appukkutty, Director of SDM Departures, with Guy Palumbo of Amazon public policy as the external contact. Both names are worth saving. Watching which Amazon executive signs each WARN is a quiet tell on which org is next, and Appukkutty's "SDM Departures" title alone narrows the signal to Software Development Managers.

Project Dawn 2 in context: 30,000 cuts and counting

Project Dawn 2 is the colloquial name for Amazon's October 2026 round, following the original Project Dawn cuts that brought corporate layoffs to roughly 30,000 by January 2026, or close to 10% of Amazon's white-collar headcount. The "Project Dawn" codename itself leaked via a mis-sent calendar invite tied to an email signed by Colleen Aubrey, SVP of Applied AI Solutions at AWS.

The pattern of Washington-state cuts across the sequence:

• October 2025: 2,303 Washington cuts.
• December 2025: 84.
• January 2026: ~400 tied to grocery closings.
• February 2026: 2,198.
• Summer 2026: 57.
• October 2026 (Project Dawn 2): 121 and counting.

Impacted employees across the Dawn rounds have come from AWS, Alexa, Prime Video, devices, advertising, last mile delivery, Kindle and supply chain optimization. The Blind "big four" (Stores, Prime Video, AWS, PXT) is directionally right for Dawn 2 specifically, but historically the surface has been wider.

30,000

Why 121 is a keyhole, not the pool

The 121-role Washington WARN is a narrow geographic slice of a much larger cut, and treating it as the universe is the first mistake sourcers make. Only a small share of Amazon layoffs ever appear on any single state's WARN.

Of the 121 roles disclosed, 43% are software or applied science. The headline title breakdown:

• SDE I: 13 roles
• SDE II: 12 roles
• SDE III: 12 roles
• Service Technician III: 9 roles
• Applied Scientist III: 8 roles

Compare that against the actual Amazon pool in Refolk's index of professional profiles:

The 37 SDE cuts in the WARN represent roughly 3.4% of the US AWS SDE pool. If you build your outreach list from the WARN alone, you are talking to a tiny slice of the people this round actually touches. The other 96.6% are either in other states, in other orgs, or on an internal transfer clock no public filing captures.

The Blind "four orgs" leak is directionally right, geographically wrong

Washington ESD captures Seattle, Bellevue and Sumner, but Prime Video's center of gravity sits in Los Angeles. In Refolk's index, LA profiles under the Prime Video / Amazon MGM Studios umbrella outnumber Seattle profiles by roughly 2×. Any sourcer who only watches WA ESD will miss roughly half of Prime Video exits.

The parallel endpoints to bookmark:

1. Washington ESD WARN database (esd.wa.gov).
2. California EDD WARN notices.
3. New York DOL WARN tracker.
4. GeekWire's layoff tracker, which typically breaks WA WARN filings same-day.
5. Blind, specifically keyword alerts on "Amazon" plus "Project" plus any proper noun.

AWS Elemental in Corvallis, OR and Amazon MGM Studios in LA are two sub-orgs that will show up in impacted-employee headlines but never in a Washington WARN. If your boolean is anchored on Seattle, you have already excluded them.

Waiting for the WARN means arriving at a market the inside hired out of 60 days ago.

PXT is a near-useless search string

Searching LinkedIn or GitHub for "PXT" to find laid-off Amazon HR will return almost nothing, because the verbatim phrase is internal jargon that rarely survives a profile rewrite. In Refolk's index, only 14 US profiles use "Amazon PXT people experience technology" verbatim, versus thousands who hold the underlying functional titles.

The mechanism: when an Amazonian updates their LinkedIn after a layoff, usually within 30 days of separation, they translate internal shorthand into recruiter-legible titles. "PXT" becomes "People Experience and Technology Solutions," then "HR Business Partner," then just "HRBP."

If you want to find PXT leavers, search on the output, not the input:

• "HRBP" scoped to Amazon.
• "Senior Manager, HR Operations" scoped to Amazon.
• "Site HR Lead," "Area HR Manager," "Learning Experience Designer" scoped to Amazon.
• "Workforce Staffing" scoped to Amazon fulfillment.
• "People Experience" as a loose keyword, which catches recent rewrites.

This is the kind of translation problem that eats hours in LinkedIn Recruiter and resolves in one sentence in Refolk: "HRBPs and HR operations leaders who worked at Amazon in Seattle, Bellevue or Arlington in the last 18 months, filtered to people who updated their profile in the last 60 days." You describe the person; the shortlist comes back ranked.

The 90-day window is the whole premise

Amazon gives impacted staff roughly 90 days of advance notice during which they can apply for internal transfers, and that window is the pre-WARN sourcing playbook's entire reason to exist. By the time a WARN hits the ESD portal, the affected employees have been quietly on the market for 60-plus days.

Mapped to Dawn 2:

• Internal notifications: July 1 to July 29, 2026.
• WARN filed with WA ESD: August 31, 2026.
• Blind thread: early September 2026.
• First separations: October 1, 2026.
• Final separations in this batch: October 27, 2026.

The sourcer who starts outreach on October 1 is working a market that has been shopping offers since mid-July. The sourcer who starts on September 1, armed with the Blind leak, has a 30-day head start on everyone waiting for GeekWire.

3.4%

Seniority offered no protection

In the 121-role batch, cuts are almost perfectly flat across SDE I, II and III at 13, 12 and 12. The implication: filtering only on Staff and Principal to avoid a perceived "junior laid-off" bias will miss roughly two-thirds of the actual pool.

Three sourcer habits to break for Dawn 2 specifically:

• Dropping SDE I and SDE II out of the shortlist. SDE II at Amazon has 3 to 5 years of production experience and clears most mid-level bars at startups.
• Weighting Applied Scientist III below Staff ML Engineer. Amazon's Applied Scientist ladder runs deep; III is a working research scientist with shipped systems.
• Ignoring Service Technician III. Nine of these roles are in the WARN, and they map cleanly to data-center ops and site reliability roles at hyperscalers and colos.

For a target list that respects what Amazon's levels actually mean, build the boolean on tenure and shipped work, not title inflation.

Codename watch as a leading indicator

Any new codename ("Project Dawn 2," "Project Dusk," anything with "Project" plus a proper noun) surfacing on Blind in Q4 2026 is a leading indicator roughly 2 to 6 weeks ahead of ESD paperwork. The original Project Dawn leaked via a mis-sent calendar invite tied to Colleen Aubrey's email; Dawn 2's Blind thread beat the WARN by about two weeks.

A minimal watchlist for Q4 2026:

• Blind keyword alert: "Amazon" + "Project" + any capitalized second word.
• Blind author alerts on verified Amazon posters in the Compensation and Rumors channels.
• LinkedIn alerts on Vani Appukkutty, Colleen Aubrey and Brad Glasser, Amazon's standard spokesperson, whose "teams regularly review their structures" phrasing is the standard Amazon tell.
• ESD, EDD and DOL WARN RSS feeds in a single reader.
• GeekWire layoff tracker, same reader.

Once a codename hits, cross-reference impacted-org claims against your existing Amazon map. A plain-English query in Refolk like "Prime Video product managers in Los Angeles who have been at Amazon MGM Studios for more than two years" returns a ranked list across LinkedIn, GitHub and the open web, so you can build a pre-WARN target list in the hour the Blind thread goes up, not the week after.

The pre-WARN sourcing playbook in one page

The playbook for sourcing laid-off Amazon employees ahead of the Washington ESD filing is five moves, in order:

1. Monitor Blind, ESD, EDD and DOL in parallel; do not treat any single endpoint as the universe.
2. Translate internal jargon ("PXT," "SDM," "Last Mile") into LinkedIn-legible titles before you search.
3. Build the boolean against the full US pool, then intersect with "profile updated in last 60 days" instead of filtering on geography alone.
4. Keep SDE I, SDE II and Service Technician III in scope; the cuts are flat across levels.
5. Start outreach the day the codename surfaces, not the day the WARN posts.

Dawn 2 is 121 named roles in Washington. The actual market in motion is thousands, spread across Seattle, Bellevue, LA, Corvallis, Arlington and remote. The sourcers who treat the WARN as a starting whistle are the ones still writing cold emails in November, to candidates who signed offers in September.

FAQ

How accurate was the Blind thread about Amazon's October 2026 layoffs?

Directionally accurate on timing and partially accurate on orgs. The thread correctly flagged the 10/1/2026 effective date that Washington ESD then confirmed with a 121-role WARN, and it named four orgs (Stores, Prime Video, AWS, PXT) that match the recurring pattern from the January 2026 Project Dawn round. Where it was weakest is geography: Prime Video exits concentrate in LA, not Seattle, so WA WARN undercounts that org by roughly 2×.

Why do only 14 Amazon PXT profiles show up in a direct search?

Because "PXT" is Amazon-internal shorthand for People Experience and Technology Solutions, and almost nobody puts it on their LinkedIn headline. Within 30 days of a layoff, impacted HR employees typically rewrite their titles to industry-standard labels like HRBP, Senior Manager HR Operations or Site HR Lead. To find PXT leavers, search those functional titles scoped to Amazon rather than the acronym.

Which state WARN databases should I watch alongside Washington ESD?

At minimum California EDD and New York DOL, because Prime Video and Amazon MGM Studios are LA-weighted. For AWS specifically, add Oregon, where AWS Elemental sits in Corvallis. GeekWire's layoff tracker aggregates WA quickly but will not catch the others on day one.

What is the pre-WARN sourcing playbook in one sentence?

Start from Blind and codename leaks roughly 2 to 6 weeks before state WARN filings, translate Amazon-internal jargon into recruiter-legible titles, and intersect the full US company pool with recent profile-update signal rather than filtering on the WARN's narrow geographic slice. The 90-day advance-notice window Amazon gives employees is the runway you are trying to compete inside.