Principal System Architect

Wayve•Sunnyvale, CA
•Hybrid

About The Position

Wayve’s Product Architecture & Safety (PAS) team defines, governs and validates the system and product architecture of Wayve AI Driver across programs, providing OEMs and partners with a unified technical voice. The system architecture team works across assisted driving through L4 driver-out. This role owns end-to-end system architecture and supports deployment of Wayve AI Driver across L0–L4, with a near-term focus on L3 eyes-off and L4 driver-out. The scope begins with Robotaxi needs and may grow with the business. The role translates use cases, operational design domains (ODDs) and operational constraints into reusable product, system and integration architecture. It defines sensor and compute topology, vehicle interfaces, safety mechanisms, redundancy, fallback and minimal-risk manoeuvre assumptions in collaboration with safety engineering. It also covers on-board and off-board architecture for connectivity, remote assistance and operation, and fleet operations, including latency, availability and ownership across Wayve, OEMs and operators. The architect distinguishes core product changes from partner-specific integration so that deployment requirements reinforce a common architecture. This full-time position is based in Sunnyvale, US, or London, UK, with a hybrid working model. Travel to customer and partner sites is expected during integration phases. The role includes hands-on collaboration in vehicle workshops and labs.

Requirements

  • Strong experience in system architecture, systems engineering or solution architecture for ADAS/AD, robotics or complex safety-relevant embedded systems.
  • Broad understanding of system- and vehicle-level architecture, sensors, compute and hardware, embedded software, vehicle integration and safety.
  • Experience defining and owning product or integration architecture for complex, cross-functional systems end-to-end.
  • Ability to translate high-level product or deployment goals into concrete architectural requirements and trade-offs.
  • Experience working across multiple technical domains and aligning different engineering stakeholders.
  • Experience leading technical discussions with OEMs, Tier 1s or other external partners.
  • Working knowledge of ISO 26262 and ISO 21448 (SOTIF) and how they shape system architecture.
  • Strong written and verbal communication, including producing architecture documents others can build from.
  • Hands-on ability to support technical problem-solving, bring-up and integration trade-offs in practice.

Nice To Haves

  • Experience with L3 eyes-off, L4 or robotaxi systems, including fail-operational and redundancy concepts.
  • Experience with assisted driving (L0–L2+) functions and their system requirements.
  • Experience with AI- or ML-based driving systems and their deployment on embedded platforms.
  • Familiarity with automotive middleware, real-time operating systems, Linux and embedded platform integration.
  • Experience with vehicle connectivity, remote assistance, remote operation/teleoperation, fleet operations, HMI or other robotaxi application-layer integration.
  • Experience bridging internal product architecture and external customer integration.

Responsibilities

  • Own end-to-end system architecture, interface contracts, assumptions of use and decision records.
  • Lead technical discussions with OEMs, Tier 1s and partners, aligning internal architecture owners around a common direction.
  • Define ECU and sensor requirements.
  • Guide system engineers and support integration planning, bring-up, triage and system-level debugging on vehicles and HiL/ViL benches.
  • Translate use cases, ODDs and operational constraints into reusable product, system and integration architecture.
  • Define sensor and compute topology, vehicle interfaces, safety mechanisms, redundancy, fallback and minimal-risk manoeuvre assumptions with safety engineering.
  • Define on-board and off-board architecture for connectivity, remote assistance and operation, and fleet operations, including latency, availability and ownership across Wayve, OEMs and operators.
  • Distinguish core product changes from partner-specific integration so deployment needs strengthen one common architecture.

Benefits

  • Meaningful equity.
  • Relocation support and visa sponsorship where applicable.
  • Hybrid working and core hours.
  • Learning and development budgets, with support for training, conferences and growth.
  • Comprehensive benefits including health insurance, dental, enhanced maternity and paternity leave, retirement or pension where applicable, access to therapists, wellbeing partnerships and team socials.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service