Xbox layoffs reportedly gut Id Software’s coding team and cut 60-70 developers from Obsidian

In the weeks following Microsoft's acquisition of Activision Blizzard for nearly $69 billion, the gaming giant has been quietly reshuffling its development talent. A new report from Video Games Chronicle paints a stark picture: id Software, the legendary studio behind Doom and Quake, has seen its coding team gutted. While Obsidian Entertainment, maker of The Outer Worlds and Grounded, lost between 60 and 70 developers. The scale of these cuts goes far beyond typical seasonal trimming - it threatens to hollow out the very engineering capability that made these studios iconic.

For a company that now owns more triple-A studios than any other publisher on Earth, these layoffs raise uncomfortable questions about the sustainability of its content pipeline. If id Software can no longer count on its veteran engine architects, who will maintain and improve the id Tech engine that powers many of Xbox's flagship shooters? If Obsidian has shed nearly a third of its technical staff, how will it keep delivering the sort of deep, systems-driven role-playing games that defined its reputation?

These aren't abstract concerns for studio managers they're risks that ripple through every layer of game development - from build stability to shader compilation to the long-term health of the codebase. Let's look at what the reports actually tell us, what it means for the teams left behind, and what the wider industry can learn from this forced reorganization.

The Scale of the Cuts: More Than Just Numbers on a Spreadsheet

According to VGC's sources, id Software's layoffs primarily targeted engineers working on core engine technology and tooling. This is the team responsible for the Vulkan renderer, the physics simulation pipeline. And the low-level systems that let Doom Eternal run at 120 fps on a mid-range GPU. Removing experienced engine programmers doesn't just slow down feature development; it erodes the proprietary knowledge that has accumulated over two decades of real-time rendering R&D.

At Obsidian, the cuts were broader. The reported 60-70 departures represent roughly 15-20% of a studio that had around 400 employees before the reductions. Notably, several senior systems designers and narrative programmers were among those let go. These are the people who write the branching dialogue trees, the quest scripting frameworks, and the save‑game migration logic that make RPGs feel responsive to player choice. Losing them mid‑development cycle - particularly if the studio is already deep into work on The Outer Worlds 2 or the rumored Avowed - can stall production for months.

What makes this especially concerning is the timing. Microsoft's fiscal year Q2 2024 earnings call boasted record gaming revenue, driven largely by the Activision Blizzard acquisition. The company isn't laying off staff because it's running out of money it's laying them off as part of a larger restructuring meant to "align resources with priorities" - corporate shorthand for cutting costs in areas that no longer fit the immediate profit profile.

Why Engine Teams Are Particularly Vulnerable - and Why That's Dangerous

Engine programming is often misunderstood as a cost center rather than a competitive advantage. A typical triple‑A engine team lives in a world of deferred maintainability: they spend months refactoring a rendering pipeline. And the payoff only becomes visible two years later when a game ships at 60 frames per second while a competitor's stutters at 30. In the short term, it's easy for finance departments to view engine work as overhead that can be trimmed without immediate consequences.

Yet the physics of software deterioration is unforgiving. Without ongoing investment, engine tech begins to accrue technical debt that compounds exponentiallyFor example, id Software's id Tech 7 was lauded for its clean architecture compared to id Tech 6. That quality came from years of continuous care by a dedicated core team. If that team is halved, the next iteration - id Tech 8 - will almost certainly ship with design compromises that future developers will pay for many times over.

We saw a similar pattern inside EA's DICE studio after the Frostbite engine became nearly impossible to update without breaking older games. Engine teams that are gutted rarely recover their full velocity; they become reactive maintenance teams rather than proactive innovation engines. For Xbox's internal studios, this could mean longer development cycles, more engine‑caused delays - and eventually, games that rely on middleware like Unity or Unreal rather than their own differentiated technology.

Obsidian's Lost Developers: A Case Study in Narrative Systems Engineering

Obsidian has always punched above its weight by building sophisticated data‑driven narrative systems. Games like Pillars of Eternity and The Outer Worlds use custom scripting engines that allow writers and designers to author complex reactive quests without needing a programmer to glue each line of dialogue. This is the sort of technical architecture that gives smaller teams a multiplicative output.

When you lose even a handful of the people who designed and maintain such systems, the risk is not just that future games take longer it's that the systems themselves become undocumented, fragile, and eventually abandoned. New engineers brought in to replace departed staff often end up rewriting subsystems from scratch because no one understands the original design decisions. In software engineering best practices, this is known as the "bus factor" - the number of people whose departure would cripple a project. Obsidian's bus factor just got a lot lower.

Furthermore, RPGs rely on extremely tight coupling between narrative content and engine functionality. A change to the quest system can ripple through hundreds of script files. Without veterans who can predict these side effects, the risk of regression bugs skyrockets. Quality assurance budgets rarely increase to compensate, so players end up encountering more broken quests, soft‑locks, and save‑game corruption.

The Broader Microsoft Strategy: Efficiency Over Expertise

To understand why a company with record revenue would cut so deep, we have to look at the larger organisational shift. Microsoft Gaming CEO Phil Spencer has been explicit that the company is focused on "growing the platform" - Game Pass subscription and cloud streaming - rather than the artistry of individual studios. In this view, studios are content factories. And layoffs are simply a way to prune inefficient manufacturing lines.

