Program Engineering Manager – Software

Hybrid:

This means the successful candidate is expected to report to the Warren Technical Center, Warren MI or Milford Proving Grounds, Milford, MI three times per week, at minimum, or other frequency dictated by the business.

Job Description

Work Arrangement:

Hybrid:

This means the successful candidate is expected to report to the Warren Technical Center, Warren MI or Milford Proving Grounds, Milford, MI three times per week, at minimum, or other frequency dictated by the business.

Our Mission:

At General Motors, our product teams are redefining mobility. Through a human-centered design process, we create vehicles and experiences that are designed not just to be seen, but to be felt. We’re turning today’s impossible into tomorrow’s standard —from breakthrough hardware and battery systems to intuitive design, intelligent software, and next-generation safety and entertainment features.

Every day, our products move millions of people as we aim to make driving safer, smarter, and more connected, shaping the future of transportation on a global scale.

The Role:

The Software & Electronics Platform team is building the execution foundation for GM’s software-defined electric vehicles. We are looking for a Program Engineering Manager (PEM) to lead, define, and organize the physical assets that make persistent HIL, night regression, Co-Sim, CVF, and related validation environments effective for SDV2 and future platform architectures.

This role is accountable for making complex work executable. You will establish the asset strategy, portfolio, standards, ownership model, configuration baseline, capacity plan, and lifecycle approach required to support platform and vehicle-program commitments. You will work directly with the platform PEMs and APEMs to connect bench and lab readiness to integrated execution plans, milestone confidence, issue resolution, launch readiness, and recovery actions.

You will also work directly for and with the Chief Engineer, translating platform strategy into investment priorities, physical infrastructure decisions, cross-functional operating rhythms, and an enterprise-ready model for onboarding future programs. The successful candidate will be equally comfortable shaping strategy with senior leaders, solving complex technical and infrastructure problems, driving disciplined execution across engineering organizations, and turning a collection of benches and labs into a coherent persistent capability.

What You’ll Do:

Define the persistent HIL and physical-validation strategy

• Establish the current-state and future-state strategy for persistent HIL benches, night-regression environments, Co-Sim, CVF, and related physical validation assets.
• Define and align asset purpose, capability, ownership, location, users, capacity, availability, lifecycle, upgrade path, and retirement criteria with the physical asset build team and engineering leaders responsible for testing
• Build a prioritized physical-asset roadmap aligned to SDV2, vehicle-program timing, build events, launch needs, and future program onboarding.
• Identify common-platform capabilities, program-specific needs, capacity gaps, duplicated infrastructure, and obsolescence risks.

Partner with the PEM to drive integrated execution

• Work directly with the PEMs to integrate asset readiness into the platform execution plan.
• Translate physical infrastructure needs into accountable owners, dates, dependencies, decision points, readiness criteria, and recovery actions.
• Provide a single, decision-ready view of bench and lab readiness, open issues, configuration risks, capacity constraints, and milestone confidence.
• Drive asset-related issues across organizational and technical boundaries from ambiguity to ownership, decision, implementation, and verified closure.
• Represent asset readiness in PAPIR, Dev/Val, quality-readiness reviews, launch reviews, and other forums as appropriate.

Establish the SDV2 asset portfolio and onboarding model

• Define the persistent HIL and regression baseline for BT1, N1, T1, C1, and future programs.
• Align physical assets to platform features, ECUs, electrical and logical topology, interfaces, diagnostics, calibration, software releases, test assets, and vehicle-integration activities.
• Create a repeatable onboarding model so future programs can use common enterprise infrastructure and standards.
• Ensure asset readiness is visible through relevant GVDP, software-quality, vehicle-integration, and launch milestones.

Govern configuration, Bench BOM, and release integrity

• Establish and maintain the Bench BOM for persistent HIL and regression environments.
• Coordinate tech packages (eBoM), part numbers, required attributes,