# Amazon's Stores Engineers Leave by Jan 25. Its Transfer Desk Calls First

_About 95 Amazon Stores staff leave Dec 7 to Jan 25, and Amazon is pitching them internal jobs first. How to time offers and find profiles that just say Amazon._

- Canonical URL: https://www.refolk.ai/blog/amazon-stores-layoffs-engineers-transfer-window
- Published: 2026-11-11
- Reading time: 9 min
- Keywords: Amazon layoffs software engineers hire, Amazon WARN notice November 2026, Amazon Stores layoffs engineers, recruit laid off Amazon engineers, Amazon 90 day notice period start date

If Jan 25 is your deadline to hire laid-off Amazon Stores engineers, you're competing for whoever is left. Any engineer who takes an internal Amazon job before their separation date is never laid off, and Amazon is already pitching AWS and AI roles to the people it cut.

Amazon's Washington WARN notice was filed Nov 2 and made public the evening of Nov 3. It puts about 95 employees on separation dates running from Dec 7, 2026 to Jan 25, 2027. Most recruiters will read that as a two-month window. It's shorter than that, because Amazon's internal transfer hunt has already started.

## What does the Amazon WARN notice from November 2026 cover?

It covers about 95 Washington employees from Amazon's October retail cuts. It is not a new layoff round. An Amazon spokesperson told GeekWire the filing belongs to the cuts the company had already announced.

A WARN notice is a public filing that employers have to make before a layoff of qualifying size. This one tells you:

- **Sites:** Bellevue, Redmond, Seattle, Pasco and Sumner, plus 15 remote workers who live in Washington.
- **Roles:** software engineers, product managers and operations staff.
- **Notice:** at least 90 days. Amazon pointed out that WARN "requires only 60 days' advance notice."
- **Separations:** Dec 7, 2026 through Jan 25, 2027.
- **Contact:** Guy Palumbo, Amazon Public Policy, is the person named on the letter.

Layoff emails went out Oct 6, in the middle of Prime Big Deal Days. They hit customer service, selling partner support and retail engineering. Amazon confirmed the cuts through spokesperson Brad Glasser, and the total was fewer than 1,000 people across the US, India and the UK. A separate Oct 28 cut removed up to 250 jobs in Devices & Services, most of them software roles. All of this follows 14,000 cuts in October 2025 and 16,000 in January 2026.

> **4,858** Amazon corporate employees laid off in Washington since late 2025
>
> That's from state filings. The 95 Stores roles are the latest addition.

So Seattle has plenty of ex-Amazon engineers. The Stores group is different because its people are still on payroll, and Amazon is still recruiting them.

## Why is the real deadline Amazon's internal transfer window?

The WARN notice says that employees who get another Amazon job before their separation date won't be laid off, and Amazon is actively recruiting them for those jobs. Your competition for a Stores engineer is an Amazon recruiter with an open req, not another startup.

Each piece of the transfer process favors staying:

1. **An internal move cancels the layoff.** The engineer simply stays employed.
2. **Internal candidates go first.** In the 2025 round, Amazon said its "recruiting teams will prioritize internal candidates."
3. **Amazon is calling them.** The company has been contacting former employees, including people from earlier layoffs, about AWS and AI openings. One of those efforts was internally named "Swami's Boomerang Reengagement Initiative."
4. **The internal offer comes with a deadline.** After the January layoffs, a poster in Blind's "Amzn Internal" channel said they took an internal offer "as there was a deadline."

That last point is the key one. An internal offer has a date on it. Yours probably doesn't, and the engineer won't turn down a sure thing while waiting on an outside process that might not finish. If your offer lands after Jan 25, it's going after people Amazon has already kept. The Dec 7 group has even less time: from the day the notice went public, their internal window closes in roughly a month.

> Your rival for these engineers isn't a startup. It's an Amazon recruiter with an AWS req and a deadline.

Most outside hiring processes can't move that fast. If sourcing alone eats weeks before anyone gets a first screen, and the interview loop then runs into December, the internal recruiter has closed the deal before your offer is ready.

