Amazon's Diwali Cut: 350 Marketplace SDEs, 10 Days to Move

On October 8, 2026, Amazon announced a fresh round of cuts across its US, UK, and India Stores business. The timing landed on day one of the Great Indian Festival sale, with marketplace support, seller partner services, customer service, and retail engineering roles taking most of the hit in Bengaluru, Chennai, and Hyderabad. If you source engineers in India, the next ten working days are the entire game.

What Amazon actually cut on October 8

Fewer than 1,000 white-collar roles globally, concentrated in the Stores division, with India, the UK, and the US workforces named. In India, the functions hit are the ones disproportionately staffed in Bengaluru and Hyderabad: customer service, seller partner services, marketplace support, and some retail-ops engineering.

The headline number is misleading. "Fewer than 1,000" is a global figure, but Stores operations are heavily offshored. When the denominator is India, a 1,000-person global cut routinely translates to a 300 to 500 person India concentration in exactly the SDE segments most sourcers do not have ready lists for.

Three facts worth pinning to the wall:

• Amazon employs roughly 1.2 lakh people in India. This is the third India wave in 12 months.
• Prior India layoffs in October 2025 and January 2026 removed 800 to 1,000 employees across finance, HR, marketing, and technology.
• Amazon's Bengaluru World Trade Center campus, opened March 2026 and described by Amazon as its largest office in Asia, is the physical center of gravity for the cut.

Cumulatively, the ex-Amazon India tech alumni pool from this cycle is now well over 2,000 people. The Oct 8 round is the freshest cohort, and the only one still unanchored.

Why the Diwali timing is the opportunity, not the obstacle

Outreach landing between October 9 and October 11 catches candidates before US and EU recruiters wake up to the India list the following Monday. Conventional sourcing wisdom says Indians will not job-hunt during Diwali week; the opposite is true this cycle.

Three mechanics work in a first-mover's favor:

1. Severance clocks start now. Candidates are not deferring the search to November. They are triaging options this week.
2. Families are physically together for the festival. This is the decision-making moment for a career change, not a quiet one.
3. News spread via internal Slack as the Great Indian Festival sale began. Candidates are already comparing notes with peers; the social proof for leaving is live.

There is a second deadline on the same clock. Business Insider reported that Amazon has been approaching former employees, including some who were laid off, for roles in AI, machine learning, and cloud computing. Any outbound you send after roughly the ten-day mark competes with a boomerang offer at Amazon pay-band, from a recruiter the candidate already trusts.

350

The directly addressable base, in numbers

The India SDE pool is huge, but the marketplace-specialist slice inside it is small enough to saturate in a weekend. That asymmetry is the whole play.

Here is the shape of the pool, pulled from Refolk's index of professional profiles:

Two takeaways from the table.

First, the marketplace-engineer pool is roughly 50x scarcer than the generic India SDE pool (350 against 17,695). Catalog, FBA, pricing APIs, seller onboarding flows: this is domain knowledge Meesho, Flipkart, Myntra, Walmart Marketplace India, Zepto, and Nykaa cannot grow in-house in a quarter. If you own a complete list of these 350, you own the next six months of marketplace hiring in India.

Second, the 4.3x ratio of senior AWS engineers to marketplace specialists is a comfort number for candidates, not for sourcers. There are plenty of landing pads for the generic AWS senior; your competition is everyone. For the marketplace specialist, the landing-pad shortlist is maybe ten companies, and your reply rate will reflect that.

The 48-hour sourcing playbook

Run three parallel loops between October 9 and October 11, each tuned to a different signal. Nobody wins this window with a single Boolean.

Loop 1: The signal flip

Watch for behavioral tells, not for the word "layoff":

• LinkedIn Open to Work green ring appearing on profiles currently listing Amazon.
• GitHub bio edits removing "@amazon" or "Amazon India" within a 72-hour window.
• Blind posts tagged "Amazon" from Bengaluru, Hyderabad, or Chennai referencing severance, Jassy, or Stores.
• New r/developersIndia threads referencing Oct 8 or Great Indian Festival.
• Spikes in membership of "ex-Amazon India" LinkedIn alumni groups (these jumped after January 2026 and will again).

Loop 2: The named-niche Boolean

The 350-profile marketplace pool is small enough to brute-force. For LinkedIn and GitHub searches, combine:

• Current or past employer: Amazon or Amazon Development Centre India
• Location: Bengaluru, Bangalore, Hyderabad, Chennai
• Keyword: marketplace OR "seller central" OR "seller partner" OR SPS OR FBA OR "catalog systems" OR "pricing service"
• Title variants: SDE, SDE II, SDE III, Software Development Engineer, Senior Software Engineer
• Negative filter: AWS Bedrock, Kuiper (unless you specifically want adjacent orgs)

