Amazon's 14,000 Cut: Two Resumes Before the 90-Day Badge Flips

On October 28, 2025, Amazon told roughly 14,000 corporate employees they have about 90 days to find a new role inside the company before severance kicks in. The memo frames that window as a soft landing, but the mechanics are brutal: you are competing against your laid-off peers for a shrinking internal req list, and the moment the badge dies, "Amazon" on your resume starts reading as "severance package" to every external recruiter. You need two resumes in parallel, and you need both of them finished this week.

What Beth Galetti's memo actually said, and what it did not

Amazon's SVP of People Experience & Technology, Beth Galetti, confirmed a reduction of approximately 14,000 corporate roles, with most affected employees given 90 days to find a new role internally (timing varies by local law) and recruiters told to prioritize internal candidates. That is the sentence everyone is quoting. The parts people are missing matter more.

• The 14,000 is roughly 4% of Amazon's ~350,000-person corporate workforce (the last public figure from early 2023).
• Reuters reporting flagged by GeekWire suggests the total could ultimately reach ~30,000 as cuts continue into 2026, which would exceed the 27,000 eliminated in 2023.
• Galetti's stated goal is "fewer layers and more ownership," language Andy Jassy has repeated as he pushes Amazon to feel like "the world's largest startup."
• Amazon had nearly 1.2 million total employees as of October 31, 2024, with more than 360,000 in corporate.

The "fewer layers" phrase is not corporate throat-clearing. It is a hiring instruction. Any internal manager posting a req this quarter is reading the same memo you are, and they will not backfill a Manager-of-Managers slot. That changes what belongs at the top of your internal resume, and it changes it today.

The 90 days is not one window, it is two

Treat the 90 days as two separate hiring markets with a payroll-status flip in the middle, because that is how Amazon's systems treat it. Day 1 through roughly Day 60 is pre-separation: you are still badged, still in the internal directory, still eligible to be "transferred." Day 61 through Day 90, and anything after, is post-separation: multiple employees on Blind and Glassdoor report that once laid off, Amazon's systems treat them as terminated and they must reapply as external candidates with rehire eligibility, not as internal transfers.

That distinction is why one laid-off PM reported applying to six highly relevant internal roles out of about 50 openings and getting desk-rejected on all six, with only the automatic rejection message, no hiring manager response. A counter-example on Blind described a manager who said their org was prioritizing laid-off people and keeping interviews simple. Both can be true. The signal: priority is a recruiter-level instruction, not a system-level guarantee, and it decays fast.

Here is the structure to internalize:

Start the external resume on Day 1, not Day 61. The internal portal is a lottery with 14,000 ticket-holders. The external market is the real escape hatch.

Resume One: the internal Amazon version

The internal resume is a Leadership Principles translation exercise, and it goes to a specific hiring manager, not an ATS. Keep the Amazon dialect. "SDE III," "L6 PM," "PE," "PgM" are all fine, because the reader speaks the language and the internal tooling indexes on it.

What to do on the internal resume:

1. Lead with the LP you most recently got written up for in a doc. Hiring managers inside Amazon read for Ownership, Deliver Results, and Dive Deep in that order right now.
2. Quantify in Amazon's units: GMS, OP1/OP2 goal attainment, p99 latency, OE wins, ticket volume reduction, headcount leverage.
3. Name the orgs you worked in. "Consumer Payments org under RBS" lands with an internal reader. "Payments team" does not.
4. Drop a line that explicitly addresses "fewer layers." If you were a manager, show the IC artifact you still ship: the doc you wrote, the system you designed, the on-call you still take.
5. Attach the two most recent PR/FAQs or six-pagers you authored. Internal recruiters will forward them. External ones cannot read them.

Then do the thing the portal cannot do for you: email the hiring manager directly. Internal priority is a recruiter instruction; a direct note from an affected L6 to an L7 who posted a req last Tuesday converts at a rate the portal will never match. Attach the internal resume as a PDF, not a link, because the link breaks the day your badge dies.

Resume Two: the external version, before the badge tell

The external resume has one job: strip every Amazon dialect word that signals "I was just laid off" and replace it with impact a non-Amazon recruiter can price. The badge is a feature on Day 1 and a liability by Day 91, and the ATS does not care about your LPs.

The biggest translation problem is the title itself. In Refolk's index of US professional profiles, there are about 22,782 people with "Software Development Engineer" or "Senior SDE" in their current title, and 13 of the top 25 sampled sit at Amazon or AWS. The SDE title is largely an Amazon dialect. External ATS systems trained on "Software Engineer," "Backend Engineer," and "Staff Engineer" will underweight an SDE resume for reasons that have nothing to do with your code.

Fix the title line explicitly:

• "Senior Software Engineer (Amazon title: SDE III), AWS Kinesis, 2021 to 2025"
• "Staff Software Engineer (Amazon L6), Alexa Devices, 2019 to 2025"
• "Senior Product Manager, Technical (Amazon Sr PM-T), Prime Video Ads, 2022 to 2025"

Then do the same thing for every verb. "Owned OP1 goal" becomes "Led annual planning for a $40M P&L." "Wrote a 6-pager" becomes "Authored product strategy adopted by three partner teams." "Raised a SIM" becomes nothing, because nobody outside Amazon knows what a SIM is.

