Release Train Engineer

ERCOT

Taylor, TX

Full Time

Posted September 23, 2026

$120k - $165k

Grid Infrastructure

Apply Now

Application opens on company website

Listing evidence and provenance

Source: Workday View original listing
Freshness: Open in the current public read path; this is not an employer guarantee.Last observed October 5, 2026
Classification: Modern power-system classification not yet published for this listing.Legacy source industry field: Grid Infrastructure
Pay provenance: Employer-provided pay

Job Description

Facilitate product release planning and governs the end-to-end release lifecycle across ERCOT applications, AI, and data platform portfolio.

Key Responsibilities

Applies knowledge of release planning, change management, and delivery governance principles to facilitate structured, compliant, and predictable software releases across ERCOT's application and data platform portfolio.
Follows established release management processes and procedures to coordinate deployment activities across Agile sprint, waterfall, and hybrid delivery teams; ensures cross-functional alignment on release scope, schedule, and readiness.
Creates, reviews, and manages IT change records in ServiceNow in accordance with ERCOT change management standards; coordinates Change Advisory Board activities and ensures all releases meet NERC CIP change governance requirements prior to production promotion.
Maintains the production release calendar and facilitates release planning meetings, backlog grooming sessions, and deployment readiness reviews to ensure consistent, predictable release cadence across all delivery tracks.
Contributes to the generation and distribution of release metrics, status reports, and delivery dashboards supporting program-level visibility and continuous improvement of the release management function.
Hybrid Delivery Coordination — Coordinate release planning and deployment sequencing across teams operating under Agile, waterfall, and hybrid delivery methodologies; synchronize cross-team releases when shared dependencies exist.
Program-Level Release Governance — Enforce release readiness criteria before each deployment window; validate test completion evidence, environment stability, stakeholder approvals, and CAB authorization; serve as program-level production gate keeper.
NERC CIP & ITSM Change Governance — Ensure all releases comply with NERC CIP change management requirements; coordinate with the CAB, enforce change classification standards, and maintain complete audit trails for all production promotions.
Emergency & Expedited Change Coordination — Facilitate emergency and expedited change management processes; coordinate expedited CAB review, risk assessment documentation, stakeholder notification, and post-implementation review.
IT & Change Metrics Reporting — Track and report IT change metrics including change volume by type, change success rate, unauthorized change incidents, CAB throughput, change-to-incident correlation, and SLA compliance; publish via ServiceNow and Power BI.
SDLC Metrics & Delivery Throughput Analysis — Measure program-level SDLC metrics including throughput, cycle time, lead time, WIP load, and bottleneck patterns; publish actionable insights to delivery leadership.
Release Health Dashboards — Design and maintain executive-facing dashboards in Power BI reflecting deployment status, release calendar adherence, milestone completion rates, change success rates, and DORA metric trends.
Dependency & Risk Register Management — Maintain a product dependency map and risk register; facilitate cross-team dependency resolution and ensure all risks are visible, owned, and actively mitigated.
Continuous Improvement Leadership — Lead retrospectives and release planning improvement sessions; identify and drive elimination of waste, handoff delays, and approval bottlenecks; track improvement items to completion.
Waterfall Phase Gate & Milestone Governance — Coordinate formal waterfall phase gate reviews; ensure gate entry/exit criteria are met, required artifacts are complete, and stakeholder sign-offs are documented and archived