Bungie's $766M Write-Down: Source the Tiger Engine Team Before June 16
Bungie ends Destiny 2 development on June 9, 2026. Here's how to source the Tiger Engine netcode and anti-cheat team in the 21-day window.
Bungie confirmed on May 21, 2026 that the June 9 update will be Destiny 2's last, and Bloomberg's Jason Schreier reported the same day that Sony is preparing a "significant number" of layoffs with no Destiny 3 in production. If you ship live-service netcode, anti-cheat, or any engine work that has to survive contact with millions of concurrent players, this is the cleanest sourcing unlock of the year. You have about 21 days.
The 21-day clock starts now
The dates are tight and the order matters. May 21: Bloomberg breaks the layoff story. May 22: TechSpot and Game Informer confirm the June 9 update is the last. June 9: active development on Destiny 2 ends. Mid-to-late June: the RIF lands. That gives recruiters from roughly May 22 through June 16 to make first contact before Riot, Epic, and Discord have these engineers in final-round loops.
Bungie was a 1,000-plus employee studio before its recent cuts. This will be the third round since Sony acquired the company for $3.6 billion in 2022. Sony took a $565 million impairment on Bungie in Q4 FY2025 on top of a $201 million Q2 write-down, and CFO Lin Tao confirmed Bungie's earnings missed expectations. When the parent company writes off three quarters of a billion dollars in a single fiscal year, the second shoe is not a question of if.
The Bungie layoffs 2026 cycle is also not happening in a vacuum. Industry observers are openly comparing the trajectory to Firewalk Studios (Concord), Bluepoint, Neon Koi, and Japan Studio. Retained Bungie staff have watched this Sony playbook four times now. They will answer your message.
Stop chasing "Destiny gameplay engineers"
The obvious mistake is to search LinkedIn for "Destiny 2" in the title and call the senior gameplay programmers. That cohort is the most exposed in the RIF, but it is also the least transferable. Seasonal content pipelines and raid sandbox systems do not map cleanly to anyone else's stack.
The rare, defensible skills sit one layer down: the Tiger Engine shared-services team. Tiger is Bungie's proprietary engine, built after the studio left Microsoft as an overhauled fork of the blam! engine that powered Halo. Destiny, Destiny 2, and Marathon (2025) all run on it. Tiger was architected around multithreading, cross-platform support, layered decoupling of engine from game logic, and a long-horizon mandate to support advanced tech. The Destiny codebase is roughly 5 million lines, with engine-enforced data rules that make these engineers specialists in large-scale system constraints.
That is exactly the skill stack AI world-sim startups, robotics simulation teams, and the next generation of competitive shooters need. And it is the skill stack that does not show up cleanly in a LinkedIn boolean.
Why LinkedIn is the wrong primary surface
Many Bungie engineers deliberately do not list "Destiny" on their LinkedIn profiles. The reasons are practical: harassment from players, security posture around anti-cheat work, and a culture of crediting "Bungie" without naming the project. If you run a LinkedIn-only search for Tiger engine Bungie, you will miss the people you most want to reach.
The higher-signal surfaces are public but scattered:
- GDC speaker archives. Chris Butcher's 2015 talk "Lessons from the Core Engine Architecture of Destiny" (gdcvault.com/play/1022106) is the canonical public artifact. Mine its citations and the follow-up talks.
- The Destiny Developer Insight blog bylines on bungie.net.
- USENIX networking talks and GDC networking-track sessions.
- Credits screens for past Destiny expansions and Marathon.
- GitHub activity from engineers who maintain personal accounts under different handles than their LinkedIn.
This is the exact friction we built Refolk to remove. You describe the person in plain English ("senior engine engineer at Bungie who has spoken at GDC about netcode or anti-cheat, currently in the Seattle metro") and get a ranked shortlist that pulls from GitHub, LinkedIn, and the open web at once, including the GDC and conference surfaces that don't index well in standard sourcing tools.
The people you want are not the ones whose LinkedIn headline says Destiny. They are the ones whose headline says nothing at all.
The four sub-pools, and who buys each one
Treat the Bungie cohort as four distinct talent markets, not one. Each maps to different buyers and different outreach angles.
1. Netcode and matchmaking
These are the engineers who kept Destiny 2 raids and Crucible playable at scale, and who shipped Marathon's matchmaking. They understand deterministic simulation, rollback, lag compensation, and the brutal economics of running authoritative servers for millions of concurrent users.
Buyers: Riot Games (Project L, Valorant infrastructure), Epic (Fortnite live-ops, UEFN), Roblox (engine and matchmaking at scale), Discord (game SDK, low-latency networking), and Valve, which is right next door in Bellevue/Kirkland and currently staffing Deadlock.
2. Anti-cheat
Marathon shipped into a brutal anti-cheat environment and lost 59% of its launch peak on Steam by mid-April 2026, with a 24-hour peak around 31,000 players a month after release. The engineers who fought that fight learned things you cannot learn from a clean greenfield project. That is a feature, not a bug.
Buyers: Riot's Vanguard team, BattlEye, Easy Anti-Cheat (Epic), and any studio shipping competitive PvP at scale. Marathon's struggles are a recruiting accelerant here, not a blocker. The pitch writes itself: "You learned what doesn't work. We want that."
3. Engine, tools, and build pipelines
The Tiger Engine shared-services team. As recently as June 2023, Bungie was hiring a Senior Tools Engineer for "Tiger Engine Sharing," a core team building tools across Destiny, Marathon, and other projects. Those engineers are now exposed, and their skill set (custom engine internals, build pipelines for a 5-million-line codebase, layered engine/game decoupling) is the exact stack that AI world-sim companies need.
Buyers: World Labs, Decart, Odyssey, Fable Studio, Nvidia Omniverse, the Cosmos robotics-sim teams, and any company trying to build a real-time deterministic simulation engine from scratch. Also Microsoft/343 Industries, which still ships on a blam!-derived engine and sits 20 minutes away in Redmond.
4. Live-ops and seasonal content systems
This is the most Destiny-specific pool, and the hardest to place. But there is a real buyer set: any studio trying to convert a single-player IP into a live service (Ubisoft, EA, Take-Two), plus the live-ops teams at Epic, Riot, and Roblox who staff seasonal events.
Bellevue is the unlock
Bungie is in Bellevue, Washington. So is Amazon Games. Valve is in Bellevue and Kirkland. Microsoft and ZeniMax are 20 minutes east in Redmond. ProbablyMonsters, founded by former Bungie CEO Harold Ryan, is also in the area, as are several other Sony studios. In-person poaching is feasible in a way it is not for, say, a remote-first Discord role.
If you are an engineering leader at any of those companies, the move this week is to get coffees on the calendar for the second week of June. Not interviews. Coffees. The senior engineers will not commit to a process while they are still trying to read the room internally, but they will sit down with someone they respect who works ten minutes away.
For out-of-market buyers, the calculus is different. You need to compete on either money, mission, or interestingness of the problem. AI-sim startups have an unusual advantage here: the work is genuinely novel, and the Tiger Engine engineers who built deterministic simulation for Destiny are, on paper, the best-prepared candidates on earth for what World Labs and Decart are trying to do. Lead with the technical problem, not the equity package.
The named-target starter kit
A sourcing-team starting point, in priority order:
- Pull the speaker list from every GDC session tagged "Destiny," "Bungie," "netcode," or "anti-cheat" from 2014 to 2025.
- Cross-reference with the Destiny Developer Insight blog bylines from bungie.net.
- Mine the credits screens of Destiny: The Taken King, Forsaken, The Final Shape, and Marathon (2025) for engine, tools, network, and infrastructure roles.
- Search GitHub for engineers in the Seattle metro with public activity on game engine, networking, or simulation projects who also follow Bungie engineers.
- Filter to current Bungie staff using the live-service engineer hiring history on the studio's careers page and LinkedIn employee lists.
Steps 1 through 4 are the part that takes a team of sourcers two weeks. With Refolk, you describe the cohort in plain English and the system pulls the GDC, GitHub, and LinkedIn signals together in one pass, which is the difference between making first contact this Friday and making it the Friday after the layoffs land. That gap is the entire game.
The bigger pattern
Bungie is the third Sony studio cut in 18 months. Firewalk is gone. Bluepoint and Neon Koi have been gutted. The pattern is now legible enough that even retained Bungie staff are reading it in real time. If you are sourcing game engine engineers in 2026, the assumption should be that any Sony first-party studio is a sourcing target on a 12-month horizon, and that the Tiger Engine cohort specifically is the highest-leverage unlock available between now and the next Riot or Epic round of public hiring.
The recruiters who win this cycle will not be the ones who run a LinkedIn boolean on June 17. They will be the ones who already had the named list on May 22.
FAQ
When exactly will the Bungie layoffs hit?
Bloomberg's May 21, 2026 report indicates "significant" layoffs are planned after the June 9 final Destiny 2 update. The most likely window is mid-to-late June 2026, though Sony has historically announced cuts in clusters with limited public warning. Plan outreach as if the RIF lands the week of June 15.
Why focus on the Tiger Engine team rather than gameplay engineers?
Gameplay engineers who specialized in Destiny's seasonal content and raid sandbox have skills that do not transfer cleanly outside the Destiny IP. Tiger Engine shared-services engineers (netcode, matchmaking, anti-cheat, build tools, engine internals) have skills that map directly to Riot, Epic, Roblox, Discord, and the AI world-sim startups. The defensible skills sit in the engine layer.
How do I find Bungie engineers who don't list Destiny on LinkedIn?
Use GDC speaker archives, the bungie.net Developer Insight blog bylines, USENIX networking talks, and credits screens from past expansions and Marathon. Cross-reference with GitHub activity in the Seattle metro. Refolk pulls these surfaces together in a single plain-English query so you do not have to maintain six separate sourcing spreadsheets.
Should I bother reaching out to engineers who shipped Marathon despite its struggles?
Yes, aggressively. The engineers who fought Marathon's 59% Steam decline and anti-cheat battles learned lessons no greenfield team has access to. For anyone shipping competitive PvP or extraction-shooter mechanics, that experience is the recruiting pitch. Marathon's commercial outcome and its engineering value to a future employer are two different questions.