Microsoft's 268 Xbox Cuts: The 10 Redmond Names That Matter

Microsoft notified 277 Puget Sound workers on September 22 that they're out on November 21, buried inside a global 268-at-Xbox headline that most sourcers are reading as "500 anonymous names, somewhere on Earth." The WARN filing turns that fog into a street address: 252 of those positions sit at One Microsoft Way in Redmond. If you recruit for a competing studio, you have an eight-week window and a very small list of people to actually chase.

The 268 global number is the wrong denominator

The actionable Redmond engineering pool is a subset of the 252 One-Microsoft-Way positions, not the 268 global Xbox cut, and it's probably 60 to 100 people, not 268. Treat the headline as a TAM and you'll build a pipeline that doesn't exist.

Here's what the public reporting actually says, broken apart:

• Microsoft is cutting around 500 workers, with 268 coming from Xbox Game Studios and the rest spread across Cloud and AI.
• The Washington WARN filing lists 277 Puget Sound positions, including 252 at One Microsoft Way in Redmond and 25 remote-but-Washington-based.
• Everyone was notified September 22, and all 277 exits are scheduled for November 21.
• GeekWire specifically called out that artists, game designers, and producers were hit hard, so engineering is a share of the 252, not the whole thing.

That last bullet is the one most sourcing plans skip. If artists and producers absorb a large share of the Redmond cut, you're sourcing against a smaller engineering slice, and gameplay/engine/tools engineers are a slice of that. The exclusive, hireable Unreal and C++ pool landing on the open market from this specific filing is small enough to work by hand.

What Refolk's index actually shows for Xbox Game Studios

In Refolk's index of professional profiles, only about 6% of the public Xbox Game Studios footprint sits in the Puget Sound zone where the WARN notice is landing. That's the number that explains why the "268 globally" story feels bigger than the Redmond phone-tree you can actually dial.

A keyword pull on "Xbox Game Studios" across the US returns 161 profiles. Narrow it to the region on the WARN filing and the number collapses:

Two derived numbers matter more than any of the above. The Puget Sound share of the Xbox-tagged pool is roughly 6.2% (10 of 161), which is why the global 268 hides the Redmond signal. And of 135 US engineering profiles directly adjacent to this cut, only about 11% (15 of 135) are still badged at Microsoft. That 11% is your realistic warm-contact ceiling, before you touch WARN rosters, Washington ESD filings, or alumni networks.

10

The voluntary-exit shadow pool is 10x the layoff

Roughly 2,625 ex-Microsoft employees are already free to interview with no WARN clock on them, because about 30% of 8,750 eligible US staff took the first-ever voluntary buyout earlier this year. That shadow pool dwarfs the 268 and should be the top of your funnel, not the bottom.

Framing matters here. The layoff is a trigger, not the pool. Candidates who took the voluntary package:

1. Self-selected out, so they are open to outreach by definition.
2. Left with severance, which means they're not desperate, which means your pitch has to be about the work.
3. Have cleaner non-solicit timers than active employees, because the clock started months ago.
4. Carry the same first-party Xbox lineage you'd pay a bounty for.

The sourcing move is to filter for people whose Microsoft tenure ended in the months before the September 22 notification, cross-reference with Xbox-adjacent repos and credits, and treat the November 21 cohort as the second wave. Refolk handles the awkward part of this - describing "ex-Microsoft gameplay engineers who left in the last six months and shipped on a first-party Xbox title" in plain English - instead of forcing you to stack five filters that none of them exactly fit.

Studios losing franchise ownership are the softest targets

Engineers at World's Edge, Rare, and whoever owned the next Halo title just lost their project identity even if their badge survived, which is a classic poach moment that doesn't require a layoff letter. Microsoft is folding those studios under Activision, Bethesda, and King, and Ninja Theory (the Hellblade studio) is reportedly facing closure.

The restructuring reads as a specific list for outbound:

• Halo Studios: included in the 268, and the next Halo title is moving under Activision's banner. Engine and multiplayer engineers are now shipping on someone else's franchise.
• World's Edge: now under Activision. Engineers who shipped on its titles are a rare profile on the open market.
• Rare: Sea of Thieves systems and live-ops engineers, now under Activision. UK-heavy but still a named target.
• Ninja Theory: Hellblade studio, closure reportedly on the table.

If you're a competing studio recruiter, you don't need the WARN roster to work this list. Half the sourcing is public: shipped-game credits, Discord presence, GitHub forks of engine plugins. The gap is going from "engineers who shipped Sea of Thieves systems work" to a ranked, deduped list of 30 names with contact handles.

The WARN notice is a sourcing calendar

