Hardware Systems Engineer, VOS

Applied Intuition•Sunnyvale, CA

2d•$130,000 - $220,000•Onsite

About The Position

Applied Intuition is seeking a Hardware Systems Engineer with strong robotics and software expertise to take ownership of system-, hardware-, and electrical/electronics (EE)-level requirements for a new, strategically important product. This role involves decomposing vehicle-level requirements into clear, testable system and hardware requirements, and defining the EE systems for validation test benches and rigs. It is a requirements- and architecture-focused position, not a hands-on hardware development role. The engineer will define what the hardware and test infrastructure must do, own requirements and architecture in a model-based environment, and establish foundational processes, tooling, and traceability (ASPICE, Polarion, Cameo) for the program.

Requirements

3+ years of systems or hardware systems engineering experience covering requirements, functional decomposition and allocation, analysis, and verification.
BS/MS in Electrical Engineering, Computer Engineering, or a related field.
Experience deriving and allocating requirements from higher-level (e.g., vehicle-level) requirements.
Working understanding of EE systems - power, wiring and harnessing, signal interfaces, instrumentation, and DAQ - sufficient to define test benches and rigs.
Excellent written and verbal communication - able to move fluidly between deep technical detail and stakeholder-level clarity.
Note: this role does not involve hands-on hardware development (schematic capture, PCB layout, or board bring-up).

Nice To Haves

Familiarity with software safety analyses (SW-FTA, SW-FMEA) or software safety case development at the application or platform level — this is a strong differentiator for this role
Familiarity with software tool classification and qualification activities per ISO 26262 Part 8
Experience across multiple vehicle domains — ADAS or propulsion or chassis, or body electronics — with an understanding of domain-specific safety challenges
Exposure to ASPICE (Automotive SPICE) software process assessments alongside ISO 26262
Experience working with third-party assessors through product assessment or audit cycles

Responsibilities

Decompose and allocate vehicle-level requirements into system-, hardware-, and EE-level requirements; define system bounds, capabilities, and functional features.
Convert customer needs and autonomy/Vehicle OS use cases into system and hardware requirements and operational objectives for the system as a whole.
Ensure the built system meets its intended requirements, and keep requirements current as vehicle-level requirements evolve.
Define the electrical and electronics (EE) architecture for the test benches and rigs used to validate the product, including hardware-in-the-loop (HIL) rigs and bench setups.
Specify power distribution, wiring and harnessing, signal interfaces, instrumentation, data acquisition (DAQ), sensor/actuator emulation, and safety interlocks for benches and rigs.
Capture bench and rig requirements and interfaces, and partner with the teams that build and maintain them so the infrastructure delivers the coverage needed to verify system and software requirements.
Use Cameo (MBSE/SysML) to build, maintain, and analyze the functional and logical architecture, and define variant management for Vehicle OS products.
Own validation and verification of requirements at both the system and hardware level.
Maintain end-to-end traceability across user journeys, features, system requirements, subsystem/hardware/EE requirements, bench and rig definitions, and test cases - across the full toolchain.
Define processes for ASPICE Level 2 compliance, partner with the QA team to meet industry standards (e.g., ISO 26262 functional safety), and configure Polarion (requirements management) and Cameo (architecture management) for compliant industry processes.
Work daily with hardware, embedded, perception, and autonomy software teams, providing requirements guidance so the delivered design stays as close as possible to the intended design.
Coordinate with test, validation, and lab teams to align bench and rig capability with the program's verification needs.