Amazon's 90-Day Internal Transfer Clock: The Resume Rewrite

Amazon confirmed 16,000 more corporate cuts on January 28, 2026, and most US employees got the same terms: 90 days to find an internal role before severance kicks in. The internal req system was built for happy-path career moves, not a stampede of laid-off L4s through L7s competing against each other for shrinking headcount. If your application is stuck in "pending informational" a month in, the problem is rarely the ATS, and it is almost never your Leadership Principles stories.

What the 90-day clock actually is

Amazon's 90-day internal-transfer window is a soft severance runway: US employees affected by the January 2026 cuts have roughly 90 days to secure another role inside Amazon before separation, outplacement, and continued health insurance formally trigger. Miss the window and you exit; find and accept a req in time and you keep tenure, RSUs vest as scheduled, and the layoff never lands on your resume.

The scale is why the internal market is broken right now:

• 16,000 corporate roles cut on January 28, 2026, on top of ~14,000 in autumn 2025, together a ~10% reduction of Amazon's corporate workforce.
• A Washington State WARN filing put 2,198 affected positions in WA alone, with separations rolling from April 28 through late June, which is the 90-day window drawn on a calendar.
• Cuts are concentrated in AWS, Alexa, Prime Video, Devices, Advertising, Last-Mile Delivery, Kindle, and supply-chain optimization within fulfillment.

Which means, in practice, that a laid-off Alexa PM applying to an AWS req is competing against a Devices PM and a Prime Video PM applying to the same req. The internal codename for the round, leaked via a calendar invite, is Project Dawn. Beth Galetti, Amazon's SVP of People Experience and Technology, signed the memo. Andy Jassy has framed the whole restructuring as AI-driven flattening. None of that context makes your resume better, but it explains why hiring managers are so slow: they are being flooded, and they know more cuts are coming.

Why "pending informational" is the real failure mode

"Pending informational" almost never means the system is slow. It means the hiring manager is watching the applicant queue grow and quietly waiting to see who else surfaces before committing to a loop. Blind threads keep surfacing the same three patterns from laid-off Amazonians:

1. Reqs get pulled mid-loop. One L5 PM: "Had an internal transfer lined up but the role was canceled."
2. Loops finish, then the req fills with someone else. One SDE3: "A few roles got filled before I finished interviewing. I've got several that are just sitting in 'pending' informational, the HM has not even responded."
3. Cross-country reqs collide with the garden-leave clock. "Got laid off, SDM is calling me tomorrow about an offer to transfer internally. I'd have to move across the country. My garden leave ends next week."

The mechanism behind pattern one is budget. When a VP freezes headcount mid-quarter, the req vanishes and every candidate in the loop becomes a rounding error. Pattern two is worse because it is behavioral: the HM has ten internal applicants for a role that used to draw two, and the cost of waiting a week is close to zero for them and catastrophic for you. Pattern three is a calendar problem the resume cannot fix, but you can pre-empt it by naming your relocation constraints in the resume summary so HMs self-select out early instead of ghosting late.

Any Amazon internal transfer plan has to be built around the assumption that at least a third of the reqs you apply to will die or fill silently. That is not pessimism, that is the base rate people are reporting on Blind right now.

Confirm your eligibility flag on day one, before you touch the resume

The single most-missed step in a 90-day internal job search at Amazon is confirming that you can actually apply. Two silent blockers show up repeatedly in Blind threads:

• Being under the 12-month tenure mark can block internal transfers by policy.
• Being on an active coaching or performance plan can block the internal job portal entirely.

A perfect resume does not help if the "apply" button is greyed out. Before you spend a weekend rewriting bullets, open a ticket with HR Partner or your resource manager and get written confirmation that your account is flagged for internal-transfer eligibility under the impacted-employee policy. Do it on day 1 of the window, not day 30.

Once eligibility is confirmed, screenshot the confirmation. You will need it if your applications sit in a pending state longer than two weeks and you have to escalate.

The math: internal is not a fallback, it is the primary shot

For most senior ICs affected by Project Dawn, the internal transfer is mathematically the highest-probability path, because the external market for their exact profile is undersupplied with roles, not candidates. In Refolk's index of professional profiles, the pool of AWS-skilled senior-plus engineers in the US is smaller than the WA-only impacted cohort:

The ratio of AWS-skilled senior-plus engineers in the external market (~1,550) to WA-impacted Amazonians alone (2,198) is roughly 0.7x. And in Refolk's index of the Amazon-tagged corporate PM/TPM pool, Amazon itself is the top current employer by roughly 4x the next competitor, Meta. Translation: for PM and TPM reqs specifically, "internal transfer competition" and "external competition" are largely the same people, and the near-market supply is dominated by other Amazonians.

The internal mobility resume: shorter, sharper, org-specific

An internal mobility resume for Amazon should be shorter than the external version you would send to Meta or Stripe, and every bullet should point at the target team's stack, not your current team's charter. The internal HM already trusts your Leadership Principles framing because you cleared it once. What they cannot see from your BIS profile is whether you fit their org's specific problems in the next quarter.

Concretely, cut the external-market instincts:

