Amazon Wants 11,000 SDE Hires After Cutting 1,800. The Math Is a Trap.

AWS CEO Matt Garman went on stage and said Amazon will hire 11,000 software developers, interns and engineers in 2026. Three weeks earlier, WARN filings across four states confirmed Amazon had cut roughly 1,800 engineers as part of a 30,000-role corporate restructure. If you read those two numbers as a hiring boom, you are being played.

The headline number is mostly interns

Garman's 11,000 figure is not 11,000 senior SDE seats opening in Seattle. It is a pipeline number weighted heavily toward interns and new grads, and it does not reverse the 30,000 corporate cuts Amazon completed between October 2025 and May 2026.

Here is the actual shape of the year, from the reporting:

• Amazon eliminated ~30,000 corporate roles across late 2025 and early 2026, roughly 8.6% of a 350,000 corporate base.
• WARN filings in NY, CA, NJ and WA show engineers were ~40% of 4,700 tracked cuts, the source of the ~1,800 engineer figure.
• Garman announced 11,000 "software development engineers and interns" for 2026.
• Andy Jassy has said publicly that corporate headcount will keep shrinking as AI absorbs work.

So the 11,000 is a replacement-plus-skill-swap number, not net growth. For a mid-career SDE II laid off in February 2026, Amazon is not the safety net. It is competing for the same top-of-funnel it has always fed on, and it wants people cheaper and more AI-fluent than the ones it just cut.

19,000

What "1,800 engineers" actually means for your pipeline

The 1,800 number is engineers hit by publicly filed WARN notices in four states over a single reporting window. The real US-wide, identifiable, named ex-Amazon engineer pool is larger, older, and already partially absorbed.

In Refolk's index of professional profiles, there are 1,578 US-based engineers currently carrying an "ex-Amazon" signal and holding an SWE-family title today. That is the addressable pool, not a rumor of a pool. The top current employers in the sample tell you where the obvious names went:

Two things jump out. First, Amazon itself is the single largest re-employer of ex-Amazon engineers. That is the boomerang machine Garman's 11,000 is designed to feed. Second, Google and Meta have already taken the most legible names. If your outreach starts with "I noticed you left Amazon," you are already late on the top decile.

The interesting middle of the pool, the SDE IIs and Sr SDEs who did not have a Meta recruiter in their DMs on day one, is where the sourcing edge is. That is a plain-English query problem, not a boolean problem, which is the exact gap Refolk closes: you describe the person you want ("Senior SDE, ex-Amazon retail or Prime Video, laid off in the last 6 months, US, not already at Google/Meta") and get a ranked shortlist instead of a LinkedIn search that surfaces the same 40 names everyone else is emailing.

The layoffs are on a public schedule. Use it.

Ex-Amazon engineers are not hitting the market in one dump. They are hitting it in dated waves, and the dates are public. A single Washington WARN notice lists 2,303 employees separated across nine staggered dates from January 26 through May 26, 2026.

That matters because outreach timing has a narrow sweet spot:

1. Week 0 to week 1 post-separation: severance clarity lands, LinkedIn "Open to Work" toggles flip on.
2. Week 2 to week 6: peak reply rate. Candidate has decompressed, has not signed anywhere, is comparison-shopping.
3. Week 6 to week 12: top decile is already in final rounds elsewhere; conversion drops sharply.
4. Week 12+: whoever is still on the market is either holding out for FAANG-comp or has a story you will need to dig into.

The operational move is to map your outreach cadence to the WARN dates, not to blast the whole "ex-Amazon" segment on a Tuesday. If you know a wave separates on March 30, your first-touch emails go out April 6, not April 1 (too raw) and not April 27 (too late).

The 11,000 is a pipeline number weighted toward interns. It is not a life raft for the SDE II you are trying to hire.

Seattle is the arbitrage

The concentration of ex-Amazon engineers in Seattle creates a pricing advantage that does not exist in the Bay. In Refolk's index, 24% of the top-25 sampled ex-Amazon engineers are in Seattle, versus 12% in New York. Seattle is roughly 2x the next metro.

Why that matters mechanically:

• Outside Microsoft, most Seattle tech employers are dramatically smaller than Amazon.
• Local competing offers per candidate are thinner than in SF or NYC.
• Remote-first startups can pay a Seattle-competitive number without paying a Bay Area number.
• The candidate does not have to relocate, which kills the single biggest late-stage deal-breaker.

If you are a Series B founder hiring your first four backend engineers, Seattle ex-Amazon SDEs are the highest-leverage segment in the US right now. You are competing against a hiring machine that is publicly shrinking, not against Stripe and OpenAI.

The skill Amazon is actually hiring for is not what it cut

Amazon's 2026 hiring is concentrated in AWS, supply chain tech, and AI infrastructure, with an explicit preference for distributed systems, cloud-native, and data pipeline experience. Garman also said, on record, that expertise in specific coding languages will "become less valuable" and that broader problem-solving and application-building matter more.

Translate that into a sourcing brief:

