Bungie's June 9 Sunset: The Bellevue Netcode Team Belongs in Fintech
Bungie's June 9, 2026 Destiny 2 sunset frees a senior Bellevue netcode org with no internal landing spot. Here is who to source and how to pitch them.
On May 21, 2026, Jason Schreier reported in Bloomberg that Bungie is planning a significant round of layoffs tied to the end of Destiny 2 development, with the final live-service update ("Monument of Triumph") shipping June 9. There is no Destiny 3 to absorb the team, Sony already took a $765M Bungie-related impairment, and Marathon is averaging roughly 10,000 concurrent Steam players. Translation for anyone hiring in Bellevue: a senior, agentic, latency-obsessed engineering org is about to be on the market with no internal landing pad, and most of the people chasing them will be the wrong recruiters.
The setup nobody at Sony can fix
Sony bought Bungie in 2022 for $3.6 billion. On May 8, 2026, in its full-year results, it disclosed an impairment loss of roughly 120.1 billion yen (about $765 million) tied to the value of that acquisition, with the bulk of the charge (around 88.6 billion yen) landing in the January to March quarter. The Destiny 2 sunset on June 9 is the operational consequence of that writedown, not a separate event.
The Schreier piece is explicit about the part that matters for sourcing: the Destiny 2 development team has no project to move to. Sony has not greenlit a successor. Developers at Bungie have pitched a number of games to leadership, including some Destiny games, but nothing has been green-lit for production. Marathon, which launched March 5, 2026 at a $40 price point, is not absorbing anyone at 10K concurrents.
This will be the third layoff round since the Sony acquisition, on top of hundreds of layoffs at Bungie since 2023 and several canceled projects (including a Destiny spinoff called Payback). The exact number affected of the current 850 employees is not publicly known. The studio's expanded Bellevue HQ, designed by NBBJ to grow from 84,000 sf to more than 208,000 sf "to support multiple project teams across multiple game franchises," now has very few franchises to support.
Why "netcode engineer" is the wrong frame
If you read "Bungie layoffs 2026" and your first move is to ping ProbablyMonsters or Amazon Games Seattle, you are competing in the wrong market. Those studios will get the gameplay programmers and the tools engineers. That is fine. The much sharper move is on the backend half of the org, and the people screening those résumés for fintech and real-time infra are almost certainly going to miss them.
A Destiny 2 backend engineer has spent close to a decade shipping consistent state across a global player base under continuous adversarial pressure. Cheaters. DDoS. Exploit economies. Account takeovers. Item duplication. That is the same problem shape as fraud detection at a payments processor, order-book consistency at a trading venue, or anti-abuse at a wallet. The vocabulary is different. The systems are not.
The Built In Bungie listings still up before the news broke include a Senior Full-Stack Engineer role to "design and develop web services and frontends, ensuring high performance and player experience," a security lead, and gameplay systems roles, all Bellevue-based. The web services half of that posting describes someone Stripe would hire tomorrow if they read the JD without the Bungie logo on it.
The four sub-profiles to actually source
Not every Destiny 2 engineer is fintech-bound. Split the org into four buckets and recruit each differently.
Distributed backend / netcode. Globally consistent player state, regional failover, matchmaking. Maps to: trading infra, payments orchestration, real-time risk. Best landing spots are Stripe, Robinhood, Cloudflare's Bellevue office, Databricks, Datadog.
Anti-cheat and trust-and-safety. Bungie has run a sophisticated stack (BattlEye integration plus internal telemetry) for years. Maps to: fraud, AML, account takeover. This is the highest-leverage hire nobody is naming, and it is a structurally less cyclical career than gameplay engineering.
Live ops and SRE. Patching a live game with millions of players without downtime is the same on-call discipline as running a payments rail. Maps to: any Bellevue-HQ'd fintech, plus the Seattle SoFi presence.
Gameplay and tools. This bucket does belong in other studios. Let ProbablyMonsters and Xbox Game Studios in Redmond have them. Do not waste outreach budget.
The Bellevue geography is the recruiter's actual moat
Here is the part most outside recruiters miss. Sony is the parent. The impairment is fresh. There is no generous relocate-to-Tokyo or relocate-to-SF program coming. These engineers are anchored to the Eastside by mortgages, partners at Microsoft or Amazon, and school district enrollments.
If you can offer Bellevue or Redmond on-site or hybrid, you will out-convert SF remote offers consistently. That tilts the field toward employers most recruiters do not associate with fintech sourcing: Center (spend management, Bellevue HQ), doxo (which "built the first truly ubiquitous bill pay experience that works with any payment method, any bank, and any biller"), Xpanse (mortgage automation, Bellevue), and SoFi's Seattle engineering presence. It also tilts toward the Seattle-area offices of Cloudflare, Databricks, Datadog, Apple, and Shopify, all of which already employ this profile.
Bellevue is a moat. Anyone pitching SF remote against a 6 percent mortgage on a 4 bedroom in Sammamish is going to lose.
The comp conversation is where this gets uncomfortable. As of May 20, 2026, the average yearly pay for remote fintech in Seattle is $118,463, with most workers earning between $87,667 and $141,783. That is well below typical AAA senior engineer comp at a Sony-owned studio. Fintech offers to ex-Bungie staff have to lean on equity, scope, and title, not base. The pitch is "principal engineer owning fraud infra for a Series C," not "we pay better than Sony." You will not.
Sourcing them before June 30, not waiting for June 9
The Bloomberg report did not specify a date for the cuts, only that they follow the final update. Historically, Bungie's milestone-tied announcements have come within weeks of the ship. Recruiters who wait for the LinkedIn "Open to Work" banners are already late.
Here is the actual playbook, and where most teams break down. You need to identify still-employed Bungie backend engineers in Bellevue, filter for the four sub-profiles above, and reach out before the June 9 ship date so your conversation is already warm when severance hits. Doing that on LinkedIn alone is a disaster because Bungie's public employee count of about 850 hides the specific senior engineers in private accounts, and title searches like "Senior Software Engineer" at Bungie return everything from UI programmers to build engineers undifferentiated.
This is exactly the gap Refolk was built to close. Instead of running ten LinkedIn boolean strings and three GitHub searches, you describe the person in plain English ("senior or staff backend engineers at Bungie in the Seattle area who have worked on netcode, anti-cheat, or live-ops infra, ranked by distributed systems depth") and get a ranked shortlist that pulls signal from GitHub commits to Bungie's open-source repos, LinkedIn, conference talks, and the open web in one pass.
A search across the index for U.S.-based senior, staff, and principal engineers with multiplayer, netcode, and distributed-systems skills returns about 15,400 matching profiles, with the Greater Seattle Area in the top three regions. That confirms what the Bungie footprint already implied: Bellevue is a dense, addressable pool for this profile, and the Bungie subset of it is small enough to work through in a week if you start now.
Channels that beat InMail
Cold InMail will not work here, particularly with the recent LinkedIn changes to inbox quality scoring. Better channels, in rough order:
- GitHub commit graphs. Bungie maintains a handful of public repos. Recent committers are easy to identify and have public email addresses on commits.
- The Bungie Slack alumni group. Active, vouches travel.
- GDC Online Programming track attendee lists. The netcode talks specifically. Speakers and attendees self-select for the profile you want.
- The "Destiny 2 Game Design" LinkedIn group. Lower signal than the alumni Slack but useful for warm intros.
- r/truedestiny and r/LowSodiumDestiny mod teams. Often actual Bungie engineers. Do not pitch them on Reddit, but the names are public.
The competition you are actually fighting
If you are a fintech or real-time infra recruiter, your assumption should be that the Seattle game studios will move first and noisily. ProbablyMonsters in Bellevue, Amazon Games Seattle, the ex-Bungie diaspora at Possibility Space and Just Cause Productions, and Microsoft's Xbox Game Studios in Redmond will all post roles within days of the cuts. They will get the gameplay engineers, and that is the right outcome.
Your job is to get to the backend, anti-cheat, and live-ops engineers before those studios convince them that another AAA shop is the safe choice. After three layoff rounds since 2023, many of these engineers are explicitly trying to leave games entirely. They are receptive. They just do not know that Center, doxo, and Cloudflare's Seattle office want them, because nobody has told them in those words.
When you write the outreach, lead with the system, not the company. "Your team's matchmaking and anti-cheat work maps directly to how we keep adversarial actors off our payments rails" lands better than "we're a Series C fintech." Refolk surfaces the specific GitHub repos and conference talks each candidate has shipped, so the first sentence of your email can reference the actual work, not a job title.
What "live-service game engineer hiring" looks like in Q3
Three months from now, the Bungie cohort will be split four ways: a chunk at other Seattle studios, a smaller chunk at Sony-adjacent roles in California, a chunk that took six months off, and a chunk that crossed over to fintech and real-time infra. Which bucket is biggest depends almost entirely on who got to them in May and June, before the LinkedIn banners flipped.
If you are running Bellevue tech recruiting in the second half of 2026, this is one of the cleanest sourcing windows you will get all year. The list is small, the geography is fixed, and the competition is mostly going to mis-screen the résumés. Move before June 30.
FAQ
Who exactly is getting laid off at Bungie on or after June 9, 2026?
Bloomberg reported a significant number of layoffs tied to the end of Destiny 2 development, but the specific count out of Bungie's roughly 850 employees has not been disclosed. The most exposed groups are Destiny 2 backend, live ops, anti-cheat, and gameplay engineering, since there is no successor project greenlit. Marathon will retain a small team, but it is averaging around 10,000 concurrent Steam players and cannot absorb a full second team.
Why are Bungie netcode engineers a fit for fintech specifically?
A Destiny 2 backend engineer has spent years shipping consistent global state under continuous adversarial pressure: cheaters, DDoS, exploit economies. That problem shape is structurally identical to fraud detection at a payments company and order-book consistency at a trading venue. Anti-cheat engineers in particular map almost one-to-one onto fraud, AML, and account-takeover roles, often at higher comp and lower cyclicality than gameplay engineering.
Should I wait for "Open to Work" banners before reaching out?
No. Bloomberg did not specify a cut date, but Bungie's pattern is to announce within weeks of milestone ships, which means late June or July. By the time LinkedIn banners flip, ProbablyMonsters, Amazon Games, and Xbox Game Studios will already have warm pipelines. Sourcing through GitHub, the Bungie alumni Slack, and GDC attendee lists in late May and early June is how you get in front of these engineers while they are still deciding whether to stay in games at all.
How do I avoid mis-screening these résumés?
Treat the Bungie logo as a feature, not a category. Read the JD-equivalent of what they actually shipped: distributed backend services, anti-cheat telemetry, matchmaking, live ops on-call. If your ATS is filtering on "fintech experience" or "payments background," you will miss the entire cohort. A natural-language sourcing layer like Refolk helps here because you can describe the underlying system experience you want ("globally distributed state under adversarial load") instead of relying on industry keywords that the candidates do not have on their LinkedIn.