Sr. Software Solution Lead Engineer
General Motors
- Location
- Milford, Michigan, United States of America
- Work model
- On-Site
- Level
- Senior
- H-1B history
- 267 approvals (FY2023)
- Posted
- 6h ago
Skills
About this role
Job Description
The Team: Do you have a desire to influence the future of electric power distribution on GM’s exciting new vehicles? Consider a role as a Senior Software Solution Lead Engineer (SSLE) on our LVI (Low Voltage Infrastructure) Team. An LVI Senior SSLE develops some of GM’s most advanced and critical features, which are used across our portfolio of electric, internal combustion and autonomous vehicles. The software you define will power the vehicle and create a stable host environment for our devices and controllers.
The Role
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. You will work closely 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. What You’ll Do (Responsibilities): Create and maintain Behavior Technical Specifications (BTS) for applicable software solutions, following Behavior Driven Development (BDD) principles. This includes 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