You will run our calendarized release cadence, which includes monthly maintenance releases plus quarterly major feature releases and serve as the central point of accountability for release readiness, sequencing, communication, and post-release validation. You will work shoulder-to-shoulder with Engineering, QA, DevOps, Product, Support, and the Incident Response team to make sure every release reaches production cleanly and every regression is caught early. This is not a paperwork role. It is a high-judgment coordination role for someone who genuinely enjoys reducing chaos and pulling signal out of a fast-moving release pipeline.

Own the end-to-end release calendar for Atlas 5, including monthly releases and the major release train. Drive release readiness reviews: scope freeze, code freeze, regression sign-off, deployment plan, rollback plan, and go/no-go decisions. Partner with QA leadership to track regression trends, rejected-ticket spikes, and exit-criteria adherence release over release. Coordinate deployments with DevOps across all environments (dev, QA, staging, UAT, production) and across tenants where deployment ordering matters. Author and publish release notes, internal change communications, and customer-facing release announcements aligned to our release versioning scheme. Run the Change Advisory Board (CAB) process for production changes: agenda, evidence package, approvals, and audit trail aligned with ITIL practices and our SOC and ISO controls. Drive post-release validation, hot-fix triage, and integrate findings back into release retrospectives. Maintain release dashboards in Jira (and downstream reporting) so executives, support, and engineering see the same picture of what is shipping when. Continuously improve release tooling, automation, and metrics: release cycle time, change failure rate, mean time to restore, escaped defect rate. Serve as the release-side coordinator during major incidents that span an active release Window

• 5+ years in release management, technical program management, or a closely related • discipline at a B2B SaaS company. • Proven experience establishing and maintaining SaaS releases. • Demonstrated ownership of a recurring release cadence in production, including major • releases that touch multiple teams and tenants. • Strong working knowledge of CI/CD pipelines, branching strategies, environment promotion, • feature flags, and rollback patterns. • Hands-on fluency with Jira (or equivalent) for release tracking, including dashboards, JQL, • and integration with QA and DevOps tooling. • Practical experience operating inside an ITIL-aligned change management framework (CAB, • RFC, change classifications, audit evidence). • Excellent written communication. Release notes, executive updates, and incident-adjacent • comms must be clear under time pressure.