Release Manager

Role Overview This role is first and foremost about getting finished games out of the door and into players' hands, cleanly certified, live on every platform, and supported long after launch. You own the release pipeline end to end, platform certification and submission; the backends for PC and console platforms, and the post launch update cycle for every title in the catalogue. You coordinate closely with the Mythwright Production team and development partners across every project, managing build cadence and holding releases to quality and schedule. You work hands on across platforms, using emerging tools and automation to streamline submissions and reporting. Key Responsibilities 1 - Release and Certification You manage releases and submissions on Steam and other PC storefronts as necessary, as well as console certification and submission with Sony, Microsoft, and Nintendo. Validate builds against platform requirements, and run the PC and console backends, depots, and branches so every build ships correctly. You track cert requirements as they change and build repeatable checklists so submissions pass first time, using automation for build validation and backend configuration where it improves reliability. You’re able to conduct console compliance passes yourself or you coordinate passes via a vendor. Success looks like: Builds pass console certification first time, or with minimal cert resubmissions. Releases ship on schedule across PC and console platforms. Builds, depots, and branches are configured correctly ahead of launch. Platform requirements are tracked early with no launch day surprises. Submission checklists make smooth releases repeatable. Automation removes manual effort from build validation and backend setup. 2 - Launch Coordination You execute on the launch windows defined by marketing, coordinating developers and platforms so every title goes live correctly and on time across PC and console. You own the day of launch runbook end to end, sequencing platform go live steps so nothing slips through the cracks, and keep the studio informed with a clear, current view of release status. Success looks like: Launches proceed smoothly with developers and platforms coordinated. Store pages, builds, and branches activate cleanly at the launch moment. Launch day issues are triaged and resolved without disrupting release. Release status is visible and current across the studio. Launch runbooks are clear, repeatable, and improve with each title. Risks are surfaced early with practical options ahead of launch. 3 - Live Operations and Updates You own the post launch update cycle for every title in the catalogue, maintaining the update cadence beyond launch and managing certification and submission for every patch and update. You coordinate fixes with developers, keep live builds current across every platform, and use automated workflows to deliver regular updates efficiently without manual overhead. …