Release Manager
About this position
Responsibilities
• Release Planning and Coordination
• Rollout Planning: Develop detailed rollout schedules in collaboration with engineering teams, defining milestones, essential tasks, and dependencies.
• Stakeholder Communication: Coordinate with relevant stakeholders (e.g., Engineer, SRE, Platform, and POs) to keep everyone aligned on release timelines, expectations, and associated risks.
• Documentation and Compliance: Ensure all release documentation, including change logs and rollback plans, is updated and stored according to company policies.
• Change Management
• Change Request (CR) Management: Review, prioritize, and track CRs, coordinating with engineering and product teams to assess risks, impacts, and implementation needs.
• Change Advisory Board (CAB) Coordination: Act as the primary liaison with CAB, presenting fundamental changes, risk assessments, and mitigation plans to gain approval.
• Incident and Risk Management: Identify and mitigate risks related to release changes, ensuring backup plans are in place for critical changes.
• Service Delivery Oversight
• Service Quality Monitoring: Oversee post-release monitoring, working with the SRE and platform teams to measure service stability and performance after rollout.
• Continuous Improvement: Gather feedback after releases to identify pain points, process bottlenecks, or improvement opportunities for smoother future releases.
• Operational KPI Tracking: Track services delivery KPIs, such as release frequency, success rate, and deployment downtime, to assess the efficiency and quality of the release process.
• Cross-Functional Alignment and Support
• Collaboration with Product Owner: Work closely with POs to ensure release timelines are aligned with product roadmaps without impacting PO focus on strategy.
• Support Engineering Teams: Coordinate with technical teams to align release readiness, including final testing, pre-release verification, and sign-offs.
• Incident Response Coordination: In the event of a critical post-release issue, coordinate rollback or patch deployment, minimizing service disruption.
Requirements
• Smooth and Timely Releases: Releases happen on time with minimal disruptions, and issues are quickly resolved if they arise.
• Effective Risk Management: Risks are well-identified and mitigated, with clear backup plans.
• Stakeholder Satisfaction: POs and engineering teams have fewer operational interruptions, allowing them to focus on core product and development tasks.
• Continuous Improvement: Consistently applies feedback to optimize the release process, reducing the likelihood of incidents and improving overall service quality.