Fishlabs Cuts Staff Citing 'Changing Project Requirements'

Fishlabs, the Hamburg-based studio behind the Galaxy on Fire series and more recently Chorus, has announced layoffs affecting its development and support teams, citing what the company called "changing project requirements." No headcount, severance terms, or timeline have been disclosed so far, which itself tells you something about where affected workers stand.

The studio, owned by Plaion's Deep Silver label since 2013, attributed the cuts to shifting needs around its current project slate rather than a formal closure or restructuring announcement. The exact phrase — "changing project requirements" — is doing a lot of load-bearing work here, and practitioners in game development will recognize the pattern.

What does this mean for affected roles?

For the developers and support staff implicated, the practical consequences are immediate. Studio-level layoffs in games typically hit QA, live-ops support, and mid-level engineering first, because those functions map most directly onto a project's current phase. When "requirements change," the roles attached to the de-scoped or pivoted work are the ones cut. Fishlabs has not specified which sub-teams within development and support are affected, nor how many people.

That lack of disclosure matters for anyone reading the German games labor market. Without a headcount, it's harder to judge whether this is a routine trim — single digits — or a deeper cut that signals the current project is in trouble. Publicly, neither Plaion nor parent Embracer Group has commented beyond the studio's statement.

A familiar pattern, not an isolated one

This is not Fishlabs' first contraction. The studio went through layoffs in 2024, roughly a year after shipping Chorus in 2021, and Embracer's broader portfolio has seen repeated restructuring since its 2023 restructuring program. Fishlabs sits inside that structure, so a studio-level "project requirements" explanation often reflects publisher-side portfolio decisions as much as local management.

For individual developers, the read is straightforward. A studio citing project-level causes is usually still alive but repositioning — which means hiring may resume in adjacent specializations (a studio cutting support roles while a project pivots often rebuilds around new tech or genre demands). Watching what roles Fishlabs posts over the next two quarters will tell you more than the layoff announcement itself.

What should workers in the sector take from it?

Support and QA staff remain the most exposed functions across mid-sized European studios, because their staffing scales with live projects rather than permanent pipeline needs. Developers with portable, engine-specific skills — Unreal or Unity specialization that transfers across studios — face shorter gaps between roles than those tied to a single proprietary pipeline.

If you're inside a Plaion or Embracer-owned studio, the useful signal is portfolio language. "Changing project requirements" at one studio has, across the 2023–2024 restructuring cycle, preceded similar announcements at sibling studios within months. Watching for that wording is a legitimate early-warning practice.

Fishlabs has not announced a replacement project, a hiring freeze, or any further staffing statements; whether the studio restaffs around its revised slate should become clear from its next published credits and job postings.