As a release manager, the role requires a positive level of technical understanding and goes beyond sprint planning and tracking delivery. The Release Manager owns end-to-end governance of code and configuration promotion across the program from Build through Cutover to Technical Go-Live (TGL) that is, all pre-production config movements: Dev, Dev Master, QA/Test, and Prod Master, up to and including the Production release itself. The role is the single point of control for what moves between pre-production environments, when it moves, and under what approval - ensuring every promotion is planned, reviewed, sequenced, evidenced, and auditable. This includes formal sign-off authority at each release gate (Gate 0: User Story Go/No-Go Dev Dev Master QA/Test Prod Master Prod), ownership of release documentation and versioning and enforcement of segregation of duties so that no one promotes their own change to production.
The Release Manager's accountability ends at Technical Go-Live - once a release is successfully promoted and stable in production, ownership passes out of this role. The Release Manager owns the pre-production release pipeline - and the evidence trail behind it - up to TGL. The role is a compliance trade-off by design: it improves release quality, which requires that time for gate reviews and evidence checks be planned into the delivery calendar rather than treated as absorbable slack.
Role: Delivery Release Manager/Senior
Location: Bangalore, Hybrid
Responsibilities
Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.