Production Management Support

We made history and now we work to transform the future – for our customers, our communities and our families. You'll see your work on the road every day, helping people move freely and pursue their dreams. At Ford, you can build more than vehicles. Come build what matters.

Enterprise Technology plays a critical part in shaping the future of mobility. If you’re looking for the chance to leverage advanced technology to redefine the transportation landscape, enhance the customer experience and improve people’s lives, this is the opportunity for you. Join us and challenge your IT expertise and analytical skills to help create vehicles that are as smart as you are.

• In this position...
  This role is for an Enterprise Release Manager within the Ford Credit Command Center.

• The Command Center mission is to help maintain a stable production environment through effective change, incident, and problem management. 

• Enterprise Release Management (ERM) is a Ford Credit enterprise-wide IT best practice designed to synchronize changes to “core” and "non-core" applications.

• ERM manages interdependent applications as a synchronized set to improve quality, efficiency, and reduce production implementation costs.

• In this role, you will provide essential leadership to our release coordination efforts while playing a key part in the smooth operation of our core IT Service Management (ITSM) processes, specifically Incident, Change, and Problem Management.

• A critical component of this position involves modernizing our release processes by minimizing developer friction through automation, establishing clear quality gates, driving a predictable "release train" cadence, and utilizing DORA metrics to track and improve launch behavior.

• This is a fantastic opportunity for someone who enjoys supporting multiple highly synchronized initiatives, working with modern DevOps tools, and contributing to both release success and operational stability within a global IT environment.

What you'll do...

• Minimize Friction & Automate Data Collection: 

  • Meet developers where they work.

  • Integrate ERM tooling (e.g., ServiceNow, Jira Align, ADO) directly with CI/CD pipelines and backlog tools. 

  • Use "Release Tags" in Jira/ADO to flag dependencies and automate status updates (e.g., auto-updating release plans when pull requests merge or QA deployments succeed).

• Define & Enforce Quality Gates: 

  • Establish and monitor a lightweight but firm governance framework. 

  • Define and enforce a "Definition of Ready for Release" (DoR) at key milestones (e.g., T-Minus 10 days for cross-team dependency sign-offs, T-Minus 5 days for regression testing/vulnerability checks, T-Minus 2 days for verified rollback plans). 

  • Ensure gates are objective and binary (Pass/Fail) using automated checks (e.g., SonarQube, automated test pass rates).

• Establish a "Release Train" Cadence: 

  • Publish and maintain a 12-Month Release Calendar locking in major release dates, code freeze windows, and maintenance windows. 

  • Run short, highly focused "Scrum of Scrums" or Release Readiness Syncs (15–20 minutes) to resolve cross-team dependencies and environment conflicts. 

  • Enforce a "Train Leaves on Time" policy where lagging features that miss critical gates are decoupled and pushed to the next release.

• Provide Immediate Value to Teams: 

  • Coordinate staging and test environments to act as a "traffic cop" and resolve contention. 

  • Automate the generation of release documentation, CAB (Change Advisory Board) approvals, and audit logging to shield developers from corporate bureaucracy. 

  • Work to eliminate deployment weekend chaos, turning long troubleshooting sessions into quiet, non-event deployments.

• Measure & Gamify with DORA Metrics: 

  • Track and publish key performance indicators, inclu