Staff Systems Engineer - Low Voltage Vehicle Systems

General MotorsWarren, MI
4dHybrid

About The Position

We are seeking a Staff Systems Engineer to join the Vehicle Systems Engineering organization, focused on Low Voltage (LV) vehicle systems, supporting the new Software-Defined Vehicle (SDV) architecture and 12V system design thinking across the vehicle. This role operates in a highly complex technical space with significant cross-domain dependencies spanning software, hardware, electrical architecture, validation, and virtual environments. The ideal candidate is comfortable working in ambiguous problem spaces, can navigate evolving requirements, and is able to establish themselves as a technical leader by driving clarity, alignment, and robust system solutions. You will translate high-level product intent into scalable, testable system architectures using Model-Based Systems Engineering (MBSE), while influencing technical direction across programs and organizations, including helping shape and influence future SDV and Low Voltage (LV) architecture direction. What You’ll Do: Lead system-level architecture, definition, and integration of Low Voltage vehicle systems using MBSE. Decompose product and program intent into system models, functional architectures, and testable software and hardware requirements. Develop and maintain system blueprints, including functional decomposition, logical architectures, interface definitions, requirements, allocations, and FMEAs. Own and evolve MBSE artifacts, such as functional models, use-case, activity, sequence, and context diagrams. Allocate and partition system functionality across multiple implementation teams, supporting architectural trade studies and optimization. Define and maintain co-simulation and virtual validation strategies, including simulation architectures and acceptance criteria. Work closely with software, hardware, validation, electrical architecture, and platform teams to manage complex interdependencies and integration risks. Support system integration, calibration, validation, and issue resolution, including root cause analysis across domains. Ensure system designs meet safety, regulatory, quality, and performance requirements, supporting certification and approvals. Drive continuous improvement in MBSE adoption, modeling quality, and virtual validation capability. Clearly document technical decisions, trade-offs, and deliverables across the product lifecycle.

Requirements

  • Bachelor's degree in engineering (Systems, Electrical, Software, Mechanical, or related field).
  • 7+ years of experience in systems engineering or software-intensive automotive development.
  • Strong expertise in systems architecture, MBSE, requirements development, integration, and validation.
  • Solid background in model-based development and virtual simulation.
  • Experience defining and managing system interfaces, performance targets, and validation/testing strategies.
  • Proficiency with MBSE and requirements tools (e.g., Rhapsody, DOORS / DOORS Next).
  • Demonstrated ability to operate effectively in ambiguous problem spaces and drive clarity.
  • Proven track record of technical leadership, influence, and cross-organizational collaboration.
  • Strong prioritization, execution, and stakeholder management skills.
  • Excellent written and verbal communication skills.

Nice To Haves

  • Master’s degree in engineering or related field.
  • Advanced experience with MBSE, including Rhapsody modeling (activity, use-case, sequence, context).
  • Familiarity with Agile / SAFe development methodologies.
  • Understanding of service-oriented architectures (SOA).
  • Knowledge of CI/CD and continuous testing in software-intensive systems.
  • Experience working in highly interdependent system architectures with multiple stakeholders.
  • Exposure to reliability engineering, functional safety, and regulatory compliance.

Responsibilities

  • System architecture definition and modeling using MBSE
  • Functional decomposition and end-to-end requirement traceability
  • Managing change, dependencies, and architectural allocation using system models
  • Co-simulation strategy and system-level validation planning
  • Definition of acceptance criteria and “definition of done” for system deliverables
  • Providing technical leadership in complex, cross-functional environments, fitting well with technical expectations for system integration, fault strategy ownership, and architectural influence
© 2024 Teal Labs, Inc
Privacy PolicyTerms of Service