Key Notes
Vehicle-integration architecture sits between Wayve’s AI Driver and OEM or Tier 1 platforms, covering sensors, signals, middleware, ECU constraints, timing, diagnostics, safety assumptions and validation. Applicants need ADAS or embedded architecture experience, clear boundary and interface definition, vehicle electronics knowledge, automotive protocols and OEM integration. The position is full time and hybrid in London with core working hours.
What You'll Work On
- Define customer vehicle-integration architecture between Wayve software and OEM or Tier 1 sensors, signals, middleware and ECU environments.
- Convert product and customer discussions into technical specifications, interface contracts, ownership boundaries, assumptions, dependencies and open decisions.
- Coordinate Software Architecture and Validation teams on feasibility, integration tests and verifiable customer-programme requirements.
- Maintain integration guides, architecture diagrams and decision records while identifying partner deliverables, technical gaps and programme risks.
Why This Role Matters
- OEM vehicle-integration programmes depend on explicit interfaces and ownership boundaries so Wayve software and partner systems are not built against conflicting assumptions.
- Wayve’s core AI Driver architecture remains reusable when customer-specific sensors, middleware and ECU constraints are translated into bounded integration decisions rather than product fragmentation.
What They Are Looking For
- Experience: ADAS, autonomous-driving, embedded-software or vehicle-system architecture experience, especially at the software–vehicle interface, is required.
- Technical: Defining ownership models, assumptions, dependencies and interface contracts is required.
- Domain: Vehicle electronics, ECU integration, real-time execution, timing, diagnostics and production software knowledge is required.
- Technical: Knowledge of automotive protocols or architectures such as CAN, FlexRay, Automotive Ethernet, SOME/IP, AUTOSAR or equivalents is required.
- Stakeholder: OEM/Tier 1 integration experience, validation-ready specifications and multidisciplinary engineering collaboration are required.
- Preferred: A relevant bachelor’s or master’s degree, Tier 1 experience, generative AI, end-to-end autonomy, embedded middleware or sensor-integration experience is desirable.