Sub-System Lead Engineer

General Motors•Milford, MI

2d•Hybrid

About The Position

The Sub-System Lead Engineer (SSLE) is responsible for leading the development, definition, and documentation of requirements for applicable sub-systems or Agile Release Train (ART) solutions. The role involves close collaboration with cross-functional teams, ensuring technical specifications are well-defined, system behavior is clearly documented, and compliance with requirements is maintained throughout the development lifecycle. As a technical domain expert and single point of contact, the SSLE provides guidance on system design, troubleshooting, and optimization and owns the development and delivery of solutions, driving cross-team and group efforts. This SSLE role focuses on ownership of the PTMA Arbitration Domain and System Behavior Technical Specifications (System BTS). The role is responsible for defining and maintaining system-level behavioral intent, arbitration logic, prioritization strategies, cross-domain coordination, and degraded/fault behavior for thermal management functions supporting cabin comfort and propulsion thermal objectives in electric vehicles.

Requirements

Bachelor’s degree in engineering (Mechanical, Electrical, Software, Systems, or related fields).
5+ years of professional experience in automotive systems, controls, software, or requirements engineering, including experience with thermal management, system behavior definition, or cross-domain integration in BEV applications.
Strong analytical and problem-solving skills, including the ability to make independent, high-impact decisions.
Experience with requirements engineering in automotive, aerospace, or related industries.
Knowledge of Behavior-Driven Development (BDD) and MBSE principles.
Familiarity with Jira for managing software-related requirements.
Ability to facilitate cross-functional collaboration and lead discussions with stakeholders.
Experience with Agile methodologies and SAFe practices.
Strong documentation and communication skills to support a distributed, cross-functional team environment.

Nice To Haves

Master’s degree or PhD in Engineering (Mechanical, Electrical, Software, Systems, or related fields).
8+ years of experience in thermal systems, controls, system integration, or model-based development, including use of simulation and plant models for testing, requirements generation, or behavior validation.(Matlab/Simulink, CarSim, dSPACE, ETAS, Star-CCM+, etc.).
2+ years of embedded software development experience.
Knowledge of serial data communication, diagnostics (RIDs/DIDs), and user services.
Hands-on experience with IBM Rhapsody and system modeling techniques.
Proficiency in DOORS/DNG for requirement management.
Familiarity with ISO 26262 (Functional Safety).
Demonstrated experience defining system behavior, arbitration logic, interface requirements, or mode-based behavior across multiple functions or engineering teams.
Demonstrated strong knowledge of classic control engineering and estimation algorithms.

Responsibilities

Create and maintain System Behavior Technical Specifications (System BTS) using Behavior-Driven Development (BDD) principles, ensuring customer impact, system intent, and cross-functional traceability are well understood.
Lead triad meetings with key stakeholders to ensure effective communication, timely decision-making, and continuous improvement throughout the development process.
Provide technical leadership and mentorship for PTMA system behavior, with particular focus on arbitration strategy, system integration, and behavioral consistency across domains.
Maintain interface requirements in DOORS/DNG and collaborate with Feature System Architects (FSAs), system engineers, and domain owners to ensure requirement structure, behavioral intent, and arbitration logic align with program objectives.
Define and maintain arbitration logic for competing against thermal demands, including prioritization rules, mode-based behavior, fault responses, and system-level coordination across affected domains.
Co-Owns system-level behavioral alignment between the Arbitration Domain, subsystem requirements, software implementation, and verification strategy.
Maintain technical communication with 3rd party suppliers for the Arbitration domain.
Participate in debugging and root causing issues observed in vehicle testing.
Create and maintain Solution FMEAs, Subsystem FMEAs, and AFMEAs (Algorithm) in the area of responsibility.
Support DFMEA and PFMEA development by collaborating with software and hardware teams to address failure modes.
Ensure awareness of hardware failures (Sev 9, 10) and their impact on arbitration behavior within the SSLE’s area of responsibility.