Staff Systems Software Engineer

Remote US & Canada

Most engineering roles at Thatgamecompany ship features to players. This one ships velocity and quality to engineers. Cloud, Gameplay Backend, and Cross-Platform Backend build the services and features the game runs on; you build the systems that prove that work is correct, fast, and ready — before it reaches players. You will build the systems that prove the gameplay feature works — at scale, on every device, on every commit — and the infrastructure that lets a hundred engineers find that out in minutes instead of days. If it runs in production, another team owns it. If it exists to test, measure, or accelerate what those teams build — test harnesses, load/chaos infrastructure, device labs, build/GPU clusters — you own it. Your output is the studio's velocity and the game's quality floor.

On any given day, you might:

Build and own the studio's functional test automation framework — runner, fixtures, game-state harness, reporting — plus coverage instrumentation that makes untested systems visible

Build regression analysis tooling that separates real regressions from noise and attributes them to a commit automatically

Improve test suite speed/trust via flake detection, quarantine, parallel sharding, deterministic replay

Design load/stress testing systems modeling realistic player behavior, capable of driving launch-scale synthetic traffic against pre-production

Build chaos testing capability — fault injection, latency/partition simulation, dependency failure — run safely against real infrastructure

Run disaster recovery exercises, measure actual RTO/RPO vs. stated targets, and turn findings into permanent regression tests

Build app quality testing automation — frame time, memory, thermal, battery, cold-start captured automatically and gated in CI

Own the device compatibility lab, orchestration, and certification matrix so device support is verified every commit, not the week before ship

Build/operate on-prem build clusters (distributed compilation, caching, artifacts) and on-prem GPU clusters (scheduling, multi-tenancy, utilization), backing buy-vs-build with real data

Design cross-platform developer tools — including AI-assisted tooling (agents, skills, MCP servers) — that reduce toil across Cloud, Backend, and Client Engineering

Define, instrument, and publish developer velocity/quality metrics (build time, test cycle time, flake rate, escaped defect rate, MTTR) and use them to prioritize your roadmap

Drive adoption across teams that don't report to you

Mentor engineers in testing strategy, performance analysis, systems thinking

Raise the bar through code review, documentation, reducing bus factor

Be a passionate gamer who puts players first

Treat developer experience as a product — users, adoption curves, a quality bar — not internal plumbing

Operate at Staff level: set technical direction studio-wide, influence without authority

Be relentless about systems that prevent problems, not just report them

Embrace experimentation for ambiguous, complex problems

Communicate trade-offs clearly across distributed teams