## When should a laid-off Amazon engineer's start date be?

Set it after their separation date, which falls somewhere between Dec 7 and Jan 25. That way they collect all their notice pay, plus any severance, before they start with you. But ask about their own terms first, because reporting says those terms vary.

This is the part of the Amazon 90-day notice period that outside employers usually get wrong. People laid off in October got 90 days on payroll to find another Amazon job or look outside. Severance reportedly depends on tenure. If you push for a December start, the engineer may be choosing between your offer and money they've already earned. I couldn't confirm whether leaving early forfeits pay. Coverage tells affected workers to check how an early exit affects them, so treat it as an open question for each person.

| Date | Event | What it means for you |
|---|---|---|
| Oct 6, 2026 | Layoff emails during Prime Big Deal Days | Notice period begins |
| Nov 2 to 3 | Washington WARN notice filed, then public | Sites and role types confirmed |
| Dec 7, 2026 | First separations | Earliest group's internal window closes |
| Jan 25, 2027 | Last separations | Final internal window closes |

Ask each candidate these questions on the first call:

1. What is your exact separation date?
2. Would starting before that date cost you notice pay or severance?
3. How long have you been at Amazon? (Severance reportedly scales with it.)
4. Are you interviewing internally right now, and when do those decisions happen?

The calendar works for you if you use it. These engineers get paid through the holidays, so they're in no hurry. Make the offer in December and set the start date after their separation date. You'll arrive just as they make their last real choice between an internal transfer and an outside offer, and starting with you won't cost them notice pay.

## Why do their profiles only say "Amazon"?

Amazon engineers describe themselves by company, not by organization. In Refolk's index of professional profiles, 6,728 US profiles have a "Software Development Engineer" title and "Amazon" in the headline, and exactly one of them mentions "Amazon retail."

> **1 of 6,728** US Amazon SDE headlines that mention "Amazon retail"
>
> That's about 0.015%. Searching headlines for "retail" misses almost every Stores engineer.

Three things cause this:

- **The title is the same everywhere.** "Software Development Engineer" is the job title across AWS, Devices and Stores, so the title tells you nothing about the org.
- **Org names stay internal.** Names like Stores and Selling Partner Services mean a lot inside Amazon and little to an outside recruiter, so engineers leave them off their headlines.
- **"Not AWS" doesn't mean retail.** In a 25-profile US sample, 18 listed "Amazon" as their employer and 7 listed "AWS." Excluding AWS still leaves Devices and every other non-cloud group.

| Segment | Count | Note |
|---|---|---|
| US, SDE title + "Amazon" in headline | 6,728 | Refolk's index |
| India, same filter | 1,594 | Refolk's index |
| US to India ratio | 4.2x | Derived |
| US, SDE + "Amazon retail" in headline | 1 | About 0.015% |
| US sample: "Amazon" vs "AWS" as employer | 18 vs 7 | 25 profiles, directional only |
| US sample in Greater Seattle | 8 of 25 | 25 profiles, directional only |

The location numbers are a warning too. Only about a third of the sample sits in Greater Seattle. A Seattle filter plus "Amazon" gives you a pile of unsorted SDEs and still leaves out most of the people who match.

Keyword search can't handle this well, and it's the reason I built [Refolk](/). You describe the engineer the way you'd describe them to a colleague, and Refolk reads the experience text on the profile, not just the headline.

