Talent Risk

Talent Risk · Job cuts archive · January 2026 · Amazon

AI efficiency driveWednesday 28th January 2026One major outlet so farAI cited

Amazon: AI efficiency drive

AmazonCuttingTechnologyUS

16,000jobs, not yet confirmed
1report · 1 outlet, 1 major
Major outletBest source

Amazon announced 16,000 job cuts as part of a push for AI and efficiency improvements.

The sources, oldest first

  1. 28th Jan

    Reuters Major outlet

    Amazon announced 16,000 job cuts as part of a push for AI and efficiency improvements.

Amazon now

Cutting Confirmed by the company or a formal notice (such as a US WARN notice)

This label is our opinion, reached by applying one published rule to the sources listed. The full record for Amazon →

Other announcements at Amazon

  1. 3rd Nov
    Amazon to cut 1,250 jobs

    Cuts announcedTrade press only

    1,250jobs, not yet confirmed
  2. 2nd Nov
    Amazon files a WARN notice for 95 jobs in Washington

    Cuts announcedWashingtonFormal notice

    95jobs, part of a round already counted
  3. 2nd Nov
    Amazon files a WARN notice for 94 jobs in California

    Cuts announcedCaliforniaFormal notice

    94jobs, part of a round already counted
  4. 28th Oct
    Amazon to cut 250 jobs

    Cuts announcedTrade press only

    250jobs cut
  5. 7th Oct
    Amazon to cut 1,000 jobs

    Cuts announcedIndia, UKOne major outlet so far

    1,000jobs cut
  6. 31st Aug
    Amazon to cut 121 jobs

    Cuts announcedUSOne major outlet so far

    121jobs cut

The same month, nearby

Other announcements in January 2026 in the same sector or the same place.

  1. 8th Jan423jobs cut
  2. 19th Jan
    Meta files a WARN notice for 331 jobs in Washington

    Cuts announcedWashingtonFormal notice

    331jobs cut
  3. 16th Jan
    Meta files a WARN notice for 219 jobs in California

    Cuts announcedCaliforniaFormal notice

    219jobs cut
  4. 27th Jan173jobs cut
  5. 28th Jan162jobs cut
  6. 20th Jan133jobs cut

Permanent id amazon-2026-01-28-ee7b82. Machine-readable: this announcement is in /v1/events.json (seven days behind) and Amazon’s JSON.