Hiring Trends

Fishlabs Cuts Staff Across Dev and Support Teams

Fishlabs confirms layoffs across development and support teams, citing "changing project requirements" — with no headcount disclosed.

Updated

Fishlabs has announced layoffs, citing "changing project requirements" as the reason. The job cuts are impacting both th
Fishlabs has announced layoffs, citing "changing project requirements" as the reason. The job cuts are impacting both th — mwitt1337 / pixabay

Fishlabs has confirmed layoffs hitting both its development and support teams, with the Hamburg-based studio attributing the cuts to "changing project requirements."

The company's own wording is the only explanation on the table. No headcount, no severance terms, no timeline. That silence matters, because it forces affected workers and industry watchers to read the pattern instead of the press release.

Which roles are affected?

Both groups named in the announcement are feeling it. Development staff — the engineers, artists, and designers building the studio's titles — face cuts. So do support staff, the people who keep projects and players serviced after launch.

Laying off both simultaneously is unusual. Studios under financial pressure typically trim support functions first, since development capacity protects the product pipeline. Cutting both at once, and framing it around "changing project requirements," points more toward a strategic pivot — a cancelled, rescoped, or redirected project — than to simple cost trimming.

What does "changing project requirements" mean for staff?

In practical terms, this phrasing signals that specific skills the studio paid for last year no longer match what it needs next. For developers at Fishlabs, that means the safest positions are the ones tied to whatever the new project direction demands.

For support staff, the calculus is harsher. When a studio rescopes, support roles tied to the deprioritized work are usually the first to go and the last to come back.

The wider picture

The games industry has been through successive waves of job cuts across development studios of every size, and announcements like this one rarely arrive with hard numbers attached. That absence of data is itself a signal: companies disclose headcounts when they want to demonstrate proportionality, and withhold them when the figures are small enough to avoid regulatory disclosure or uncomfortable enough to invite scrutiny.

For practitioners watching this space, the actionable read is straightforward. A studio citing project-level restructuring rather than broader financial distress is telling you its hiring needs have shifted, not disappeared. Anyone affected should treat the news as a repositioning of their market value inside the company — and, realistically, a prompt to test it outside.

Source: Google News: Layoffs

game-industry-layoffsstudio-restructuringtech-layoffsgaming-careers

Share this article:

More from Daniel Okafor

Daniel Okafor

Show full bio

News editor covering regulation, policy and their impact on Job market data and labor economics at Path & Pay.

476 articles

Go deeper

« Previous articleNext article »