> Markdown version of [/jobs/ext/2706424-systems-engineer](https://www.wearedevelopers.com/jobs/ext/2706424-systems-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Systems Engineer - **Company:** WAABI PARTNERS - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Salary:** $160,000.0 - $260,000.0 - **Contract:** Permanent contract - **Skills:** Systems Engineering, C++ (Programming Language), Computer Engineering, Firmware, ISO/IEC 15504, Requirements Management, Software Requirements Analysis, Verification and Validation (Software), Systems Modeling Language, Test Execution Engine - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/staff-systems-engineer-embedded-safety-architecture-waabi-9728836 ## About the Role * 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 architectural design, and hardware/software allocation. * 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 4600), Automotive SPICE (ASPICE), and component/coding standards such as AEC-Q10. * 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., * Experience standing up or maturing a standard (ASPICE, 21434, or similar) inside an engineering org, not just complying with one. * SysML or model-based systems engineering. * AV, ADAS, or other complex safety-critical domain experience. * Direct experience authoring or negotiating DIAs with an OEM. ## Description * 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 work. You're the bridge between their concept and our hardware and firmware. * 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 fold them into how the embedded team designs, documents, and works day to day. * Set up the right side of the V. Your requirements and architecture define what verification and validation later prove. You'll partner closely with the V&V effort - and support Development Interface Agreements (DIAs) with OEM partners and suppliers - without owning the downstream test execution yourself. ## Related Videos - [Model Based Systems Engineering in an Agile Product Development Process](https://www.wearedevelopers.com/videos/68-model-based-systems-engineering-in-an-agile-product-development-process) - [Playing Pong on a shoulder press machine](https://www.wearedevelopers.com/videos/100140-playing-pong-on-a-shoulder-press-machine) - [Automated Driving - Why is it so hard to introduce](https://www.wearedevelopers.com/videos/628-automated-driving-why-is-it-so-hard-to-introduce) - [Agile work at CARIAD – Creating a customer web application for controlling the vehicle ](https://www.wearedevelopers.com/videos/200-agile-work-at-cariad-creating-a-customer-web-application-for-controlling-the-vehicle) - [Agent Smith Gets Hardware: Autonomous IoT Hacking From Debug Port to Cloud API](https://www.wearedevelopers.com/videos/100258-agent-smith-gets-hardware-autonomous-iot-hacking-from-debug-port-to-cloud-api) - [Building a hypercar from scratch](https://www.wearedevelopers.com/videos/607-building-a-hypercar-from-scratch) ## Related Articles - [How software is steering vehicle technology](https://www.wearedevelopers.com/magazine/515-how-software-is-steering-vehicle-technology) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [Software Engineer Career: Things You Should Know](https://www.wearedevelopers.com/magazine/143-software-engineer-career-things-you-should-know) - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer)