Beth Galetti's January 28, 2026 memo gave most affected US employees 90 days to find a new role inside Amazon. The second wave of 16,000 corporate cuts stacks on the 14,000 from October 2025, funneling roughly 30,000 people into the same internal portal. Almost all of them will open LinkedIn first, and that is the mistake that eats the window.
The internal window is a different job market than the external one
Amazon's internal Jobfinder portal rewards Leadership Principles, product names, and Amazon-native metrics that external ATSs like Greenhouse and Workday strip out. A single resume optimized for both loses on both sides.
The mechanism is simple: an internal recruiter opening your Jobfinder profile can already see your prior team, your tenure, and your promo level through the HR system. A bullet that says "led cross-functional initiative to improve customer experience" tells them nothing they did not already infer from your title. A bullet that says "shipped Prime Video CTV playback fix that cut P90 rebuffer 41% for FireTV, cited in Q3 OP1 as Customer Obsession win" tells them exactly which req to slot you into.
External recruiters need the opposite. Greenhouse strips the acronyms. Workday flattens the LP language. Paste your Amazon-flavored bullets into a Meta or Datadog posting and half the signal disappears into a keyword mismatch.
So the play is two resumes, drafted in that order:
- Internal Jobfinder resume, done in the first 7 days of the window.
- External resume, derived from the internal one but rewritten for ATS keywords.
That first-week ordering matters because internal req volume is highest right after a RIF, before other cohorts finish grieving and start applying. Drafting the internal resume is the exact work Refolk takes off you: paste the internal req and your history, get the Jobfinder-shaped version back.
Why 30,000 cuts hit a much smaller pool of open reqs
The 90-day window is a supply shock, not a promise. Amazon says recruiters will prioritize internal candidates, but the historical baseline for internal transfer approval sits around 35%, which means roughly two-thirds of internal moves get declined in normal conditions. Layoff conditions are worse: more applicants, fewer open reqs, and hiring freezes bleeding across orgs that were not directly cut.
Here is the scale.
| Segment | Count | Source |
|---|---|---|
| Amazon corporate layoffs, Oct 2025 | 14,000 | GeekWire |
| Amazon corporate layoffs, Jan 2026 | 16,000 | GeekWire |
| Cumulative since Oct 2025 | ~30,000 | GeekWire |
| US SDE / PM / Program Manager profiles tied to Amazon | 6,908 | Refolk's index |
| US Senior PM / Senior PgM profiles tied to Amazon | 1,357 | Refolk's index |
| Share of top-25 Senior PM/PgM in Seattle | ~40% | Refolk's index |
| Seattle-area corporate Amazonians | ~50,000 | GeekWire |
| Historical internal transfer approval rate | 35% | historytools.org |
The Refolk index numbers are the ones that matter for a job seeker. Roughly 6,908 US-based Amazon SDE, PM, and TPM profiles are already indexed, and about 1,357 of them sit at Senior PM or Senior Program Manager level. Of the top 25 senior PM/PgM profiles in that slice, 10 sit in Seattle. That is the density you are competing against for a Seattle-based internal chair.
This is the pool competing for the same internal reqs during your 90-day window.
The impacted org lines named in the Galetti memo (AWS, Alexa, Prime Video, Devices, Advertising, Last Mile, Kindle, Supply Chain Optimization within fulfillment) span enough of the corporate footprint that lateral moves inside those orgs are the least likely path. Cross-org moves will do the actual work.
What the Jobfinder resume actually needs
Four things, in this order: named products, Leadership Principles tied to specific decisions, Amazon-native metrics, and the name of the hiring manager you already talked to. Everything else is decoration.
Named products, not "customer-facing platform"
Internal HMs pattern-match on product names. If you owned a service, name it: RDS Proxy, DynamoDB global tables, Kinesis Data Firehose, Ring Doorbell Pro 2, Alexa Skills Kit, Prime Video X-Ray, FBA inbound compliance. Vague product descriptions ("large-scale distributed storage service") get skipped because the recruiter cannot tell if you owned the thing or wrote a doc about it.
The tell for a weak internal resume is any bullet that would still make sense at Google. If it survives a find-and-replace of "Amazon" with "Meta," rewrite it.
Leadership Principles attached to actual decisions
Do not list the Leadership Principles at the top of your resume. Every internal reader will skim past it. Instead, attach one LP to each of your three or four biggest bullets, and only where the decision actually demonstrated that LP. Example: "Dive Deep: personally traced a 12ms p99 regression to a misconfigured connection pool in the payments service, saved rollback of Q2 checkout launch."
The pattern to avoid is what Blind threads call "LP salad": five principles crammed into one sentence so none of them mean anything. Pick one LP per bullet, and let the numbers do the rest.
Amazon-native metrics
Dollar impact, GMS, units, latency (p50/p90/p99), CX defect rate, contact-per-order, Weekly Business Review call-outs, OP1 or OP2 line items. These are the units internal recruiters and HMs already use daily, so a bullet in those units gets scored higher than the same accomplishment in generic terms.
If your metric is not one Amazon uses, translate it. "Increased engagement" becomes "cut customer contacts per order by 8%." "Improved reliability" becomes "held p99 under 200ms across peak weeks including Prime Day 2025."
The hiring manager you already talked to
This is the highest-signal line on the entire resume, and most people leave it off. Above the fold, in the summary: "In conversations with [HM name], [org], about the [role] req." That single line moves your resume from the general pool to the priority stack.
The mechanism is manager notification. Per Blind threads on Amazon internal transfer, hitting apply on Jobfinder pings a manager contact through the HR system. During a RIF, that ping often lands on the manager whose team just eliminated your role, which is awkward but survivable. What is not survivable is a cold Jobfinder application where the HM has zero prior context. Internal recruiters treat "HM already knows you" as a strong signal because it means one less loop to schedule.
The Oracle parallel and the 6 am lockout problem
Oracle's September 14, 2026 round is running the same internal-window play, with a twist: employees lost system access before receiving termination emails, some around 6 am, with the cuts starting in the US before reaching Indian teams the next day. That means any resume rewrite has to be draftable from a personal device, from memory and personal notes, without access to the corp laptop or the internal directory.
The lesson for Amazon employees currently inside the window (or inside the "any day now" pre-notification zone): pull your artifacts to personal storage today. That means:
- Your last three performance reviews (or promo doc if you have one)
- Your team roster and org chart, screenshotted
- Your OP1/OP2 goal docs, or your summary of them
- The list of services, dashboards, and runbooks you owned
- Every WBR or MBR you presented at, with dates
Once you are locked out, none of this is reachable. A resume drafted from memory two weeks after a lockout will be missing exactly the specific numbers that make internal HMs move.
Oracle laid off about 21,000 workers in fiscal year 2026 (ended May 2026), and the September round hit multiple departments with some teams cut more than 10%. The internal mobility resume playbook is the same at Oracle as at Amazon: rewrite for the internal portal first, in the first week, with product names and native metrics.
A resume that survives find-and-replace from Amazon to Meta is not an internal resume. It is a hedge that loses both bets.
The 7-day rewrite plan
Do these in order, in the first week of your window. The plan assumes you still have system access; if you do not, skip step 1 and rebuild from personal notes.
- Day 1: pull artifacts. Reviews, promo doc, org chart, OP docs, service list. To personal storage.
- Day 2: list every product and metric. One line each. Do not write bullets yet. Just inventory: what did you own, what was the number, what LP did the decision demonstrate.
- Day 3: draft the internal Jobfinder resume. Product names, one LP per bullet, Amazon-native metrics, HM contact line at the top. One page.
- Day 4: identify 5 to 10 internal reqs and the HMs behind them. Use Jobfinder search and your Slack network. Warmest first.
- Day 5: informal HM outreach. Chime or email, one paragraph, before you apply. "I saw the req, here is why I fit, can we talk 15 minutes."
- Day 6: apply on Jobfinder, referencing the HM conversation in the resume summary.
- Day 7: draft the external resume. Same accomplishments, translated out of Amazon jargon, keyword-loaded for Greenhouse and Workday.
Why applying externally first is the expensive mistake
The instinct after a RIF is to blast LinkedIn Easy Apply and feel productive. It is rational-looking and it burns the window. External applications take days or weeks to convert, external ATSs strip the Amazon-flavored bullets you need for Jobfinder, and every day you spend polishing an external resume is a day the internal req shortlist gets built without you on it.
The 35% historical internal-transfer approval rate is the pessimistic anchor. It is still higher than the external interview rate for a cold Amazon SDE applying to Meta with no referral. Internal is the higher-EV channel in weeks one through six, external takes over in weeks seven through twelve, and by week thirteen the window is closed regardless.
The two-resume strategy is not extra work. It is the same underlying career history, rendered twice. Refolk writes both from your own history and scores how well each one fits the specific req you are targeting, so you spend the 90 days applying instead of rewriting.
FAQ
Does applying to an internal role really notify my current manager if I have been laid off?
Yes, in most cases. The Jobfinder apply action routes through the HR system, and the "current manager" field still points at your pre-RIF manager during the severance window. Blind threads consistently report this. The workaround is not to skip the application, it is to have the HM conversation first and let your current (or former) manager know before the notification lands, which is standard Amazon transfer etiquette anyway.
How many internal roles should I apply to during the 90 days?
Aim for 5 to 10 targeted internal applications with prior HM conversations, not 40 cold applies. The internal recruiting team can see how many reqs you have applied to; a spray pattern reads as low signal. Depth beats volume inside the window because the internal pool is small and the recruiters talk to each other.
What if my whole org was cut, so there is no lateral move inside it?
Cross-org moves are the norm during a RIF window, not the exception. The Galetti memo named AWS, Alexa, Prime Video, Devices, Advertising, Last Mile, Kindle, and Supply Chain Optimization as impacted, which covers most of corporate. The move is to look at orgs that were not directly cut and rewrite your bullets to emphasize transferable primitives (systems design, cost optimization, launch operations) rather than the exact product you owned.
Should I bother with the external resume at all if internal is higher EV?
Yes, starting day 7. External conversion is slower, so the pipeline needs to be running by week two even if you expect to land internally. If the internal window closes without an offer, you want interviews already scheduled externally, not a blank calendar. Draft the external resume once, then tailor per posting rather than rewriting from scratch each time.