Amazon's Oct 6 Stores Cut: The Pool Is in Hyderabad, Not Seattle

Amazon confirmed on October 7, 2026 that it cut "fewer than 1,000" white-collar roles across its Stores division, with layoff emails landing the morning of October 6, the first day of Prime Big Deal Days. The affected teams sit in customer service, selling partner services, and retail engineering across the US, India, and UK. If you source for a competing marketplace or an engineering team that respects Amazon pedigree, you have a narrow window before the rumored next wave buries this cohort.

What Amazon actually did on October 6

Amazon eliminated fewer than 1,000 Stores roles on October 6, 2026, with notifications going out the same morning Prime Big Deal Days launched; the company has not published a headcount of its own. The "fewer than 1,000" figure traces to a single person familiar with the matter cited by Business Insider, and other outlets have rounded that same anonymous estimate into "nearly 1,000" or "around 1,000."

The confirmed facts:

• Cuts announced October 7, 2026; notifications began Tuesday October 6.
• Affected teams: customer service, selling partner services, and retail engineering.
• Geographies: United States, India, and the United Kingdom. City AM reports only a handful of the roles are in the UK.
• An Amazon spokesperson called it "a small number of roles" and said parts of the Stores business had been "adjusted."
• Amazon had not filed a WARN notice with Washington's Employment Security Department as of GeekWire's reporting, which legally would be required for 50 or more cuts in the state.

