Sony's Bungie Just Cut 292 in Bellevue. GitHub Indexes 9 of Them.
Sony's Bungie dumped 292 Bellevue engineers into the market on June 25, 2026. Here's why GitHub-first sourcing fails for AAA engine talent.
On June 25, 2026, Sony Interactive Entertainment's Bungie announced roughly 400 cuts, and the Washington State WARN filing listed 292 of them at the studio's 550 106th Ave NE Bellevue HQ, effective July 9. If you run engineering hiring at a game studio, a live-service startup, or anywhere with a real-time backend, you have about four weeks to move. And if your playbook starts with a GitHub search, you have already lost.
The 292 number is real, but the 400 is what matters
The WARN filing shows 292 Bellevue separations; Bloomberg's Jason Schreier reported the full cut at roughly 400 of about 800 remaining roles. The delta, about 108 people, is where the best hires hide.
WARN only covers Washington-based employees. Remote engineers, out-of-state SIE support staff, and contractors do not show up in a state filing, which means they are also absent from the LinkedIn "open to work" surges and the aggregator scrapes that recruiters will lean on next week. SIE Studio Business Group CEO Hermen Hulst told staff the cuts included "most of the Destiny team and some Marathon team members," so the diaspora spans the biggest live-service backend in gaming and a failed extraction-shooter reboot that had its own dedicated tools group.
This is the third round since the $3.6B Sony acquisition in 2022, following roughly 100 cuts in late 2023 and about 220 in mid-2024. Total post-acquisition displacement is now north of 600 people. The 2023 and 2024 cohorts are already re-employed. The 2026 cohort is the one still in market.
Why GitHub sourcing fails for AAA engine engineers
GitHub is the wrong index for this pool because AAA engine work happens inside proprietary C++ trees behind NDAs, so there is no public commit history to grep. Recruiters keyword-searching GitHub for Bungie alumni will surface hobbyists on Godot and ezEngine, not the people who shipped Destiny 2's matchmaking backend.
Consider what these engineers actually built:
- Bungie ships on the proprietary Tiger Engine, a fork of the Halo-era Blam! engine.
- Naughty Dog ships on ICE.
- Guerrilla Games ships on Decima.
- Rockstar ships on RAGE.
None of these have a public repository. None produce a commit graph a sourcer can boolean-search. The engineers who wrote them have zero surface area on the developer profile signals most sourcing stacks over-weight. In Refolk's index of professional profiles, only 9 US-based profiles match Bungie combined with engineer, programmer, or developer as a current or past title-and-employer pair. Against a known cohort of 292 people who just walked out the door, that is a public visibility rate of roughly 3%.
Broaden the search and it barely gets better. Refolk's index shows just 62 US profiles listing "Unreal Engine" as a declared skill under engineer, programmer, or developer titles, with top employers concentrated at Santa Monica Studio, Disbelief, Infinity Ward, and Avalanche Software. In a US game-dev workforce estimated in the tens of thousands, that is systemic under-declaration. AAA engine engineers do not list their tools publicly because the tools are the IP.
The exception that proves the rule shipped a week later. CCP Games open-sourced its Carbon engine on July 1, 2026, releasing two decades of proprietary tech onto GitHub, while keeping EVE Online's live game logic, art assets, server binaries, and database components strictly private. Even in the most public engine release of the year, the engineers who wrote the shipping code are still invisible on public repos.
The right signals to hunt with
For AAA engine talent, prioritize studio-alumni graphs, live-service credit lists, and conference-talk archives over GitHub. Public-title matching gets you 3% of the pool. The other 97% show up in credits databases, GDC and Digital Dragons speaker lists, Bungie's own postmortems, Destiny community wikis, and the LinkedIn "worked at" edge that never uses the word "engineer" in the headline.
Concrete signals that actually resolve to Bungie engineers:
- Shipped-title credits on MobyGames, IGN, and the Destiny credits pages for The Taken King, Forsaken, Beyond Light, The Final Shape.
- GDC and Digital Dragons talk history on backend, matchmaking, telemetry, or content-pipeline topics.
- Patent filings assigned to Bungie Inc. (a surprising number of senior tools engineers show up here).
- Alumni edges through ProbablyMonsters, 343 Industries, and Amazon Games, since Bungie's leadership tree has re-formed in Bellevue three times already.
- Community moderator and event roles in Destiny subreddits, r/DestinyTheGame Discord, and the Bungie Foundation.
This is the exact shape of query Refolk is built to run: describe the person in plain English ("senior backend engineer who shipped Destiny 2 matchmaking or telemetry, based in Bellevue, not currently at Bungie") and get a ranked shortlist that cross-references LinkedIn work history, credit databases, and open-web mentions instead of collapsing to a title-and-keyword match. Boolean strings do not work here because the boolean vocabulary is proprietary.
The 4 to 8 week window before the best 20% are gone
Bungie alumni from 2023 and 2024 were absorbed within roughly two months, and the 2026 cohort will follow the same curve. Assume you have four to eight weeks before the top quintile has signed.
Where the last two cohorts actually landed:
- ProbablyMonsters (Bellevue), founded by ex-Bungie CEO Harold Ryan, is the reliable #1 landing pad.
- Amazon Games (Seattle and Bellevue) placed 2024 alumni into senior live-ops on New World and Lost Ark.
- NetEase Worlds, Jackalope Games, and Aftermath Islands hired aggressively from the 2024 round.
- Riot Games picked up senior live-service ICs remote.
- Microsoft / Xbox in Redmond and Nintendo of America (also Redmond) absorbed tools and engine specialists.
The Bellevue cluster behaves like a moat, not a spread. Bungie has been one of downtown Bellevue's marquee tech employers and a visible anchor of the city's gaming cluster, and most of the 292 will not relocate. They will take the first credible offer within a 20-mile radius. If you are hiring in Bellevue, Redmond, or Seattle, this is your window. If you are hiring in Los Angeles, Austin, or remote, you are competing against a mortgage and a school district.
Epic Games already cut 82 locally in a prior round, and those engineers stayed in the metro. Expect the same pattern here.
The Bellevue cluster is a moat, not a spread. Most of the 292 will not relocate. They will take the first offer within 20 miles.
Live-service engineers are worth more than shooter engineers right now
Destiny 2 ran for 8+ years as one of the most complex live-service backends in gaming, which makes its engineers directly hireable outside games, not just inside them. If you pitch them a game role, you are competing with fintech and adtech offers they can take at a 40% premium.
The transferable specialties from a Destiny 2 backend engineer look like this:
| Bungie specialty | Direct crossover market | Why it transfers |
|---|---|---|
| Matchmaking / session services | Real-time SaaS, Uber/Lyft, DoorDash | Latency-bounded routing under load |
| Telemetry / player analytics | Datadog, Segment, adtech | High-cardinality event pipelines |
| Anti-cheat / integrity | Fraud (Stripe, Chime), bot detection | Adversarial ML and signal design |
| Content pipeline / build systems | Developer tools, CI companies | Multi-hour builds, artifact management |
| Live-ops economy design | Fintech, marketplaces | Real-money-adjacent balance systems |
A recruiter who can only sell "come make games" will lose the top backend engineers to Stripe, Roblox, and any Series C with a matchmaking-shaped problem. A recruiter who can articulate why a Destiny telemetry engineer maps 1:1 to a growth analytics platform will book meetings the same week.
Here is where the plain-English query matters again. Asking "find ex-Bungie engineers whose live-service backend work transfers to fintech fraud" is a semantic question, not a boolean one. Refolk translates that intent across LinkedIn work history, patent filings, and conference-talk topics, which is the exact gap the traditional Boolean stack leaves open when the underlying tech stack is proprietary.
The dataset, in one table
Everything above, in one place, so you can size your pipeline against the real numbers.
| Segment | Count | Note |
|---|---|---|
| Bungie Bellevue WARN, June 2026 | 292 | Washington ESD filing, separations July 9 |
| Total Bungie/SIE cuts (press) | ~400 | Schreier / Bloomberg |
| Delta invisible to WARN | ~108 | Remote and out-of-state, not in state filings |
| US profiles matching Bungie + engineer titles | 9 | Refolk index, ~3% surface visibility |
| US profiles listing Unreal Engine as engineer skill | 62 | Refolk index, systemic under-declaration |
| Prior post-acquisition cuts (2023 + 2024) | ~320 | Downtown Bellevue reporting |
| Sony's 2022 acquisition price | $3.6B | Closed 2022 |
The spine of this article, and of any sourcing plan you build off it, is the 9-vs-292 line. Public-title matching resolves 3% of a known cohort. Whatever tool you use next has to close the other 97%, and it has to close it in the four to eight weeks before ProbablyMonsters, Amazon Games, and Riot absorb the senior ICs. If your current stack answers "find ex-Bungie engineers in Bellevue" with a page that misses 97% of them, swap the tool before you swap the strategy.
FAQ
How many Bungie engineers were actually laid off in June 2026?
The Washington State WARN filing lists 292 employees at Bungie's 550 106th Avenue NE Bellevue location, with separations effective July 9, 2026. Bloomberg's Jason Schreier reported the full number closer to 400 of roughly 800 remaining roles, meaning about 108 additional remote or out-of-state workers were cut but do not appear in the state filing. The 292 figure is the floor, not the ceiling.
Why do GitHub searches miss most Bungie engineers?
Bungie ships on the proprietary Tiger Engine, a fork of the Halo-era Blam! engine, and nearly all AAA studios operate the same way (Naughty Dog's ICE, Guerrilla's Decima, Rockstar's RAGE). There is no public commit history for their real work, and engineers do not list proprietary tools on public profiles because the tools are the IP. Refolk's index confirms this with only 9 US profiles matching Bungie combined with engineer titles, roughly 3% of the 292-person cohort.
Where are Bungie alumni most likely to land?
Historically, ProbablyMonsters in Bellevue (founded by ex-Bungie CEO Harold Ryan) is the top destination, followed by Amazon Games in Seattle, Riot Games remote, and Microsoft/Xbox and Nintendo of America in Redmond. NetEase Worlds, Jackalope Games, and Aftermath Islands hired aggressively from the 2024 cohort. Most laid-off employees will not relocate out of the Bellevue metro, so competition inside a 20-mile radius will be sharpest.
Are Destiny 2 backend engineers only useful for game companies?
No, and pitching them only game roles is how recruiters lose them. Destiny 2's matchmaking, telemetry, anti-cheat, and content-pipeline systems map directly onto fintech fraud, real-time SaaS, adtech event pipelines, and developer tools. Companies like Stripe, Datadog, and Roblox are natural cross-industry buyers, and they typically outbid game studios on cash comp for senior backend ICs.