This translation layer is the exact work Refolk takes off you. Paste the job posting, paste your Amazon history, and Refolk rewrites the resume into the target company's dialect, drafts the cover letter, and scores how well you actually fit against the posting. For a layoff cohort trying to run two resumes in parallel against dozens of postings a week, that is the difference between finishing the external search before Day 90 and starting it after.

The boomerang track most readers are missing

There is a quiet third track running alongside the internal portal and the external market: Amazon's own rehire pipeline, which is actively reaching back out to laid-off alumni with AI/ML experience. Yahoo Finance reported that a recruiter inside Amazon's AI agent organization (overseen by AWS VP Swami Sivasubramanian) has been soliciting former employees under "Swami's Boomerang Reengagement Initiative," and AWS Finance offered a former employee an expedited interview process that led directly to an offer.

The market context makes this bigger than one program. According to ADP data cited by Yahoo Finance, returning employees made up 35% of US new hires in March 2025, up from 31% a year earlier, and in tech they accounted for nearly two-thirds of all new hires over that period. Boomerang is the dominant hiring motion in tech right now. If your resume strips out the ML-adjacent keywords because you were "really a PM," you are opting out of the biggest hiring pattern in your industry.

What to keep on both resumes to stay boomerang-eligible:

• Any model, framework, or inference infrastructure you touched, even tangentially (Bedrock, SageMaker, Triton, vLLM, LangChain, Rufus, Q).
• Agentic workflow or eval work, named by the eval harness.
• Data-labeling, RLHF, or SFT pipelines you scoped, even if you did not build them.
• The AWS service team you partnered with, by name.

Why "ex-Amazon" alone will not carry you in Seattle

In Refolk's index, about 309 US Product Managers and Senior PMs already use "ex-Amazon" as a differentiator in their headline. In the Greater Seattle Area that number is a commodity, not a signal. Add 14,000 more affected corporate employees, a meaningful share of them PMs, and the "ex-Amazon" tag becomes background noise inside a 20-mile radius of South Lake Union by Thanksgiving.

The external resume has to lead with the problem you solved and the number attached to it, not the badge. Compare:

• Weak: "Ex-Amazon Senior PM with 6 years driving customer-obsessed outcomes across Prime."
• Strong: "Senior PM who cut Prime fulfillment latency 22% and shipped a $40M ads product in 11 months. Amazon 2019 to 2025."

The badge still appears. It just stops being the headline.

A 10-day plan for the first two weeks

Run both tracks on parallel timelines, not sequential ones. Here is the sequence that fits the 90-day window:

1. Day 1 to 2: Export your performance docs, PR/FAQs, and the last two annual review packets. These are the raw material for both resumes and you lose access to some of them when the badge dies.
2. Day 2 to 3: Build the internal resume. LP-coded, Amazon dialect intact, hiring-manager-directed.
3. Day 3 to 5: Build the external resume. Strip SDE and L-levels into standard titles, requantify in dollars and percentages, keep ML-adjacent keywords.
4. Day 5 to 10: Email 10 internal hiring managers directly with the internal PDF. Apply to 20 external postings using tailored versions of the external resume. Score your actual fit against each posting before you spend an hour on the cover letter, which is where Refolk is faster than doing it by hand.
5. Day 10 onward: If you have fewer than 3 internal first-rounds by Day 30, the internal track is cooked for you. Pour the hours into external and boomerang.

The readers who finish the 90 days with an offer in hand are almost always the ones who treated Day 1 as the start of the external search, not Day 61.

FAQ

Can I actually transfer internally once I have been notified?

Yes during the 90-day window if your jurisdiction allows it, but with caveats. Amazon's memo says recruiters will prioritize internal candidates, and Blind reports confirm some managers are keeping interviews short for affected staff. However, multiple employees on Glassdoor describe being treated as terminated once laid off, with no true internal transfer available after separation, only external reapplication with rehire eligibility. Assume priority exists for the first 60 days and plan the external search in parallel from Day 1.

Should I keep "SDE" or "L6" on my external resume?

Keep them in parentheses, not as the primary title. External ATS systems and recruiters outside Amazon are trained on "Software Engineer," "Senior Software Engineer," and "Staff Software Engineer." Write the standard title first and put the Amazon equivalent in parentheses so a recruiter who does know the ladder can still map you. Refolk's index shows about 22,782 US SDE title-holders, and the title is heavily concentrated inside Amazon and AWS, so untranslated it reads as niche.

Is the Amazon boomerang program real, and who qualifies?

It is real and currently biased toward AI/ML profiles. Yahoo Finance reported active outreach from a recruiter inside Amazon's AI agent organization under "Swami's Boomerang Reengagement Initiative," and AWS Finance has already run expedited interview loops that converted to offers. ADP data puts returning employees at nearly two-thirds of US tech new hires as of March 2025, so even outside Amazon, your alumni status is more valuable than you think.

What should I do differently if I was a manager, not an IC?

Rewrite your bullets to foreground IC-equivalent artifacts: the doc you authored, the architecture you designed, the on-call rotation you still took, the customer meeting you ran yourself. Galetti's "fewer layers and more ownership" framing is now the public hiring thesis at Amazon and increasingly at other large tech employers. A manager resume that reads as "manager of managers" is a liability on both tracks right now. Lead with ship evidence, not span of control.