• Drop the two-page keyword bulleted history. Internal reviewers do not run your resume through an external ATS.
• Drop the "led a team of X" summary line if X is old scope. Recent scope in the last 12 months is what internal HMs weight.
• Drop the Alexa/Devices/Prime Video jargon in a resume aimed at AWS. It reads as tourist to an AWS HM in the 20-second scan.

Add what internal HMs actually search for:

• A three-line summary naming the target org, the adjacent org you are coming from, and the specific technical or business surface where you already overlap.
• Two to four bullets per recent role, each starting with a system or product name the target org would recognize (S3, Bedrock, Ads DSP, Kuiper, and so on), not with a verb.
• One "recent scope" block: last 12 months, headcount influenced, revenue or cost touched, launch dates.
• Relocation and start-date constraints listed plainly at the bottom. If you have a garden-leave date, put it there.

This is the exact rewrite work Refolk takes off you: paste the internal posting, get your resume back rewritten for that specific org's vocabulary, with the summary line and recent-scope block front-loaded for the 20-second scan.

Rewriting for a cross-org transfer: Alexa to AWS, Devices to Ads

Cross-org internal transfers require re-narrating the resume in the target org's vocabulary, because Amazon HMs pattern-match hard on org-specific jargon and roughly half the near-market PM/TPM supply lives in Greater Seattle (8 of the top 25 profiles in Refolk's index, plus 5 more explicitly in Seattle city). The HM reviewing your req likely walked past your building this morning and has strong priors about what "Alexa work" or "Devices work" means. If your bullets still read like your current org's OP2 doc, they will bounce.

Three concrete rewrites that show up repeatedly:

Alexa to AWS

• Before: "Owned NLU model quality for Alexa Skills, driving 12% intent-accuracy lift."
• After: "Shipped ML inference pipeline on SageMaker + Lambda serving 40M daily requests at p99 120ms, model quality lift 12%."

The AWS HM does not care about Skills. They care that you have run production ML on AWS primitives at scale.

Devices to Advertising

• Before: "Led hardware forecasting for Echo Show 12, reducing stockout risk 30%."
• After: "Built demand-forecasting models feeding a $400M P&L, driving pricing and inventory decisions weekly against 30% stockout-risk reduction."

Ads HMs are hiring for measurement, attribution, and P&L instinct. Reframe hardware forecasting as a P&L and modeling story.

Prime Video to AWS

• Before: "Owned content-encoding pipeline for live sports on Prime Video."
• After: "Owned MediaConvert + S3 + CloudFront pipeline for tier-1 live events, 3M concurrent viewers, 99.98% availability."

Same work, AWS's product names. The HM's eye stops on MediaConvert, not on Prime Video.

What to do in weeks 1, 6, and 10

The 90-day window collapses into three phases, and the resume you send in week 1 is not the resume you should be sending in week 10.

• Week 1. Confirm eligibility with HR in writing. Rebuild the master resume as an internal artifact (three-line summary, 12-month scope block, target-org vocabulary). Apply to the three highest-fit reqs only, not twenty. Reach out to two skip-levels and two cross-org peers who can pre-brief HMs.
• Week 6. Audit every "pending informational" application older than 14 days. If the HM has not responded, kill the application and apply somewhere else. Sitting in the queue is worse than being visibly interviewing elsewhere. Start a parallel external search, because the AWS-skilled-senior external pool is ~1,550 and moves slowly.
• Week 10. Assume half the reqs you are in will die. Pick one internal offer to close, negotiate the start date around any garden-leave collision, and get it in writing before the day-90 auto-severance runs. If nothing has closed, use the outplacement benefit deliberately and let the severance land clean.

For the parallel external track, Refolk drafts a tailored resume and cover letter per posting and scores actual fit before you burn hours on applications where the overlap does not exist. You want signal, not volume, in weeks 6 through 10.

FAQ

Does Amazon actually pull reqs during the internal transfer window?

Yes, and repeatedly. Blind threads document reqs being cancelled mid-loop, filled while candidates are still interviewing, and left silently open in "pending informational" for weeks. The mechanism is a mix of mid-quarter budget freezes and HMs waiting to see the full applicant pool before committing. Treat any single req as a coin flip; portfolio your applications accordingly.

How is an internal transfer resume different from an external one?

It is shorter, more recent, and written in the target org's vocabulary. Internal HMs already trust the Leadership Principles framing and do not run your resume through an external ATS, so keyword stuffing and long historical bullet lists hurt more than help. Front-load a three-line summary naming the target org and the surface where you overlap, plus a 12-month recent-scope block. That is the artifact an internal HM will actually scan.

Should I confirm eligibility before I start applying?

Confirm it on day 1, in writing, before you touch the resume. Being under 12 months of tenure or on an active coaching plan can silently block the internal job portal. A perfect resume is worth nothing if the "apply" button is greyed out. Screenshot the confirmation in case you need to escalate a stalled application later.

What if the 90 days runs out with nothing closed?

Take severance cleanly and pivot to the external market with the understanding that, in Refolk's index, the AWS-skilled senior-plus pool is only around 1,550 people in the US, which is smaller than the WA-impacted cohort alone. That undersupply cuts both ways: fewer competitors, but also fewer live roles. Use the outplacement benefit deliberately, keep tenure and RSU vest dates on the resume, and rewrite for whichever adjacent employer actually has the reqs open.