Bungie's June 9 Sunset: LinkedIn Returns 31 of the 400 Engineers in Play
Bungie's Destiny 2 sunsets June 9, 2026, triggering a third layoff wave in Bellevue. Here's how to source the engineers LinkedIn boolean misses.
On May 21, 2026, Bungie confirmed that Destiny 2 ships its final live-service update, Monument of Triumph, on June 9. Bloomberg's Jason Schreier reported the same day that "a significant number" of layoffs will follow at the roughly 850-person Bellevue studio, with no Destiny 3 greenlit and only the struggling Marathon left to fund. If you're hiring live-service engineers in 2026, this is the largest concentrated cohort of senior gameplay, netcode, and live-ops talent that will hit the market all year. And if you search for them on LinkedIn the way most recruiters do, you will find about 31 of the 400 people actually in play.
What June 9 actually triggers
The June 9 date is not symbolic. It is the contractual end of new content drops on Destiny 2, which means the live-ops org, the sandbox team, the seasonal content pipeline, and most of the gameplay simulation engineers no longer have a roadmap to staff against. Industry reporting before Marathon's launch put the internal split at roughly 300 developers on Marathon and 550 on Destiny 2. Paul Tassi reported in late spring that the split has flipped, with Marathon now edging out Destiny 2. That puts the at-risk Destiny cohort at somewhere between 300 and 400 engineers, designers, and live-ops staff.
This is Bungie's third major wave since Sony's $3.6 billion acquisition. About 100 jobs went in October 2023. Another 220 went in July 2024, with 155 more "transitioned" directly into Sony Interactive Entertainment. The Sony-side transition is the part most recruiters miss entirely. We will come back to it.
The math behind Sony's accounting tells you why no rescue is coming. A $565 million impairment in Q4 FY2025 stacked on a $201 million Q2 charge tied to Destiny 2's decline. Marathon's 24-hour peak hovered around 31,000 players a month after release, down from 88,337 on launch day, a 64% collapse. Concurrent counts had fallen 59% below launch peak by mid-April. Sony's next quarterly review is the actual question, not whether layoffs happen but how deep the second cut goes by Q4.
Why LinkedIn boolean returns 31 people
Bungie engineers do not describe themselves the way you would search for them. The senior IC titles inside the studio are "Sandbox Engineer," "Weapons Designer," "Investment Designer," "Sandbox Discipline Lead," "Tools Programmer," "Server Engineer," "Gameplay Simulation Engineer." The word "Destiny" almost never appears in their LinkedIn headline. The word "live-service" appears even less. The studio runs lean public profiles by cultural default, and a meaningful slice of engineers hide their current employer entirely.
So when a recruiter types the obvious string, something like "Destiny 2" AND engineer AND Bellevue, LinkedIn returns roughly 31 profiles. The actual layoff-affected cohort is 10x that. This is not a hypothesis. It is a vocabulary problem documented in every serious boolean guide: a candidate who describes their experience in different terms than your query will not surface, no matter how clean your operators. And LinkedIn Recruiter silently truncates boolean strings at around 1,000 characters, so the obvious fix (long synonym chains like gameplay OR sandbox OR netcode OR live-ops OR weapons OR investment OR…) gets cut off without warning.
There is a second problem stacked on top. The 155 employees Bungie "transitioned" into Sony Interactive Entertainment in 2024 now show Sony Interactive Entertainment as their current employer on LinkedIn. They still live in Bellevue. They still built Destiny. Any sourcing tool that filters company:Bungie excludes them entirely. Any tool that filters company:"Sony Interactive Entertainment" drowns them in 8,000+ unrelated PlayStation Studios profiles from Tokyo, London, and San Mateo.
The Bungie sourcing problem is not a database problem. It is a vocabulary problem and a label problem stacked on top of each other.
The titles you should actually be searching
If you are going to keep working in boolean for the moment, stop using "Destiny" and start using the disciplines:
- Sandbox engineer, sandbox discipline lead, weapons designer, investment designer
- Gameplay simulation engineer, ability systems engineer, encounter scripting
- Netcode engineer, dedicated server engineer, matchmaking engineer
- Live-ops engineer, telemetry engineer, build and release engineer
- Tools programmer, Perforce/Helix admin, Bazel maintainer
Cross-reference those with Bellevue, Redmond, Kirkland, and remote-PNW location filters. You will roughly triple the result count. You still will not get to 300.
The GitHub angle most sourcers skip
Bungie's Tiger engine is proprietary, which is why most recruiters write off GitHub for this cohort. That is the wrong read. The live-ops, telemetry, tools, and build engineers (a disproportionate share of who is actually being cut) commit to open-source dependencies: Bazel, Perforce client tooling, Helix integrations, OpenTelemetry exporters, Grafana stacks, internal CLIs they wrote at previous studios and still maintain.
A Bungie tools programmer with a locked-down LinkedIn often has a GitHub profile with three years of meaningful commits to a build-system dependency. That is the surface area you can actually search. This is the friction we built Refolk to remove: you describe the person in plain English ("senior live-ops or tools engineer at Bungie or Sony Interactive Entertainment, based in the Seattle area, with public commits to build infra or telemetry") and Refolk pulls the cohort across GitHub, LinkedIn, and the open web in one shortlist. No boolean, no 1,000-character truncation, no company:Bungie blind spot.
The Bellevue market is thinner than it looks
If you are in Bellevue or Redmond, you already know the local market for live-service expertise is shallow. Firewalk Studios, also Bellevue, was shut down by Sony in 2024 after Concord's launch failure. Many ex-Firewalk engineers did not land at another live-service studio. They went to Amazon Games' Seattle office, to AWS, to Microsoft's Azure Gaming org, to Roblox-remote. A few landed at ProbablyMonsters, the Bellevue studio founded by ex-Bungie CEO Harold Ryan, which has absorbed Bungie alumni in every prior wave.
The point is that "competitive offer" in this market is not what it was in 2022. Industry trackers count roughly 45,000 game-development jobs cut since 2022, with 9,200 in 2025 alone. The local supply of senior live-service engineers exceeds the local demand from gamedev employers by a wide margin. That means two things for your sourcing plan:
- You can hire above your normal band on raw experience, because base comp has compressed.
- You will lose candidates to non-gamedev buyers (AWS, Azure, Roblox infra) far faster than you will lose them to other studios.
If you are an engineering manager at a cloud, infra, or B2B SaaS company hiring distributed systems engineers, this wave is yours to take. Live-service engineers spend their careers on the exact problems your team has: distributed state, hot-path latency, deployment safety, observability at million-concurrent scale, anti-cheat-grade abuse detection. The pitch writes itself once you have the list.
A 60-day sourcing plan
The window from June 9 through roughly August 15 is when the cohort is most reachable, most responsive to outbound, and least saturated. Here is the cadence that has worked in prior studio shutdowns:
Week 1 to 2 (now through early June)
Build the list before the announcement. Cast wider than company:Bungie. Include Sony Interactive Entertainment + Bellevue. Include the discipline titles above. Include a GitHub pass for tools, build, and telemetry engineers. Tag anyone with 5+ years at Bungie separately, because they are the most likely to be in the cut and the most valuable hire.
Week 3 to 6 (mid-June through mid-July)
This is the active outbound window. Lead with respect for the work, specifically. "I have followed Bungie's sandbox iteration on Destiny 2 since Forsaken" beats "saw your impressive background" every time with this cohort. Reference the discipline (sandbox, weapons, netcode) rather than the IP. Do not lead with comp.
Week 7 to 9 (late July through mid-August)
Re-engage the engineers who passed in weeks 3 to 6. By this point, the severance runway is shorter, the local market is saturated with the same outreach, and engineers who said "I'm taking the summer off" are starting to take meetings. This is also when the Marathon-team engineers begin to ping recruiters quietly, because the next quarterly review is visible.
If you do not have time to run all three waves manually, the second mention is worth making here: Refolk's plain-English queries are designed exactly for this kind of multi-pass sourcing where the cohort is small, mislabeled, and split across two employer fields. You ask once, you get the deduped list, you run your three outreach passes against it.
The 12-month bet, not the 30-day one
The contrarian read on Bungie is that the June 9 wave is the smaller of the two cuts coming. Marathon's player numbers are collapsing on the same trajectory as Concord did. Sony has already written off $766 million against the studio in a single fiscal year. Justin Truman, who took over as studio head in August 2025 after Pete Parsons stepped down, inherits a portfolio with one shipped game in sunset and one shipped game in commercial freefall.
A pipeline of Bungie engineers you build in June pays out across June, the September quarterly review, and the next Sony fiscal year-end. The recruiters who only run boolean in the week after the layoff announcement will compete with every other studio for the same 31 visible profiles. The ones who built the off-LinkedIn list in May, who included the 155 Sony-transitioned engineers, who pulled the GitHub-visible tools engineers, will be having their second coffee with the senior sandbox lead while everyone else is still tuning their search string.
FAQ
How many engineers are actually being laid off at Bungie?
Bloomberg's Jason Schreier reported "a significant number" without a hard count. Pre-launch reporting put 550 developers on Destiny 2 against 300 on Marathon. Paul Tassi reports the split has since flipped toward Marathon, which puts the at-risk Destiny cohort in the 300 to 400 range. Expect the official number to land lower than the actual labor-market impact, because contractors and the Sony-transitioned 155 will not be counted in Bungie's announcement.
Why does a LinkedIn boolean only return about 31 profiles?
Two reasons. First, Bungie engineers use discipline titles (sandbox, weapons, investment, netcode) rather than IP names in their headlines, so "Destiny 2" matches almost no one. Second, the 155 employees transitioned into Sony Interactive Entertainment in 2024 no longer show Bungie as employer, so company:Bungie excludes them. LinkedIn Recruiter also silently truncates boolean strings around 1,000 characters, breaking the long-synonym workaround.
Should I be sourcing the Marathon team too?
Yes, but not as a Q3 target. Marathon's 24-hour peak fell to roughly 31,000 a month after release, down from 88,337 at launch. Sony's quarterly review cadence makes a second wave plausible by fall. Build the Marathon list now, tag it separately, and start light outreach in September. The Destiny 2 cohort is the active 60-day window; Marathon is the 12-month bet.
Where did Bungie alumni land in previous waves?
A meaningful share went non-gamedev: AWS, Microsoft Azure, Roblox-remote, and Amazon Games' Seattle office. The local gamedev landing pad is ProbablyMonsters, founded by ex-Bungie CEO Harold Ryan. Firewalk Studios, the parallel Sony-owned Bellevue shutdown in 2024, sent most of its senior engineers to cloud infra rather than to another live-service studio. Expect the same distribution this time, which is good news for cloud and B2B SaaS hiring managers and harder news for competing studios.