That last point matters more than the headcount. No WARN filing means the Seattle cohort is either under 50 or scattered across sites, and either way there is no public list. The pool has to be rebuilt from LinkedIn status flips, GitHub commit drop-offs on amzn/* and aws-samples repos, and TeamBlind chatter, not government filings.

<1,000

Why this cut is sourceable and the previous ones were not

The 30,000 cuts Amazon has made since January 2026 represent about 10% of its corporate and tech workforce of roughly 350,000, which is too diffuse to source against. The October 6 cut is the opposite: three named functions, three named geos, one timestamp. That is the kind of brief Boolean strings choke on but a plain-English query handles.

The pool is in India, not Seattle

The real volume of this cut sits in Hyderabad, Bengaluru, and Chennai, not Seattle. US-centric sourcers chasing "ex-Amazon Stores Seattle" will miss the majority of the actual affected headcount. In Refolk's index of professional profiles, India holds the single densest ex-Amazon engineering concentration on earth outside of Puget Sound, and Hyderabad alone accounts for roughly 44% of it.

The 2.5-to-1 US-India ratio understates reality for this specific cut, because Stores selling-partner support is disproportionately an India function. Hyderabad is where seller-support night shifts for North American merchants run. If your pipeline is monolingual English and US-only, you have scoped yourself out of most of the pool.

Why 86 seller-support profiles is the wrong number

Refolk's index returns only 86 profiles across the US, UK, and India when you search strictly on "seller support" or "selling partner support" in the title field. That is not the real pool. It is the sourcing trap.

The Stores support function self-camouflages on LinkedIn. The actual title conventions I see across the alumni base:

• "Associate"
• "Catalog Associate"
• "Business Specialist"
• "Investigation Specialist"
• "Account Health Specialist"
• "Risk Investigator"

Keyword-only Boolean against "seller support" returns 86. Employer plus team plus tenure overlap plus "Open to Work" signal returns something closer to the actual Stores support alumni base, which is an order of magnitude larger. This is the exact gap Refolk closes: you describe the person in plain English ("ex-Amazon in Hyderabad or Bengaluru who worked on seller or marketplace support between 2022 and 2026, laid off this month"), and get a ranked shortlist built from title, employer, tenure, and status signals together, not any one of them alone.

The BPO distinction that will cost you offers

Many "Amazon seller support" alumni on LinkedIn are not Amazon FTEs. They are Teleperformance or Concentrix badge contractors staffed onto Amazon accounts. Refolk's index shows TP and Concentrix as the top non-Amazon employers of profiles carrying "Seller Support" in the title.

That distinction decides your offer. A severance-eligible Amazon FTE wants comp parity and relocation. A TP badge contractor wants a conversion offer. Confusing the two will burn your first reply.

The three-day week pitch competitors should steal

Jeff Bezos spent the same news cycle telling Fox News host Bret Baier that AI's productivity gains could let some people "support my family by working three days a week." None of the workers Amazon cut on October 6 got a shorter week. They got severance. That cognitive dissonance is a free outreach hook for every competing marketplace.

The companies with the most reason to send a message this week:

1. Shopify for merchant-tools engineering and seller onboarding.
2. Walmart Marketplace and Walmart Connect for direct seller-support function parity.
3. TikTok Shop for growth-stage marketplace ops.
4. Flipkart for the Bengaluru and Hyderabad cohort.
5. Noon for ex-India selling-partner staff open to Dubai.
6. eBay, Etsy, Temu, Faire for the long tail.

None of the laid-off workers got a shorter week. They got severance. That is your opening line.

Refolk's index shows eBay and Concentrix already appear as secondary employers of ex-Amazon seller-support staff, which means your outreach is competing with warm-intro paths those alumni already have. Speed matters more than cleverness.

How to pipeline this in 72 hours

Treat the Amazon Stores layoffs as a 72-hour sprint, not a quarter-long project, because the rumored next wave will flood the signal. The playbook, in order:

1. Lock the geofence first. Hyderabad (Telangana), Bengaluru (Karnataka), Chennai (Tamil Nadu), Seattle, Bellevue, Arlington VA (HQ2), London. Everything else is noise for this cut.
2. Watch GitHub, not just LinkedIn. Commit-history drop-offs on amzn/* and aws-samples repos surface the engineering side days before the LinkedIn "Open to Work" banner goes up.
3. Monitor the communities where the pool surfaces first. r/amazon and r/layoffs, the Amazon Alumni LinkedIn group, and the Amazon channel on TeamBlind.
4. Split FTE from BPO before you send any offer. Teleperformance and Concentrix tenure in the employment history is the tell.
5. Translate titles. "Associate," "Catalog Associate," "Business Specialist," and "Investigation Specialist" are all seller-support in disguise.
6. Reach out in the local language where it matters. Hindi, Telugu, and Tamil outreach outperforms English for the Indian cohort by a wide margin in my experience.

The reason this is a 72-hour window and not a six-week one: Amazon has made smaller cuts across robotics and AGI groups since January, and the rumored next wave would push this cohort under a much larger pile of status changes.

A note on Doug Herrington's org

The cut sits inside Worldwide Amazon Stores, run by CEO Doug Herrington. Beth Galetti, SVP of people experience and technology, authored the January blog post that framed Amazon's broader reduction stance. Those two names are useful context for outreach notes to candidates. Not for name-dropping, but for signalling you understand which org took the hit and why that affects their severance timeline.

Where to point replacement roles

Point your replacement roles at the cities where the cut landed, in the languages those cities actually recruit in. The Hyderabad engineering market in particular is deep enough right now that a well-scoped seller-tools or marketplace-infra role posted this week will see unusual response rates.

If your target is the Seattle cohort, remember that absence of a WARN filing cuts both ways: no public list for you, no public list for your competitors either. The pool has to be reconstructed from signals, and that is where plain-English querying beats a 400-character Boolean every time.

The 15,660 number is a decoy

The 15,660 US-based Amazon engineers in Refolk's index are not your pool. They are the denominator. Your pool is the subset of those 15,660 whose profiles updated between October 6 and today, overlapped with the Stores org, in Seattle, Bellevue, or Arlington. That is a smaller, cleaner list than any Boolean string will produce.

6,306

The failure mode I keep seeing on sub-1,000-headcount cuts like this one is sourcers treating the full alumni base as the pool and spraying generic "Hey, saw the news" messages at 2,000 people. Reply rates collapse, candidates get annoyed, and the actually-affected 300-ish people in your target geos get buried. Narrow first, then write the message.

FAQ

How many people did Amazon lay off on October 6, 2026?

Amazon has not published a number. A spokesperson called it "a small number of roles" and declined to confirm. The widely cited "fewer than 1,000" figure comes from a single source familiar with the matter cited by Business Insider, and other outlets have rounded that same estimate up. Treat it as a ceiling, not a count. For context, 30,000 cuts since October represent about 10% of Amazon's roughly 350,000-person corporate and tech workforce.

Why no WARN notice for the Seattle cuts?

Washington's Employment Security Department requires a WARN filing when a company lays off 50 or more workers in the state. As of GeekWire's reporting, Amazon had not filed one for this round. That means the Seattle-based Stores cohort is either under 50 heads or spread thinly across sites. Practically, it also means no public list, so you have to reconstruct the pool from LinkedIn status changes, GitHub commit drop-offs, and community posts.

Where should I focus geographically if I only have time for one city?

Hyderabad. In Refolk's index, Hyderabad holds roughly 44% of the India-based Amazon engineering pool, and India is where the Stores selling-partner support function has its deepest footprint. For engineering-only pipelines, Seattle and Bellevue together still hold about 32% of the US cohort, but the volume concentration is in India.

How do I tell an Amazon FTE from a Teleperformance or Concentrix badge contractor?

Check the employment history for TP or Concentrix tenure immediately before the Amazon role, or for the Amazon role being formally listed under a BPO employer. Refolk's index shows TP and Concentrix as the top non-Amazon employers of profiles carrying "Seller Support" in the title, so the overlap is common. The distinction decides your offer: FTEs received severance and want comp parity, BPO contractors want a conversion to a direct employer.