Bungie's 292-Person WARN Names "Goliath" and "Run." Source Off the Codenames.
Bungie's June 26 WARN filing lists 292 Bellevue roles with titles intact. Here's how to decode Marathon's "Goliath" and "Run" codenames before July 9.
Sony confirmed the Bungie cuts on June 25, 2026. The next day, a Washington WARN notice landed with 292 Bellevue employees on it, names and addresses redacted but every business title intact, including roles filed under Marathon's internal codenames "Goliath" and "Run." Separations take effect July 9. If you source live-service engineering leadership, this is a two-week window that almost never opens.
Most recruiters will run the same play: search "Marathon" on LinkedIn and blast connect requests. That will get you second-round attention at best. The edge in this filing is not the game name. It is the codenames, the redacted title map, and the credits data that lets you back the redactions out.
What the filing actually contains
The Washington State Employment Security Department's WARN database publishes the employer, business location, worker count, layoff type, effective date, and a downloadable PDF of the notice. In Bungie's case, the PDF has names and home addresses redacted but the business titles are visible in full.
That includes roles across artists, engineers, producers, designers, technical animators, and audio leads. It also includes senior lines you rarely see on a WARN in one shot: a General Manager, an Engineering Director, producers and creative leads under "Marathon," and a Chief Vision Officer line that appears to point to Bungie co-founder Jason Jones. Bloomberg's Jason Schreier separately reported that studio head Justin Truman is stepping down less than a year after taking over from Pete Parsons.
Marathon director Joe Ziegler is publicly confirmed still in place. He is not a target. His reports are.
The address matters
Every affected employee worked at Bungie's Bellevue office at 550 106th Avenue N.E. That is a concrete geographic anchor for competitor mapping: ProbablyMonsters, Undead Labs (Microsoft), Halo Studios (formerly 343), Valve, Amazon Games Seattle, and Sony's own newly spun-out Seattle-area studio are all within a short commute. Most of these 292 will not want to relocate. Recruiters pitching remote roles or Bellevue-based studios have a real advantage over LA and Austin outreach.
Why "Goliath" and "Run" are the actual sourcing signal
Every recruiter with a LinkedIn Recruiter seat is going to Boolean on "Marathon" this week. That surface is already crowded. The filing lists some Marathon roles under "Goliath," which was Marathon's internal codename during development, and others under "Run," which is tied to Marathon's team structure. These strings appear almost nowhere outside Bungie.
That is the point. Anyone who lists "Goliath" or "Run" on their LinkedIn profile, in a GDC talk bio, in a portfolio site, or in a public credits entry is self-identifying as tenured Marathon staff who was inside the room when the codename was current. Those are the seniors. Boolean off the codenames, not the game.
A practical pass:
- LinkedIn X-ray:
site:linkedin.com/in "Goliath" "Bungie"andsite:linkedin.com/in "Project Run" "Bungie" - GitHub bios and READMEs: same strings, plus
"Marathon" "Bungie"for engineers who ship dotfiles or personal tooling - MobyGames credits: search Bungie's Marathon page and pull anyone credited on the tech side over the last three years
- GDC Vault and Digital Dragons speaker archives for talks tagged with Bungie in 2024 through 2026
This is exactly the kind of query that dies in a Boolean box and works in plain English. We built Refolk so you can ask "ex-Bungie senior engineers in Bellevue who worked on Marathon or its codename Goliath" and get a ranked shortlist across GitHub, LinkedIn, and the open web without stitching X-rays together by hand.
Cross-reference credits with the redacted title list
The Game Post already ran the play once. Public Marathon credits list Brad Fish and Eamon McKenzie under Engineering Director. The WARN filing lists exactly one Engineering Director line for Marathon, name redacted. You cannot say from the filing alone which one it is, but you can say that the pool is small, public, and reachable.
Extend the method:
- Pull the Marathon credits list from MobyGames and Bungie's own site
- Pull the WARN title list from the ESD PDF
- For each senior title on the WARN (Director, Principal, Staff, Lead, Manager, GM, CVO), find the public credits that match that discipline and seniority
- Where there is only one public name for a WARN line, you have a near-identification. Where there are two or three, you have a small named list to reach out to in parallel.
The Chief Vision Officer line is a good example of what this reveals. Bungie previously named Jason Jones, a co-founder, as Chief Vision Officer in official material. If that line is Jones, the exodus is not a Destiny cleanup. It is a full leadership reset. Senior Marathon ICs will be reading the same tea leaves you are, and they are unusually open to a first message right now.
Boolean off the codenames, not the game name. The seniors self-identify.
The 292 is a floor, not a ceiling
Two numbers that are not on the WARN matter as much as the ones that are.
First, contractors. Forbes reported that contractors on both Destiny and Marathon were cut in the same wave. WARN excludes contractors. That means the Destiny 2 live-ops contractor cohort, in the middle of a hotfix cycle, is a hidden pool of senior live-service engineers no one is talking about publicly. These people are not on any filing. They are on Discord, in credits, and in the "Bungie Alumni" informal LinkedIn network.
Second, the filing only surfaces Marathon roles whose title literally contains "Marathon," "Goliath," or "Run." Anyone whose title read "Senior Engineer" or "Producer" without the project tag is invisible in the PDF, even if they were a full-time Marathon dev. Gameriv makes this point directly: the real Marathon impact is likely larger than the named roles suggest.
If you have been tracking Bungie since the $3.6 billion Sony acquisition, you have watched more than 600 people leave a studio that had over 1,400 before the cuts began. That is a diaspora, not a single event. The July 9 cohort will hit a market that already contains former Bungie principals at Amazon Games, Microsoft, and independent studios who make excellent warm introductions.
The outreach window is narrower than it looks
Notice was June 25. Separations take effect July 9. Severance in this bracket typically runs 60 to 90 days. That gives you a practical outreach envelope: warm, respectful messages between July 10 and late September, before signing bonuses at competing studios close and before the "I already committed somewhere" replies start piling up.
Sony's public line, via SIE Studio Business Group CEO Hermen Hulst, is that impacted staff will be considered for redeployment across the global network. Read that against the fact that SIE is simultaneously cutting its own Bungie-support roles. Internal redeployment capacity is thin. These 292 are actually on the market.
What good outreach looks like this week
- Do not lead with "saw you were impacted." Everyone will send that message.
- Do lead with the specific system they shipped. Marathon extraction-shooter tech, Destiny 2 sandbox engineering, matchmaking, netcode, anti-cheat, engine work: each of these maps to a public talk, patch note, or credit.
- Reference the codename if it is on their profile. It signals you did the work.
- Offer a warm intro before a role. The best of this cohort will have three offers by August. What they will not have is a curated list of the right two conversations.
Recruiters spend most of the first week of a wave like this rebuilding a candidate list they should have already had. This is where Refolk earns its seat: you describe the person in plain English, and it pulls a shortlist from GitHub, LinkedIn, and the open web, including the codename signal that most tools bury.
Communities where this cohort is already talking
The public conversation is happening in a handful of places you should be reading, not just searching:
- Amir Satvat's games layoff tracker and support network, which has become the default clearinghouse for game-industry displaced talent
- The informal "Bungie Alumni" LinkedIn network, which activates quickly on waves like this
- Work With Indies, for anyone considering an indie or small-team move
- Into Games Discord and r/gamedev, for junior-to-mid ICs
- LinkedIn #OpenToWork tags filtered to Bellevue and Seattle, which will spike between July 9 and July 20
The senior cohort will not post publicly first. They will move through warm intros, ex-Bungie principals now at Amazon Games or Microsoft, and a small number of trusted recruiters. If you want to be one of those recruiters by 2027, the work is this month.
The bigger pattern
Sony absorbed a $765 million impairment loss across the fiscal year tied to Bungie's wider portfolio. That is not a number that gets reversed with one more cut. Expect at least one more filing in the next 12 months, and set up an email subscription on the Washington ESD WARN database so you see the next one on the day it posts.
Sourcing from WARN notices is a discipline. Read the titles, not the headline number. Cross-reference credits. Boolean off the codenames. Assume contractors and untagged staff double the visible pool. Move in the first 14 days.
Bungie's WARN gave you an unusually clean read on a live-service leadership bench that almost never surfaces intact. The studios that do the work this week will hire the people the studios doing the work in August only get to interview.
FAQ
How do I access the actual Bungie WARN filing?
The Washington State Employment Security Department maintains a public WARN database at esd.wa.gov. It lists the employer, business location, worker count, layoff type (layoff or closure), and effective date, with a downloadable PDF of each notice. For Bungie, the PDF has employee names and home addresses redacted, but every business title is visible. You can also subscribe to email alerts for new filings, which is the single highest-ROI subscription for anyone sourcing in Washington state.
Are the "Goliath" and "Run" codenames really that useful for sourcing?
Yes, more than the game name itself. "Marathon" is going to be Boolean-searched by every game recruiter in the country this week. "Goliath" and "Run" appear almost nowhere outside Bungie's internal documents, GDC talk slides, and credits sections. Anyone who lists either on a LinkedIn profile, portfolio site, or public credits entry is self-identifying as tenured Marathon staff. That is a much cleaner filter for senior talent than the game name.
Why is 292 a floor rather than a real headcount?
Two reasons. First, WARN filings exclude contractors, and Forbes reported that contractors on both Destiny and Marathon were cut in the same wave. Second, the filing only tags roles whose titles explicitly contain "Marathon," "Goliath," or "Run." Marathon developers whose titles read generically as "Senior Engineer" or "Producer" are invisible in the PDF. Assume the real impacted pool, especially on the Marathon side, is meaningfully larger than 292.
When is the best outreach window for this cohort?
Separations take effect July 9, and severance typically runs 60 to 90 days afterward. That puts the strongest window from July 10 through late September, before signing bonuses at competing Seattle-area studios like ProbablyMonsters, Undead Labs, Halo Studios, Valve, and Amazon Games Seattle close out the top of the cohort. First-week outreach should be warm and specific, referencing shipped systems rather than the layoff itself.