Describing a shortlist like this in plain English, instead of writing eight Boolean variants by hand, is the exact friction Refolk exists to remove. You ask for "SDEs in Bengaluru who worked on Amazon Seller Central or FBA in the last three years" and get a ranked shortlist across LinkedIn, GitHub, and the open web, without re-running the search every time the title or employer field changes.

Loop 3: The quiet GitHub tells

Amazon marketplace engineers rarely publish company code, but they leave fingerprints. Look for:

• Contributors to open-source SDK clients for Amazon's Selling Partner API (SP-API) or MWS.
• README edits removing Amazon affiliation in the last 90 days.
• Bengaluru or Hyderabad timezone commit patterns on retail-adjacent repos (OMS, catalog ingestion, pricing engines).

Who they will land with, and how to beat those offers

The ten landing pads to pre-empt are Flipkart, Meesho, Myntra, Walmart Marketplace India, Zepto, Nykaa, Jio Platforms, and the India arms of Shopify, eBay, and Rakuten. Amazon's own boomerang desk is the eleventh and most dangerous.

Three ways to outcompete the obvious offers:

• Specificity beats brand. A message that names "Seller Partner Services tier-2 escalation tooling" outperforms a message that says "we loved your Amazon experience." The 350-profile pool knows the difference instantly.
• Compress the loop. Marketplace specialists hired in late October usually onboard by December. If your interview process runs longer than 10 business days, you lose the candidate to someone whose does not.
• Pre-empt the boomerang. Ask directly in message two: "Has anyone from Amazon re-approached you about an AI or AWS role yet?" The answer tells you how many days of runway you have.

Every day you wait on this list, your reply rate halves and the boomerang desk closes another door.

Build the persistent list, not a one-off blast

The sourcers who win the next six months treat Oct 8 as the latest entry in a running Amazon India alumni list, not a standalone event. Three cycles in 12 months have put over 2,000 ex-Amazon India tech people on the market, and the next one is a quarter away.

A persistent list means three things in practice:

1. A living query, not a saved search. Re-run the Boolean weekly against current-employer changes. People who are still "Amazon" on October 9 may be "Open to Work" on October 23.
2. Signal-weighted scoring. A profile with a GitHub bio edit plus a Blind post plus a tenure of 4+ years in Stores is a hotter lead than a generic Open to Work flip. Score accordingly.
3. A sourcing tool that updates with the web. Static exports from LinkedIn Recruiter rot in a week. Point Refolk at a query like "ex-Amazon Stores engineers in Bengaluru hired between 2021 and 2024" and the list refreshes as profiles change, with new matches arriving without re-running anything.

For founders at Series A marketplace or logistics startups, this is also the cheapest senior-engineer market India will offer in 2026. Senior AWS talent with real Amazon tenure is normally a six-month hunt. For the next ten days, if you know which 350 names to prioritize, it is a weekend's work.

FAQ

How many engineers did Amazon actually lay off in India on October 8, 2026?

Amazon has not published an India-specific number. The global figure is fewer than 1,000 white-collar roles, concentrated in the Stores division. Because Stores operations (customer service, seller partner services, marketplace support, and some retail engineering) are disproportionately offshored to Bengaluru, Hyderabad, and Chennai, the India concentration in these specific SDE segments is almost certainly a meaningful fraction of the global cut. Treat the Oct 8 cohort as the top of a cumulative ex-Amazon India tech alumni pool that has grown past 2,000 across the October 2025, January 2026, and October 2026 rounds.

Why does Diwali week help rather than hurt sourcing?

Severance clocks start on announcement day, not after the festival. Candidates are home with family (the single most common moment for a career-change decision), and news is already spreading on internal Slack, Blind, and r/developersIndia. US and EU recruiters typically wake up to India lists the following Monday or Tuesday, so Oct 9 to Oct 11 is the quietest competitive window of the quarter.

Should I prioritize marketplace specialists or general AWS senior engineers?

Marketplace specialists, by a wide margin, if you have a product that uses their context. Refolk's index shows roughly 350 India profiles in the "Amazon marketplace / seller" niche against 17,695 generic India SDEs, a ~50x scarcity. The 1,522-strong senior-AWS pool is the comfortable fallback, but every scale-up in India is sourcing against it. Marketplace, catalog, and SP-API experience is a defensible moat that the ten likely landing pads cannot grow internally.

How do I compete with Amazon's own boomerang offers?

Move inside 10 days and ask directly whether the candidate has already been re-approached. Amazon's boomerang desk is focused on AI, ML, and cloud roles, so marketplace and Stores-engineering specialists are often lower on its priority list, which gives you an opening if you are hiring for marketplace, logistics, catalog, or pricing. Specificity in your first message (name the exact team, the exact system, the exact tech) beats a generic Amazon-brand nod every time with this pool.