The November 21 termination date clusters severance clocks, non-solicit expirations, and health-benefit cliffs into one week, so a studio that times outreach to the first week of December hits candidates at peak urgency. Washington's WARN Act requires 60 days of notice before a mass layoff, which is why a September 22 filing produces a November 21 exit.

Three dates to put on the recruiting calendar:

• September 22, 2026: Notification. Candidates are processing. Low reply rates, high note-taking value. Build the list now, don't send yet.
• November 21, 2026: Hard exit for all 277 Puget Sound positions. Severance starts, benefits begin countdown.
• First week of December 2026: Peak outreach window. Non-solicit language varies, but the holiday calendar means candidates are mentally reorganizing anyway.

This isn't a legal footnote. It's a sourcing calendar you can literally schedule. The earlier WARN filing (dated July 6, with a September 4 exit covering 605 Redmond positions as part of a plan to eliminate roughly 3,200 Xbox roles globally in fiscal 2027) already produced a wave that landed in alumni networks last month. The November 21 cohort will do the same, and the studios that time outreach to the dates above will out-recruit the studios that chase the headline.

The 268 global number is a press release. The 252 at One Microsoft Way is a phone list.

Hiring into the same market Microsoft is cutting

Redmond and the broader Seattle area still have active engineering demand that would absorb this exact candidate profile. The WARN cohort isn't picking between "Xbox or unemployment." They're picking between you and three other local offers.

If you're a recruiter at a competing studio, the move is to pre-stage the pitch now. Reply rates on cold outreach to active Microsoft engineers run in the single digits. Reply rates on warm, timed outreach to a candidate who just lost franchise ownership of the project they've shipped on for five years are a different conversation.

The pitch that works on a demoralized Xbox engineer

Quote Asha Sharma. In July, Xbox's CEO said: "Our business today is not healthy. We are operating at margins that are 3-10x lower than comparable platform and publishing businesses." She added, "We must reset Xbox." That, plus Satya Nadella publicly calling the streamlining "great to see," is the strongest internal signal candidates have gotten in a decade that this is not a short-term dip.

Translation for recruiting messaging:

• Don't pitch stability vs chaos abstractly. Quote Sharma. Candidates have read it.
• Don't pitch "come build something new." They just watched something new get folded into Activision.
• Do pitch creative ownership. The thing they're losing is the thing to offer.
• Do pitch a short runway to shipping. Microsoft's reorganization and the stated goal of reducing the Xbox workforce by roughly 20% by the end of the fiscal year are the opposite.
• Do name the credits. Candidates who shipped on Halo, Sea of Thieves, or Age of Empires respond to recruiters who read their work.

2,625

The layoff is the news, but the alumni graph is the business. A sourcing team that walks away from this week with only the 268-global number has done the easy half of the work. The team that walks away with a named list of Redmond engineers tagged by credit, shipped title, and exit date has a quarter of pipeline that competitors won't catch up on until February.

FAQ

How many of the 268 Xbox cuts are actually in Redmond?

The 268 is a global Xbox Game Studios number. The Washington WARN filing covers 277 positions, with 252 at One Microsoft Way in Redmond and 25 remote-but-Washington-based. The two numbers overlap but are not the same, because Cloud and AI cuts also hit Puget Sound and some Xbox cuts hit international studios. The hireable Redmond engineering slice is a subset of the 252, likely 60 to 100 people once you back out artists, designers, and producers.

When does the WARN clock actually run out?

Candidates were notified on September 22, 2026, and all 277 positions exit on November 21, 2026, under Washington's 60-day WARN Act requirement. The practical outreach window is the eight weeks between notification and exit for warm pipeline building, and the first week of December for peak-urgency outbound, when severance clocks and benefit cliffs land simultaneously.

Is the voluntary buyout pool actually bigger than the layoff?

Yes, by roughly 10x. About 30% of 8,750 eligible US Microsoft employees took this year's voluntary retirement offer, which is roughly 2,625 people. Not all of them are from Xbox, but the Xbox share is non-trivial, and these candidates carry no WARN clock, no severance delay, and no recent-trauma signal in their messaging. Treat the layoff as the trigger that unlocks outreach to the broader alumni graph.

What's the fastest way to turn the WARN notice into a named list?

Pull the Washington Employment Security Department WARN portal for the raw filing, cross-reference with "past Microsoft, Redmond" profile filters, and layer in GitHub activity on Unreal and first-party Xbox tooling repos. Then describe the resulting profile in plain English to Refolk ("ex-Xbox gameplay engineers in Redmond, shipped on a first-party title in the last three years, strong C++") and you get a ranked, deduped shortlist you can start working the first week of December.