• Amazon is over-indexing on systems judgment and AI-fluency, under-indexing on language depth.
• The engineers cut in the WARN wave skew mid-level, in teams (Prime Video, retail ops, HR tech, parts of AWS) that were consolidated, not necessarily under-performing.
• That mid-level cohort is exactly what most startups and scale-ups actually need, and cannot usually afford at Amazon-refresh comp.

The competing pool you should also be watching is Senior/Staff engineers with AWS listed as a skill, regardless of whether they ever worked at Amazon. Refolk's index shows 1,513 US-based Senior/Staff SWEs with AWS as a listed skill. Titles break down as ~68% Senior Software Engineer and ~24% Staff Software Engineer, distributed across Seattle, SF, Boston, Austin, and Dallas with no single metro dominating.

If your role is "backend engineer who can own our AWS footprint," you have two overlapping pools to work: 1,578 ex-Amazon engineers and 1,513 AWS-skilled Sr/Staff engineers. The overlap is small enough that you should sequence them separately.

The full picture in one table

Every number below is either from public reporting or from Refolk's index of professional profiles, marked accordingly.

The 6.1x replacement ratio is the number to keep in your head when a candidate asks "should I just wait for Amazon to rehire me?" The literal answer is that Amazon is planning to hire more than six new people for every WARN-cut engineer, but almost none of those seats are aimed at a laid-off SDE II with five years of Prime Video on their resume.

Internal morale is a live recruiting signal

Surviving Amazon engineers are publicly criticizing their own employer, which is unusual and usable. In June 2026, Amazon engineers in Seattle testified against the company at a City Council data-center hearing, and the council unanimously passed a one-year limit on new mega data center developments. Engineers went on record with their names.

Two things a recruiter should notice:

• People who publicly criticize their employer are, on average, closer to leaving than the median.
• The morale gap between "we just cut 30,000" and "we are spending $200B on AI infrastructure this year" is real, and it is showing up in public testimony and on Blind.

For sourcing ex-Amazon talent (and current-Amazon talent that is one bad quarter from ex-Amazon), the message that works is not "we are hiring." It is "we are small, we are focused, and no one here is going to reorg your team into a slide deck." That message lands harder in Seattle in Q1 2026 than it has in a decade.

The 90-day window

The sourcing squeeze is not the layoff itself. It is the compression between WARN waves and Amazon's own re-hiring, plus Google, Meta, and every AI startup with a Seattle office. Miss the window and the top decile is gone by summer.

Concretely, here is what to do in the next 90 days:

1. Pull a named list of ex-Amazon engineers by WARN separation date, not by "ex-Amazon" as a static tag.
2. Sequence outreach to hit each wave in the 2-to-6-week reply window.
3. Prioritize Seattle. That is where the price-to-quality ratio is best and competing offers are thinnest.
4. Do not lead with "we saw you left Amazon." Lead with the specific team or system they owned.
5. Skip anyone already at Google, Meta, or back at Amazon. They are not your ICP right now.

Running that as a Boolean search on LinkedIn will burn a week and surface the same names every other sourcer already burned. Running it as a plain-English query against a live index ("ex-Amazon, laid off Feb or Mar 2026, Seattle, Sr SDE, distributed systems, not at FAANG now") is a five-minute job in Refolk and produces a list you can actually sequence.

The 11,000 number will be quoted in every talent LinkedIn post for the next six months. The recruiters who win the ex-Amazon cohort will be the ones who read past it.

FAQ

How many engineers did Amazon actually lay off in 2025 and 2026?

Public WARN filings in New York, California, New Jersey and Washington account for roughly 1,800 engineers, roughly 40% of the 4,700 cuts tracked in those four states. The total corporate restructure was around 30,000 roles between October 2025 and May 2026, of which engineers were disproportionately represented relative to their share of the 350,000-person corporate base. The true nationwide ex-Amazon engineer figure is higher than 1,800 once non-WARN states and voluntary attrition are included.

Is Amazon really hiring 11,000 engineers in 2026?

Yes, but the number is mostly interns and new grads, not experienced SDE replacements. Matt Garman announced 11,000 "software development engineers and interns" for 2026, and intern classes are the primary funnel for entry-level full-time seats in 2027. For a mid-career SDE laid off in the WARN waves, Amazon's stated hiring plan is not a realistic re-entry path in the short term.

Where should I focus when sourcing ex-Amazon talent?

Seattle first, then New York, then remote-eligible candidates in Boston, Austin, and Dallas. In Refolk's index, Seattle holds roughly 24% of the sampled ex-Amazon engineer pool versus 12% in New York, and outside Microsoft the local competition for these engineers is much thinner than in the Bay Area. That geographic concentration is the single biggest arbitrage available to non-FAANG employers right now.

What is the best way to time outreach to laid-off Amazon engineers?

Map your outreach to WARN separation dates rather than blasting the whole ex-Amazon segment at once. A Washington WARN notice alone lists 2,303 employees across nine staggered separation dates through May 2026. First-touch messages sent 1 to 2 weeks after a specific wave's separation date hit the peak reply window, when severance is clear and candidates have not yet signed elsewhere but are actively comparing offers.