The Role:
The Sub-System Lead Engineer (SSLE) is a highly skilled individual contributor who owns work across the full vehicle development lifecycle—from requirements definition and design through implementation, testing, validation, and issue resolution. You will apply strong systems thinking and collaborate closely with system engineers, software developers, test engineers, and cross-functional partners to deliver innovative features for General Motors’ next-generation vehicles. Experience with Agile development, software design and release, requirements management, embedded controls, and calibration is preferred. We’re looking for someone with the drive, curiosity, and tenacity to grow both technically and professionally while working on some of GM’s most exciting technologies.
What You’ll do:
- Create and maintain Sub-System Technical Specifications (SSTS) and other requirements (Component Technical Requirements Specifications-CTRS, serial data, diagnostics, U-services, etc.) for exterior lighting software solutions using requirements management software (e.g. DOORS Next Gen, DOORS)
- Create and maintain Behavior Technical Specifications (BTS) for exterior lighting software solutions, following Behavior Driven Development (BDD) principles. This includes leading triad meetings and discussions with key stakeholders
- Develop and maintain blueprints and/or functional block diagrams
- Design and Sustain Model Based Systems Engineering (MBSE) diagrams (e.g. Block Definition Diagram, Use-case Diagram, Activity Diagram, Internal Block Diagram) using Rhapsody
- Establish and Uphold Subsystem/Solution Failure Mode and Effect Analysis (FMEAs) using the FMEA Integration Tool (FIT). Support the development and linking of Software Component FMEAs, Process FMEAs, and system FMEAs, when appropriate, by providing context of software related failure modes and contributions, with a focus on high severity items.
- Collaborate cross-functionally with other SSLEs to ensure robust integration of subsystems/solutions, including failure mode discussions for interfaces between your subsystem/solutions to other subsystems/solutions
- Create and update Calibration Bill of Materials (CalBOM) template for calibrations
- Collaborate with Controls and Software Engineers to review controls design and/or software implementation, providing guidance to ensure compliance with requirements
- Support definition and implementation of Testable Functionality Roll-Out Plan (TFRP)
- Collaborate with Validation Engineers to support the creation of testable scenarios to ensure intent of BTS requirements is met with a robust test plan
- Support the root cause analysis for applicable sub-system related issues and translate resolutions into new or revised requirements, as appropriate
- Support the development of requirements related to OBD regulations or calibrations, as applicable
- Support the development and tagging of safety requirements, based on rolldown from systems/systems safety, and regulatory requirements
- Operate in agile development of software-related requirements as a key participant and stakeholder in scrum meetings and ART ceremonies (e.g. Daily Stand-Up, Iteration Planning, Iteration Review, and Program Increment Planning, etc.)
- Create and maintain Features and Stories to manage requirements and specifications of sub-systems using change management tool (e.g. Jira) and complete stories by agreed timing
- Review Owner’s Manual and Service information related to the applicable sub-system to ensure alignment with intended sub-system operation, if applicable
- Provide guidance to support COSIM environment development
- Provide guidance and input for feature design verification plan by working with System and/or Feature Owners and Validation Engineers
- Support advanced technical work projects that drive future features and vehicle enhancements
Your Skills & Abilities (Required Qualifications)
- Bachelor’s Degree in Systems/Mechatronic/Mechanical/Controls/Electrical/Software or related engineering discipline
- Technical Writing
- Signal Mapping
- Software FMEA
- Minimum of 6+ years of relevant experience
- Experience related to mechatronic systems or subsystems
- Basic knowledge of controls theory and the software development process
- Strong analytical problem-solving skills, including independent judgment and decision-making skills, where problems are very unusual and extremely difficult
- Demonstrated communication and interpersonal skills required to build relationships with team members and customers to solve problems and resolve issues
- Physics-based understanding of the Voice-of-Customer (VOC), and Critical to Quality (CTQ) requirements.
- Ability to effectively communicate issues, status and recommendations to leadership
- Proven ability in project management skills, strong attention to details, and ability to teach others
- Ability to prioritize work with limited direction
What Will Give You A Competitive Edge (Preferred Skills)
- Masters or PhD in Engineering with an emphasis on Systems, Mechatronics, software or Controls
- Experience with writing, interpreting or managing requirements
- Experience in the vehicle exterior lighting technical domain
- Experience with calibration, software, and controls development
- Experience with requirements management tools (e.g., DNG, DOORS, etc.)
- Experience with Behavior Driven Development (BDD), Test-Driven Development (TDD), Gherkin syntax
- Experience with Model Based Systems Engineering and associated tools (e.g. Rhapsody)
- Knowledge of risk-assessment tools, such as Failure Mode and Effects Analysis (FMEA)
- Experience leveraging simulation environments and plant modeling for testing or requirements generation (e.g., Matlab/Simulink, CarSim, GT-Power, D-Space, ETAS, etc.)
- Experience with work management tools such as JIRA/JIRA Align, Azure, IBM Rational Team Concert, etc.
- Experience with Agile methodologies
- Experience with automotive regulations or safety critical systems
- Experience with automotive electrical architectures and/or software defined vehicles
- Familiarity with vehicle network communication protocols and tools such as CAN, LIN, and SPI
- Hardware I/O level controller knowledge
