Change & Release Manager_ Noida

Change & Release Manager

End-to-end change governance and integrated release planning Role element Description

Function

Technical Management / Change & Release Management

Reports to

Manager Change Management

Environment

Customer-facing, multi-service and multi-vendor integrated delivery

Experience

Typically, 8–12 years in IT/telecommunications service delivery, operations & service management

Document status

Version 1.1 | October 2026

1. Role Purpose

Accountable for governing the end-to-end change lifecycle and coordinating integrated release planning to enable safe, predictable and compliant delivery with minimum avoidable service disruption. The role acts as a central coordination point for customers, service owners, technical teams, project/release stakeholders and suppliers—balancing delivery priorities, risk, service stability and business needs.

2. Key Accountabilities Area Core responsibilities

Change governance

Own the change portfolio and process controls; review RFC completeness, classification and traceability; maintain change policy, workflows, change models and standard-change catalogue. Ensures NO unauthorized changes.

Risk & readiness

Coordinate end-to-end risk/impact assessment with technical and service owners; validate dependencies, affected services, outage impact, resources, prerequisites, test evidence, implementation and rollback plans.

CAB / eCAB

Prepare agendas and decision packs; facilitate CAB and emergency CAB; ensure appropriate stakeholders, documented decisions, approval conditions and escalation of unresolved risks.

Scheduling & coordination

Maintain the integrated change calendar; resolve schedule conflicts; coordinate windows, resources, vendor/customer dependencies and support coverage; enforce blackout/freeze controls.

Communication

Coordinate timely, audience-appropriate communications covering impact, timing, risk, required actions, implementation status, completion/failure and escalation arrangements.

Implementation & recovery

Track execution and record outcomes; coordinate response to change-related incidents; lead/coordinate PIR and failed-change reviews; track corrective actions and update relevant knowledge/runbooks.

Compliance & improvement

Maintain audit-ready records; monitor policy adherence; support relevant ITIL and ISO/IEC 20000 controls and applicable information-security controls; drive improvements using trends and lessons learned.

Dashboard & governance

Own accurate change reporting, upcoming activity, risks, conflicts, failures, exceptions and actions; provide clear customer/leadership updates and escalate material issues.

3. End-to-End Release Planning (Additional Accountability) Lifecycle stage Responsibilities

Intake & scope

Consolidate release scope, objectives, owners, milestones and success criteria with engineering, product, service and technical teams.

Integrated planning

Maintain the release calendar and integrated plan; resource planning; coordinate sequencing, resource demand and business constraints.

Readiness & controls

Coordinate readiness checkpoints for testing/signoffs, security/compliance, operational acceptance, support coverage, monitoring, and required change approvals.

Deployment & go/no-go

Ensure deployment runbooks, implementation sequence, validation, rollback/back-out, communications, escalation paths and accountable owners are documented; facilitate go/no-go decisions by authorised owners.

Release execution

Coordinate release-day status/war-room cadence where required, cross-team hand-offs, issue escalation and stakeholder updates; maintain risks, issues, dependencies and action logs.

Validation & closure

Coordinate post-deployment service validation, outcome confirmation, release closure, lessons learned and follow-up actions; analyse schedule adherence, rollbacks, incidents and recurring defects.

Accountability boundary: The role owns governance, integration and coordination. Technical implementation remains with designated engineering/deployment teams; business risk acceptance and formal technical/service approvals remain with the authorised decision-makers.

JOB DESCRIPTION | CHANGE & RELEASE MANAGEMENT

Orange Restricted

4. Required Knowledge, Skills and Competencies Competency Expected level / evidence

ITIL & service management

Strong practical knowledge of ITIL 4 Change Enablement and related release, deployment, incident, problem and configuration practices.

Change & release control

Hands-on expertise in risk-based change assessment, CAB/eCAB, integrated scheduling, release plans, readiness gates, rollback and PIR.

Planning & analysis

Strong dependency, resource and schedule management; analytical thinking, risk judgement, root-cause facilitation and attention to detail.

Stakeholder leadership

Confident customer-facing facilitation across senior stakeholders, technical teams, suppliers and multi-service delivery groups.

Communication

Clear, concise written and verbal communication; able to explain technical risk and business/service impact to varied audiences.

Behavioural strengths

Accountability, results orientation, collaboration, constructive challenge, adaptability, prioritisation and continual improvement.

Tools

Experience with ITSM/change platforms, reporting dashboards, collaboration tools and project/release planning tools.

5. Education, Certifications and Experience Requirement Profile

Education

Bachelor’s degree in Telecommunications, IT, Computer Science, Engineering or equivalent may be considered.

Experience

Typically 8–12 years in IT/telecommunications operations, service delivery or service management, including customer-facing change governance.

Required / preferred

ITIL 4 Foundation required or strongly preferred. SIAM, project/release management (e.g., PMP/PRINCE2) and relevant technical certification (e.g., CCNA for network-heavy scope) are advantageous.

Relevant exposure

CAB/eCAB, failed-change/incident coordination, risk assessment, production deployments/upgrades, release planning, customer communication and service governance.

6. Why Become a Change Manager?

The Change Manager role offers a unique opportunity to work at the intersection of technology, business and service delivery. It provides end-to-end ownership of complex changes, direct engagement with customers and senior stakeholders, and the opportunity to drive service stability, operational excellence and business outcomes.

The role builds strong capabilities in leadership, risk management, stakeholder engagement and project management, while fostering a high degree of accountability and decision-making.

7. Career Growth Opportunities

The experience gained as a Change Manager creates a strong foundation for progression into diverse leadership and specialist roles, including:

Project / Programme Management – leading complex initiatives and end-to-end delivery.

Release Management – driving integrated release planning, coordination and execution.

Service Delivery & Operations Leadership – managing service performance and customer outcomes.

Technical Consulting – leveraging cross-functional expertise to deliver technology solutions.

Transversal & Governance Roles – progressing into service management, process excellence, risk and compliance, or other cross-functional leadership positions.

The role offers a valuable pathway to broaden professional expertise, strengthen leadership capabilities and advance into wider business and technology responsibilities.