Environment Release Manager

Role: Environment/Release Manager

Location: Minneapolis, MN (Onsite)

Fulltime Permanent

Job Description

Must Have Technical/Functional Skills

Release and deployment management

Integrated cutover planning

CAB and change governance

Environment and dependency coordination

Microsoft Project

Azure DevOps and Jira

ServiceNow Change Management

CI/CD concepts and Jenkins/Git

Readiness dashboards and reporting

Hypercare and service transition

Roles & Responsibilities

Owns integrated environment and release planning across applications and vendors, with accountability for release calendars, deployment sequencing, change approvals, cutover orchestration, readiness decisions, command-center execution, and post-release stabilization. Unlike the Environment Manager, this role is primarily release- and project-governance focused

Define the release strategy, release trains, governance forums, calendars, quality gates, approval model, and deployment standards.

Build integrated release plans covering SAP IS-U, CDG, MDM, IEE, Salesforce, GIS, mobile, integration, reporting, and third-party systems.

Coordinate deployment sequencing, code/configuration/data dependencies, environment windows, test completion, change freezes, certificates, and infrastructure prerequisites.

Lead release-readiness reviews and confirm designs, testing, approvals, security, rollback, monitoring, support, and business readiness.

Prepare and govern change requests, CAB submissions, implementation plans, validation steps, rollback plans, and audit evidence.

Develop integrated cutover runbooks, minute-by-minute schedules, ownership, checkpoints, communications, and command-center protocols.

Manage release RAID, critical path, vendor commitments, milestone forecast, resource needs, and executive escalation.

Coordinate dress rehearsals, defect drops, emergency fixes, production deployments, smoke testing, and business validation.

Track hypercare incidents, failed transactions, technical health, backout criteria, stabilization actions, and transition to support.

Conduct post-implementation reviews and improve release metrics, controls, automation, and reusable procedures.