Bungie's 292 WARN Hides 400. Tiger Engine's Netcode Is the Real Prize.
Bungie's July 9, 2026 Bellevue WARN released the deepest live-service netcode bench in a decade. Here's the sourcing playbook, by title and surface.
Bungie's Washington WARN filing separated at least 292 Bellevue employees on July 9, 2026, and reporters on the internal call put the real number closer to 400. If you source live-service infrastructure engineers, this is the single largest release of netcode, matchmaking, and engine-internals talent since the last console generation, and it is concentrated inside a 20-minute drive of Redmond.
Most recruiters will read "292 Bungie layoffs" and start scraping LinkedIn for "Destiny" in job titles. That is how you end up with a shortlist of gameplay designers when the actual prize is a small, deeply specialized group of engineers who kept a 5M-line codebase shipping seasonal content for nine years. Here is how to separate them.
The WARN is a floor, not a ceiling
The Washington filing lists at least 292 impacted employees at 550 106th Ave NE. That number captures WA-based permanent staff only. It does not capture remote employees in other states, transferred SIE support staff, or contractors, several of whom may not even be able to push a final Destiny 2 hotfix now that the org has collapsed. Paul Tassi and Bloomberg's Jason Schreier both reported the internal figure was roughly 400.
If you anchor on 292 and only pull Bellevue LinkedIn profiles updated in July, you will miss the third of the market that lives in Kirkland, Woodinville, or worked hybrid from Portland and Austin. The Bungie layoffs July 2026 pool is bigger than the state filing, and the strongest candidates will have offers within two to four weeks of separation. If you wait for "Open to Work" flags to appear in August, you are already competing with Riot and Epic on price.
Not every "Destiny engineer" is a prize
This is the mistake that will cost you. Bungie shipped a live game for nine years, which means the studio built two very different engineering populations under one roof.
The first population is gameplay engineers tied to Destiny's seasonal sandbox, raid encounter scripting, sandbox weapons balance, and content pipelines specific to the IP. Their skills are excellent but IP-shaped. They transfer well to other AAA live-service shooters and less cleanly to non-gaming buyers.
The second population is the Tiger Engine shared-services layer: netcode, matchmaking, anti-cheat, deterministic simulation, build systems for a 5M-line cross-platform codebase, and the tools infrastructure that let a few hundred engineers ship weekly. Tiger Engine is a blam!-derived, multithreaded engine designed from day one for multi-year live service. The people who own that layer are the ones who map cleanly to AI world-sim (World Labs, Decart, Odyssey, Fable), Nvidia Omniverse, defense simulation, Discord's real-time infra, and any live-ops team at Epic, Riot, or Roblox.
If you are sourcing gaming engineers for a non-gaming buyer, the second population is the entire game. Prioritize accordingly.
Titles the WARN actually names
The Washington filing's affected-role list is unusually specific and gives you a starting shape for the org chart:
- Chief Vision Officer (co-founder Jason Jones)
- Game Director (25-year veteran Tyson Green fits the slot)
- Managing Director of Technology
- Director of Development
- Engineering Director
Studio head Justin Truman, less than a year into replacing Pete Parsons, stepped down separately. Former VP of Operations Poria Torkan is reportedly running what remains, though Sony has not officially announced it.
For a sourcing shortlist, the titles that matter under those directors are the ones the WARN does not spell out but the org must have carried: Principal Engine Engineer, Senior Netcode Engineer, Matchmaking Services Engineer, Anti-Cheat Engineer, Build & Release Engineer, Tools Engineer (Tiger Engine), Backend Services Engineer (player data, telemetry), and Cinematics Tech Director. The entire cinematics org was eliminated, per outgoing cinematics director John Ebenger's Bluesky post, so the cinematics tools engineers are in the pool too.
Where these people are actually visible
LinkedIn will surface maybe 40% of this pool with any useful signal. The senior engine and netcode engineers who built Tiger Engine over a decade are more legible on other surfaces, and this is where most sourcers stop looking.
The canonical citation graph
Chris Butcher's 2015 GDC talk "Lessons from the Core Engine Architecture of Destiny" is the citation root for the entire netcode and engine cohort. Mine it, mine the follow-up GDC networking-track sessions from 2016 to 2022, and mine the USENIX networking track archives for any Bungie-affiliated author. The names that recur across those sessions are the ones you want.
Credits screens and Developer Insight bylines
Destiny 2 and Marathon credits screens are public. So are the bungie.net "Developer Insight" posts, where individual engineers wrote up systems work under their real names. Cross-reference the bylines against LinkedIn and against Seattle-metro GitHub activity, often under alternate handles that do not mention Bungie.
This is the exact seam Refolk was built for. You describe the person in plain English, including the non-LinkedIn signals ("bungie.net byline", "GDC networking track speaker", "Tiger Engine tools"), and you get back a ranked list that includes the engineers whose LinkedIn profiles are deliberately generic. When the pool is 400 and the window is two to four weeks, filtering by surface rather than by keyword is the only way to move fast enough.
The comp trap: many of these are cash-outs, not distress exits
Here is the piece almost every outbound recruiter is going to get wrong. Tassi reports that many of the oldest and most-key Bungie employees have Sony sale earn-outs from the 2022 $3.6B acquisition vesting this month. The layoff timing is not coincidence. Several of the biggest engineering names are walking out with meaningful cash, not with a mortgage clock ticking.
That changes the entire approach. A generic "sorry to hear about Bungie, we'd love to chat" message from a Series B recruiter lands flat. These people can afford to wait, to consult, to advise, or to take founder roles. Your first message needs to acknowledge that and lead with the technical substance, not the urgency.
The engineers who built Tiger Engine's netcode do not need a job in August. They need a reason to skip a sabbatical.
For your Destiny engineers hiring pitch, this means offer construction matters as much as sourcing. Founding engineer titles, meaningful equity, technical scope that maps to what they already built, and named technical peers on the team. If you are a live-service buyer competing against Riot and Epic on cash, you will lose the top decile. If you are a well-funded AI world-sim startup offering a founding-engineer stake and a genuinely hard simulation problem, you will win people cash cannot buy.
The buyer map: who actually needs this stack
Sort your outreach by which of your clients or portfolio companies can credibly absorb this talent.
Same-engine, same-city
343 Industries in Redmond still ships on a blam!-derived engine. Twenty minutes from 550 106th Ave NE. Same engine DNA, no relocation, and Microsoft has the cash. Assume 343's recruiting team started outbound the day the WARN posted.
Live-service ops at scale
Riot, Epic, Roblox, and Discord all have real needs for matchmaking, netcode, and anti-cheat engineers who have shipped at Destiny's concurrency scale. Ubisoft, EA, and Take-Two live-ops teams converting single-player IP to live service are the second tier, and they historically move slower.
AI world-sim and real-time simulation
Nvidia Omniverse, World Labs, Decart, Odyssey, and Fable Studio all need deterministic real-time simulation and networking. This is where the Tiger Engine shared-services layer is genuinely underpriced. These buyers do not have gaming recruiters and often do not know the credits-screen names to hunt.
Defense and industrial sim
Anduril, Shield AI, and the more serious defense-sim primes will pay for the netcode and deterministic simulation skill stack. Clearance is a filter, but the technical fit is close to perfect.
Adjacent WA context: Bellevue keeps compressing
Epic Games cut 82 at its Bellevue Lincoln Square office earlier in 2026. Bungie itself has cut roughly 600 jobs across three rounds since Sony's 2022 acquisition (100 in October 2023, 220 in July 2024, 292+ now), taking the studio from a peak of about 1,400 to roughly 500. Sony took a $750 to $765M impairment charge on Bungie assets tied to Marathon's reception.
The practical effect for sourcers is that the Bellevue WARN notice Bungie filed is landing in a candidate pool that is already thickening from Epic's cuts. Local density is real. If you can offer hybrid out of Seattle or Redmond, you have a meaningful edge over any Bay Area buyer trying to relocate this cohort.
A concrete week-one plan
If you are running this search, here is the sequence that actually works in the two to four week window.
- Pull the Destiny 2 and Marathon credits screens. Build a named list of everyone in Engine, Networking, Services, Tools, Build, and Anti-Cheat departments.
- Cross-reference against GDC Vault networking-track speakers and USENIX networking-track authors from 2015 to 2024.
- Cross-reference against bungie.net Developer Insight bylines.
- Now hit LinkedIn, with the named list in hand, not with a keyword search. Refolk will flag the profiles whose employer field is blank or generic but whose history matches.
- Segment by the two populations above (IP-shaped gameplay vs Tiger Engine shared services). Route to buyers accordingly.
- Lead outbound with technical substance, not sympathy. Acknowledge the earn-out reality if you are talking to a 10-plus-year veteran.
The 292 number will drive the news cycle for another week. The engineers who matter will be off the market before the second wave of thinkpieces publishes.
FAQ
How many Bungie engineers were actually laid off on July 9, 2026?
The Washington WARN notice lists at least 292 Bellevue-based permanent employees with separations effective July 9, 2026. Reporting from Paul Tassi and Bloomberg's Jason Schreier put the real internal figure at roughly 400 once you include remote Washington employees, out-of-state remotes, and contractors. A vast majority of the affected roles are engineers, producers, and designers.
Which titles should I prioritize for live-service infrastructure roles?
Prioritize the Tiger Engine shared-services layer: senior and principal engine engineers, netcode engineers, matchmaking services engineers, anti-cheat engineers, backend services engineers, and build and release engineers. The WARN explicitly names Managing Director of Technology, Director of Development, and Engineering Director as affected. Gameplay engineers tied to Destiny's seasonal sandbox are talented but their skills are more IP-shaped and transfer less cleanly to non-gaming buyers.
Why is LinkedIn insufficient for sourcing this pool?
The senior Tiger Engine and netcode engineers built their public reputations on GDC Vault talks, USENIX networking-track papers, bungie.net Developer Insight bylines, and Destiny and Marathon credits screens. Many keep deliberately generic LinkedIn profiles. Chris Butcher's 2015 GDC talk "Lessons from the Core Engine Architecture of Destiny" is the citation root you should mine first, then cross-reference against Seattle-metro GitHub activity under alternate handles.
Who is the toughest competitor for this talent?
343 Industries in Redmond, twenty minutes from Bellevue, still ships on a blam!-derived engine and has Microsoft budget. Assume their recruiting started the day the WARN posted. Riot, Epic, and Discord will move next for live-service and real-time infra roles. The underpriced buyers are AI world-sim companies (World Labs, Decart, Odyssey, Fable) and Nvidia Omniverse, because they lack gaming-native recruiters and do not know which credits-screen names to hunt.