But games aren't widgets. A factory analogy ignores the profound interdependence of technical talent and creative output. When you remove senior engineers, you don't just lose lines of code. You lose the mental model of how the entire game systems interact. VGC's report specifically mentions that some of the departed id Software developers were the architects of the temporal anti‑aliasing and motion clarity systems that make Doom Eternal feel so responsive. Those exact algorithms aren't in textbooks; they exist only in the minds of the engineers who wrote them.

Microsoft may be betting that this kind of expertise can be reacquired later or replaced by middleware. But in practice, recruiting world‑class engine engineers is notoriously difficult. The entire market of senior render engineers is probably fewer than 5,000 people worldwide. Most of them already have jobs at Epic, Unity, or NVIDIA. So even if Microsoft wanted to rebuild id Tech 8 with a new team, the talent simply isn't Available on demand.

What This Means for Game Developers: Practical Lessons

For engineers working in the games industry, these layoffs are a grim reminder that even a company with an AAA‑caliber library and a dominant subscription service can treat human talent as disposable. If you're a programmer at a large publisher, here are three actionable takeaways:

• Document everything. Institutional knowledge evaporates the moment a person leaves. Write architecture decision records (ADRs) for every important system. Keep READMEs that explain why, not just what.
• Build a public portfolio. Since The developers who landed on their feet after the id Software cuts were the ones with open‑source contributions, conference talks. Or published technical blog posts. A Stack Overflow profile isn't enough; you need proof of your engineering thinking that transcends your employer.
• Diversify your skills. If your entire career is built around one proprietary engine (id Tech, Frostbite, etc. ), you're more vulnerable than someone who also knows Unreal, Unity. Or general‑purpose systems programming. The game industry consolidates; your skills should be portable,

The Ripple Effect on Game Quality and Player Experience

Players may not read analyst reports, but they will feel the consequences? When a studio loses its engine experts, the observable results include:

• Longer load times because streaming pipelines are no longer optimized
• Shader compilation stutter on PC (a problem that Doom Eternal famously avoided)
• Reduced modding capability if toolchains are abandoned
• More frequent bugs in edge‑case interactions between narrative systems and game mechanics

We already saw hints of this when the team behind Redfall (a game from Arkane Austin, another Microsoft studio that was later shut down) shipped with unacceptable performance and stability issues. While that case involved many factors, the underlying pattern was the same: senior engineers had left or been reassigned and the remaining team lacked the knowledge to fix deep engine problems quickly.

If id Software's next Doom game ships with frame‑time spikes or memory leaks that previous titles avoided, players will attribute the problem to "bad optimization" rather than to a management decision made three years earlier. The disconnect between corporate restructuring and shipped quality is one of the hardest problems in video game production. And it rarely gets the Attention it deserves.

FAQ

A Warning for the Industry: The Cost of Short‑Term Thinking

What is unfolding at id Software and Obsidian isn't an isolated incident. Across the games industry, we are seeing a wave of layoffs that disproportionately target technical roles. In the last 12 months, companies like Unity, EA, Sony. And Riot Games have all announced significant cuts. The common justification is "efficiency," but the outcome is the slow erosion of engineering capacity that took a decade to build.

From a software engineering perspective, this is a classic case of optimising for short‑term cost metrics at the expense of long‑term system health. In production environments, we often see that every dollar saved by cutting senior engineers ends up costing two dollars later in bug fixes - slower iteration. And missed deadlines. Games are particularly unforgiving because they ship with a fixed scope and date - you cannot patch a delayed launch.

There is a better way. Instead of one‑off layoffs, companies could use internal transfers to move engineers from maintenance projects to growth projects. They could reduce contractor overhead before cutting permanent staff. They could offer voluntary buyouts with generous re‑skilling packages. But those approaches require long‑term thinking that public quarterly earnings rarely reward,

Conclusion: The Talent That Leaves Doesn't Come Back

The most important lesson from the Xbox layoffs is that talent isn't an inventory item. The engineers who designed id Tech 7, who built Obsidian's narrative systems, who spent years debugging the edge cases of a Vulkan pipeline - they aren't interchangeable commodities. Once they're gone, they find other industries, other projects, or retire. The next Doom will be made by a different team with different knowledge. Whether that results in a better or worse game remains to be seen, but it will certainly be different.

For developers reading this, the message is clear: invest in yourself, document your work. And stay adaptable. For executives, the message is equally clear: the only sustainable way to produce great games is to protect the people who make them. Every layoff is a bet that you can rebuild expertise later. History suggests that bet usually loses.

If you have been affected by these cuts or are considering your next career move in game development, share your story in the comments. We need to talk more honestly about the human side of software engineering - it's the only way to build an industry that respects the craft as much as the quarterly report.

What do you think?

Should Microsoft prioritise preserving in‑house engine expertise even if it lowers short‑term profit margins?

What engineering practices could studios adopt to reduce the bus factor before layoffs strike?

Is it realistic for a large publisher to maintain multiple proprietary engines,? Or is consolidation to Unreal inevitable,