You are a software developer sitting inside compliance. You will build and continuously evolve a secure compliance pipeline so we can ship games and platform changes faster and safer - and you will be the technical person who defends what we shipped when an auditor, a certification lab, or a regulator asks.
The scope is not games alone. You will stand in front of game certification labs, and you will also defend the platform: ISO certification of our systems and the evidence work that leads into a future SOC 2 audit. In every case, the job is the same. You produce the proof. You walk the auditor through it. You answer the question that was asked, with the evidence that was requested, and you stop there.
You will own the technical side of game certification. You take a game math package from the review channel to the lab, you produce the evidence the lab needs - build hashes, PAR sheets, configuration snapshots, version manifests - and you answer the lab’s technical questions yourself, without a developer sitting next to you. When a certificate comes back, you are the person who confirms every deficiency is closed before the game is allowed past the pre-release gate.
Between lab submissions, you treat the pipeline as a product. Manual evidence collection, one-off screenshots, and tribal knowledge are the things you replace. You automate controls, tighten the audit trail, and shorten the path from “ready to ship” to “ready to show an auditor” without weakening the bar. Faster and safer at the same time is the point of this role - not one at the expense of the other.