Solutions Architect

Job description

Before the detail, here's the challenge you'd help us solve. We build the embodied intelligence that moves real vehicles safely, and the ecosystem a billion machines will run on in the future. Very few people in AI can say this. Every role here, whatever the team, plugs into that. Here’s what this particular role covers. The role We are looking for an experienced Solution Architect to support the integration of Wayve’s autonomous driving technology with automotive OEM vehicle platforms. In this role, you will work at the boundary between Wayve’s core AI Driver architecture and OEM / Tier 1 vehicle systems. You will help define how Wayve software interfaces with vehicle platforms, including sensors, vehicle signals, middleware, ECU constraints, timing, diagnostics, safety assumptions, data logging, and validation. The ideal candidate can translate product and customer needs into clear technical specifications, understand both high-level system architecture and implementation details, and help ensure that Wayve’s solution integrates safely, efficiently, and consistently across customer programs. You will be expected to work independently within your scope, handle ambiguous technical problems, identify dependencies and risks, and keep stakeholders aligned. Key responsibilities: - Define and manage the technical architecture for customer vehicle integration, focusing on the interface between Wayve software and OEM / Tier 1 vehicle systems. - Collaborate with Product Management to translate product requirements and customer program needs into actionable technical specifications. - Define and document integration boundaries with OEMs and Tier 1 suppliers, including what is Wayve-owned, partner-owned, jointly defined, or out of scope. - Translate ambiguous customer or partner discussions into explicit ownership boundaries, interface contracts, assumptions, dependencies, and open technical decisions. - Work closely with Software Architects to assess technical feasibility and ensure customer program integration needs are aligned with Wayve’s core architecture. - Coordinate with Validation Engineers to define integration test requirements and ensure customer program requirements are verifiable. - Develop and maintain program-facing technical documentation, including interface specifications, integration guides, ownership boundary definitions, architecture diagrams, and decision records. - Support customer program planning by identifying integration complexity, dependencies, technical gaps, technical risks, and required partner deliverables. - Participate in OEM and Tier 1 technical discussions, representing Wayve’s product architecture, integration approach, and technical assumptions. - Act as a technical bridge between customer programs and Wayve internal teams, ensuring customer-specific integration needs are clearly understood without unnecessarily fragmenting the core product architecture. About you In order to set you up for success as a Solution Architect at Wayve, we’re looking for the following skills and experience. Essential - System & SW architecture expertise: Experience defining or contributing to technical architecture for ADAS, autonomous driving, embedded software, or vehicle systems, especially at the software–vehicle interface. - Product Boundary definition: Ability to define clear technical boundaries, ownership models, assumptions, dependencies, and interface contracts between internal software and external vehicle systems. - Vehicle and embedded software understanding: Good understanding of vehicle electronics, embedded software constraints, ECU integration, real-time execution, timing, diagnostics, and production vehicle software environments. - Automotive communication and E/E architecture: Knowledge of automotive communication protocols and architectures, such as CAN, FlexRay, Automotive Ethernet, SOME/IP, AUTOSAR, or equivalent. - OEM integration experience: Experience working with, or integrating systems for, automotive OEMs or Tier 1 suppliers. Ability to support discussions on OEM-specific requirements, standards, and integration constraints. - Requirements and specification quality: Ability to translate product requirements and customer discussions into clear technical specifications, interface requirements, and validation-ready requirements. - Cross-functional multidisciplinary experience: Proven ability to work effectively across Product, Software Architecture, Hardware, Calibrations, System Safety, Validation, and customer-facing teams, including Field Application Engineering. Experience should span unit-level, subsystem-level, and system-level discussions, with the ability to align technical decisions across engineering domains and translate customer or product needs into practical architectural solutions. - Technical communication: Strong written and verbal communication skills, including the ability to explain complex architecture