Sr. Software Solution Lead Engineer

General Motors•Milford, MI

8d•Hybrid

About The Position

The Senior Software Solution Lead Engineer (SSLE) on the LVI (Low Voltage Infrastructure) Team develops advanced and critical features for GM's electric, internal combustion, and autonomous vehicles. The software defined will power the vehicle and create a stable host environment for devices and controllers. The SSLE is a dynamic individual contributor with recognized expertise, responsible for requirements and associated work throughout the entire vehicle development lifecycle, including requirements definition, design and implementation, testing, and problem resolution. This role involves close collaboration with multi-functional stakeholders (system engineers, software developers, testers, etc.) to support innovative technology development. Some travel may be required, primarily to Michigan/Ontario and other locations in the US and Canada.

Requirements

Bachelor’s Degree in Engineering (Systems/Mechatronic/Controls/Electrical/ Software/Mechanical) or related discipline.
Minimum of 6+ years of relevant experience.
Experience related to mechatronic systems or subsystems.
Basic knowledge of controls theory and the software development process.
Physics-based understanding of the Voice-of-Customer.
Must be legally allowed to work in US and able to travel to Canada.
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.
Ability to effectively communicate issues, status and recommendations to leadership.
Proven ability in project management skills and ability to teach others.
Ability to prioritize work with limited direction.

Nice To Haves

Masters degree (or higher) in Engineering with an emphasis on Systems, Mechatronics, or Controls.
Experience and background in power distribution, vehicle electrical systems, controller networks.
Experience with writing, interpreting or managing requirements.
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 with calibration, software, or software/controls development.
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 OBD regulations requirements.
Experience with safety critical systems.
Experience with automotive electrical architectures and/or software defined vehicles.
Familiarity with vehicle network communication protocols and tools such as Ethernet, CAN, LIN, and SPI.
Hardware I/O level controller knowledge.

Responsibilities

Create and maintain Behavior Technical Specifications (BTS) for applicable software solutions, following Behavior Driven Development (BDD) principles, including leading triad meetings and discussions with key stakeholders.
Create and maintain Sub-System Technical Specifications (SSTS) and other requirements (Component Technical Requirements Specifications-CTRS, serial data, diagnostics, U-services, etc.) for applicable subsystems and ART software solutions using requirements management software (e.g. DOORS Next Gen, DOORS).
Develop and maintain blueprints and/or functional block diagrams for assigned software solutions.
Design and Sustain Model Based Systems Engineering (MBSE) diagrams or GUI (e.g. Block Definition Diagram, Use-case Diagram, Activity Diagram, Internal Block Diagram) for responsible software solutions 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 subsystem operation, if applicable.
Provide guidance to support virtual CoSIM environment development.