Game Industry Commercial Intelligence: Where studios are building & spending.

Welcome to Issue #2 of Studio State.

Embark Studios gave us the clearest signal this week.

The studio has talked publicly about pushing beyond the capacity it had planned for while operating ARC Raiders. Its current roles give us a view into what sits behind that problem, including shared backend infrastructure, live-service tooling, internal workflows, anti-cheat, monetization, AI/ML, consultants, and external development partners.

Across the rest of the studios we track, a related pattern is getting clearer. Shared developer platforms are moving closer to the center of how studios build, ship, and operate games.

Lead Analysis - Embark Studios

The Signal

Embark has been unusually open about the strain that came with operating ARC Raiders after launch. Executive producer Aleksander Grøndal said the studio was "constantly overshooting our capacity" as maintenance, bug fixes, exploits, and planned content competed for the same people and time. The evolving organization around that work is interesting.

A Tech Lead for Backend Delivery sits inside a platform team providing self-service infrastructure, tooling, and shared multi-tenant clusters to other technical functions. A Fullstack Engineer on the Live Platform team builds internal tools that automate workflows, improve studio efficiency, and provide analytics.

Other current roles point to dedicated anti-cheat backend and data capability, monetization tooling, live-service management tools, consultant capacity in UX, and external partners participating in content production.

Embark is also experimenting with AI deeper in the development process. Current roles include narrative and AI systems research, gameplay ML work, and infrastructure used to train and debug models.

Our Read

The capacity problem showed up publicly first. The current organization gives us a view into the operating model being built around it. A meaningful amount of Embark's investment sits between individual game teams. Shared backend services, developer tooling, live-service systems, workflow automation, analytics, anti-cheat, and ML infrastructure can support more than one feature team or discipline.

External capacity is part of that model too. Embark is using consultants and external partners while continuing to build internal systems that help its own teams operate more efficiently.

The Bigger Picture

Live games create operating work that doesn't exist at the same scale before launch. Content plans have to compete with maintenance, exploits, incidents, player support, monetization, community needs, infrastructure, and whatever breaks once millions of real players start interacting with the game. That pressure reaches beyond staffing.

The studio needs systems that make development repeatable, shared infrastructure that reduces duplicated work, tools that remove manual effort, and enough flexibility to add specialized capacity when internal teams can't absorb everything themselves.

Embark's current activity shows several of those pieces being developed at the same time.

What We’re Watching

We'll be watching whether Embark's use of external partners expands beyond the consultant and content work already visible, and whether its shared platform functions continue to broaden.

The more live-service work moves into reusable studio-wide systems, the clearer the commercial opportunities become around developer tooling, cloud and platform infrastructure, observability, LiveOps, AI/ML infrastructure, and specialist development services.

What We’re Seeing

Patterns emerging across the studios we track and what they suggest about where game development investment is moving.

Shared developer platforms are becoming production infrastructure

LEGO Digital Play is taking its shared publishing platform through first title integrations and its first production releases. The new Director of Production for the Publishing Platform owns a roadmap and release cadence spanning engine SDKs, backend services, the release pipeline, internal teams, third-party vendors, and co-development partners.

Nex is showing the same need from a different stage of development. Its new DevOps Engineer for Game Production supports game development through build and test infrastructure, scalable CI/CD, server tooling, and monitoring for systems including its package server and Developer Portal.

Embark's Backend Delivery team adds another version of the pattern, with self-service infrastructure, shared clusters, CI/CD, observability, build pipelines, and common development tooling supporting teams across the studio.

These companies are building different products, but the capability underneath them is becoming similar.

Build, release, observability, developer experience, and shared platform engineering are becoming production infrastructure that multiple teams depend on. That creates clearer commercial entry points for developer-tooling and platform vendors than a generic engineering opening does.

Signals Worth Watching

Company developments that could materially change how a studio builds, ships, or operates, even when there isn't yet a clear commercial opportunity.

LEGO Digital Play - Moving its platform into production

We first highlighted LEGO Digital Play while much of the company was still being assembled around foundational leadership, infrastructure, safety, and production capabilities. The latest roles show the next stage.

Its publishing platform is moving through first title integrations, first production releases, and subsequent expansion. At the same time, a new Senior Data Engineer is being asked to design and scale infrastructure for high-volume event and telemetry data used for product decisions, analytics, and compliance reporting.

Teams are beginning to depend on the platform that LEGO Digital Play has spent the last several months building. We'll be watching what capabilities appear as more games integrate with it and production usage increases.

Grasshopper Manufacture - Independent again

Grasshopper Manufacture has separated from NetEase Games and is operating independently again. The ownership change matters because it may affect how the studio funds projects, publishes games, builds internal capabilities, and works with outside partners.

We don't have enough downstream evidence yet to say which of those things will change. Grasshopper has pointed to its improved self-publishing capabilities and a desire to make a wider variety of games, but the operating consequences aren't visible yet.

The first signals after independence will tell us more than the separation announcement itself.

Where Opportunity Is Forming

Selected company signals where hiring and operating decisions point to an externally addressable need. We highlight the signal and why it matters.

Nex - Production infrastructure is becoming a more visible need

Nex already showed a broad commercial surface across external creative agencies, contract leadership, localization, and outside development capacity. This week adds production infrastructure.

Its DevOps Engineer for Game Production is responsible for the build and testing infrastructure behind game development, a scalable CI/CD pipeline, server tooling, and monitoring and alerts for systems including the package server and Developer Portal.

That widens the opportunity around Nex beyond content and external development. Developer-tooling, build and release, and observability providers now have a specific production problem to investigate as Nex continues expanding its games and product ecosystem.

Balor Games - External vendors are part of the SCP: 5K launch plan

Balor Games is preparing SCP: 5K for its 1.0 commercial launch. Its new contract Brand Manager is expected to recommend and coordinate third-party vendors across PR, social, influencer, and storefront work. The role also coordinates creative assets with external contributors and agencies.

The external opportunity is explicit. Outside providers are already part of Balor's operating model for taking the title to market, giving marketing and creative vendors a clear account to investigate as the release approaches.

Naughty Dog - External staffing and art production are already inside the production model

We only began collecting Naughty Dog this week, so the current job inventory gives us a baseline rather than evidence of sudden hiring growth. The jobs themselves still tell us something useful.

An Outsourcing Production Artist is a temporary engagement through staffing partner Yoh Enterprise Solutions and is responsible for creating art briefs for outsourcing, reviewing asset submissions, and integrating externally produced assets. A Senior Environment Lighting Artist, also contingent through Yoh, works directly with outsource vendors on visual development, technology, training, and workflows.

Because collection started this week, the data doesn't establish whether external use is increasing. It does establish that contingent staffing and external art production are part of Naughty Dog's current development model, creating identifiable opportunities across staffing and art-content services.

About Studio State

Studio State tracks hiring, company activity, and external signals across game studios to identify capability investment, organizational change, and emerging commercial opportunity. Job postings may have closed or been removed since they were originally observed.

Know someone in game-industry business development, technology, investment, or studio operations? Forward Studio State to them!