Staff Systems Engineer, Embedded Safety & Architecture

Job description

Job responsibilities

• Partner with the systems and safety group. Take the vehicle-level safety concept, safety goals, and functional safety requirements as your inputs, and feed embedded expertise back into their hazard analysis and concept…
• Own the embedded technical safety concept. Derive technical safety requirements from the functional safety concept allocated to the embedded system, and allocate each to the right architectural element.
• Architect across hardware and software. Define the embedded system architecture and the hardware/software partition, including the hardware-software interface (HSI), so both groups design against one coherent picture.
• Manage requirements and traceability. Maintain bidirectional traceability from the safety goals handed down to you all the way to hardware and software requirements, and keep the work products that feed the safety case.
• Steward automotive standards for the embedded org. Stay current on the standards that apply to our work — functional safety, SOTIF, cybersecurity, autonomous-product safety, process and component qualification — and…
• Set up the right side of the V. Your requirements and architecture define what verification and validation later prove.

Job requirements

• BS/MS in Electrical Engineering, Computer Engineering, Systems Engineering, or a related field — or equivalent hands-on experience.
• 8+ years in embedded systems, with real depth spanning both hardware and software.
• Strong ISO 26262 experience concentrated on the system-design phase (Part 4) and its handoffs to hardware (Part 5) and software (Part 6): deriving technical safety requirements from a functional safety concept, system…
• Working familiarity with the broader automotive standards landscape — and the judgment to operationalize it — including SOTIF (ISO 21448), automotive cybersecurity (ISO/SAE 21434), autonomous-product safety cases (UL…
• Fluency with requirements management and traceability — you've lived in a tool like Polarion and know why traceability matters when the safety case is questioned.
• Enough range to read a schematic and reason about embedded C/C++/Rust, so your hardware/software partitioning is grounded in what each side can actually implement.
• A clear grasp of the full V, so the left-side work you produce genuinely sets the right side up to succeed.