Release Train Engineer

Responsibilities

• Guides and coaches leaders, teams, and Scrum Masters in the Agile Release Train on Agile practices and develops their understanding of Agile principles
• Executes program increment session for release train and facilitates Agile release train ceremonies
• Provides status updates regarding Agile Release Train plans, delivery, timelines, and impediments to stakeholders and leadership while communicating within the Agile Release Train to support delivery against program commitments
• Manages risk including dependency management, impediment removal, and compliance with Enterprise Change Management and other policy requirements
• Makes measurements of Agile Release Train delivery, maturity, and performance and reviews the metrics with the Agile Release Train to identify improvement opportunities
• Collaborates with the product management team and ensures the program has a healthy product and program backlog
• Defines norms and agreements for the Agile Release Train and enforces the agreements
• Facilitates PI Planning end-to-end: Business Context → Vision/Roadmap → Architecture Vision/Practices → Planning Context → Team Breakouts → Draft/Final Plan Review → ROAM Risks → Confidence Vote → Planning Retro
• Drives presenter readiness, timeboxing, parking lot capture, and decision visibility; keeps the event collaborative and energized
• Facilitates train-level routines as needed (Scrum of Scrums, PO Sync, PDT Sync, System Demo, Inspect Adapt/Retro)
• Tracks and radiates PI health: PI Objectives completion (Committed vs Completed), Business Value delivered, cycle time, velocity trend (if applicable), defect density, dependency management, and risk posture

Qualifications

• 7+ years of experience as a Release Train Engineer
• Primary focus: predictable, sustainable delivery of Technology Products via strong PI readiness, dependency/risk management, and high-signal reporting
• Continuous, sustainable delivery of business value to users through stable cadence and predictable execution
• PI Planning produces clear PI Objectives, visible dependencies, and ROAM’d risks with ownership that persists through the PI
• PICoordinate readiness across PM, POs, SMs, Architects, Tech Management, Release Mgmt; confirm Business Owner/executive participation
• Facilitate PI Planning end-to-end: Business Context → Vision/Roadmap → Architecture Vision/Practices → Planning Context → Team Breakouts → Draft/Final Plan Review → ROAM Risks → Confidence Vote → Planning Retro
• Designs agenda to support time zones, defines breakout SPOCs, enforces working agreements, and ensures all outcomes are digitally captured and visible
• Facilitates train-level routines as needed (Scrum of Scrums, PO Sync, PDT Sync, System Demo, Inspect Adapt/Retro)
• Tracks and radiates PI health: PI Objectives completion (Committed vs Completed), Business Value delivered, cycle time, velocity trend (if applicable), defect density, dependency management, and risk posture