SAFe Release Train Engineer

About the role

The Digital Sector at Leidos currently has an opening for a SAFe Release Train Engineer (RTE) to work in our Baltimore, Maryland office. This is an exciting opportunity to use your experience helping the Center for Medicare and Medicaid Services (CMS) modernize and transform its legacy Contact Center CRM platform. Original posting: September 24, 2026.

Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025.

Responsibilities

• Facilitate execution of the Agile Release Train (ART), including Program Increment (PI) planning, two-week sprint/iteration planning, sprint reviews, and retrospectives across all CCCS delivery teams.
• Collaborate with the Program Manager, Solution Architect, and Product Manager to ensure alignment of technical strategy, business strategy, and execution across the modernization roadmap.
• Maintain and continuously groom the prioritized, CMS-visible product backlog, ensuring Definition of Done (development complete, unit tested, integrated, security scanned, COR-reviewed) compliance for all user stories.
• Facilitate CMS Go/No-Go Gate reviews at each phase boundary, coordinating approval of the PoC acceptance, UAT results, SLA compliance, and production deployment readiness.
• Coordinate the iterative AI Feature Roadmap, ensuring AI-driven capabilities are delivered incrementally, validated with real users, and refined based on feedback consistent with Agile principles.
• Identify, track, and drive resolution of cross-team dependencies and risks across CRM modernization, data migration, system integration, and AI workstreams; communicate impediments and resolutions, as needed.
• Champion continuous integration/continuous delivery (CI/CD) pipeline adoption and consistent quality practices across all scrum teams.
• Facilitate sprint reviews with CMS stakeholders to demonstrate working software, including case management, knowledge integration, AI features, and external system integrations.
• Maintain Agile project management tooling (e.g., Jira, or CMS-approved equivalent) to provide CMS with continuous, read-access visibility into the program backlog.
• Coordinate release and increment planning across the phased delivery approach.
• Support technical program deliverables including documentation are updated each release/sprint cycle