> **Example search:** "Software engineers at Amazon in Washington whose experience mentions Selling Partner Services, Amazon Stores, Amazon Tax, or Amazon Payment Products, excluding AWS" - [run it on Refolk](https://www.refolk.ai/s/vkc6ask9pn)
>
> You get a ranked shortlist of retail and marketplace engineers, with the matching experience line shown for each one.

## How do you find retail and marketplace engineers whose profiles just say "Amazon"?

Search the experience sections for the team names that show up in Amazon's own job titles. Then narrow by the Washington sites and filter out the orgs that weren't part of this cut.

1. **Team names first.** Amazon job titles use names like "Amazon Stores," "Amazon Tax," "Amazon Payment Products" and "Selling Partner Services." Engineers copy these into their experience sections even when their headlines leave them out.
2. **Domain vocabulary second.** Look for project descriptions that mention seller tooling, tax or payments. One of those words alone is weak evidence. Two together, plus a team name, is a strong match.
3. **WARN sites third.** Narrow to Bellevue, Redmond, Seattle, Pasco and Sumner, and add Washington-based remote engineers. The filing names 15 of them.
4. **Exclude by default.** Leave out AWS-titled profiles, and leave out Devices & Services unless you want that cut too. Its Oct 28 round of up to 250 roles is a separate cut.
5. **Read the room.** Blind's "Amzn Internal" channel shows how people feel about internal transfers, and GeekWire's Todd Bishop covers the local filings.

Doing this by hand takes an afternoon of Boolean strings that break whenever someone writes "SPS" in place of the full name.

## Why does the WARN list miss most of the people Amazon cut?

The 95 Washington roles are roughly a tenth of the fewer than 1,000 people affected. Staff in India and the UK, and US staff below state thresholds, never show up in a public filing.

WARN applies when a layoff crosses a size threshold, and it is a US requirement. India has no public layoff list. Yet Refolk's index shows 1,594 Indian profiles with an SDE title and "Amazon" in the headline. US profiles outnumber India's 4.2 to 1, so India's pool is far from small. A recruiter who only reads filings is looking at the Washington tenth and missing the rest.

Teams hiring in India or the UK can't check a filing to find these people. They have to search profiles: the same team-name method from the section above, with location swapped for India or the UK. That approach also catches US engineers who fell below the threshold.

## What should your first message to a laid-off Amazon engineer say?

Start with timing and money, then the role. The engineer is comparing you with an internal transfer that has a deadline, so your message has to show you've accounted for that.

- **Name their window.** Something like "Your separation date is somewhere between Dec 7 and Jan 25, and the start date can sit after it."
- **Name their domain.** Mention retail, marketplace or payments so they can tell you looked past the word "Amazon" in their headline.
- **Commit to a speed.** Give your process length in days, and promise an offer before their internal decision date.
- **Make the honest contrast.** Explain what your role offers that an AWS or AI req doesn't: scope, ownership, or a product that's the company's main business rather than a side project.
- **Ask the terms question.** Find out how an early start would affect their pay before you pitch a date.

> **Senior engineering roles open now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&seniority=senior)
>
> Current senior engineering postings, for comparing your role against the market these engineers are looking at.

## FAQ

### Are the Amazon Stores layoffs a new round?

No. An Amazon spokesperson confirmed to GeekWire that the Nov 2 Washington WARN notice belongs to the retail cuts announced in October. The emails went out Oct 6 and affected fewer than 1,000 people across the US, India and the UK. The filing just made the Washington share public: about 95 roles, including 15 remote workers who live in the state.

### How many Amazon employees have been laid off in Washington?

State filings show 4,858 Amazon corporate employees laid off in Washington since late 2025. The Nov 2 notice adds about 95 retail roles across Bellevue, Redmond, Seattle, Pasco and Sumner. Company-wide, those Washington cuts sit alongside 14,000 cuts in October 2025 and 16,000 in January 2026.

### Can a laid-off Amazon engineer start a new job before their separation date?

Possibly, but it may cost them money. They're on payroll for at least 90 days, and severance reportedly depends on tenure. Reporting says terms vary, so ask each candidate what an early start would mean for them. The safe default is a start date after their separation date.

### Why not just wait until after Jan 25 to recruit them?

Because by then the strongest candidates may have moved internally. Under the WARN notice, an internal Amazon job taken before separation cancels the layoff. Amazon is pitching AWS and AI roles to these people now, and in the 2025 round it said its recruiters would prioritize internal candidates. Anyone still looking after Jan 25 is someone the internal process didn't keep.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_