Sr. Vehicle Systems Architect

Position: Sr. Staff Vehicle Systems Architect
About UsRivian and Volkswagen Group Technologies is a joint venture between two industry leaders with a clear vision for automotive’s next chapter. From operating systems to zonal controllers to cloud and connectivity solutions, we’re addressing the challenges of electric vehicles through technology that will set the standards for software-defined vehicles around the world.

The road to the future is uncharted. By combining our expertise across connectivity, AI, security and more, we’ll map a new way forward. Working together, we’ll create a future that’s more connected, more intelligent, more sustainable for everyone.

Role Summary The Vehicle System Architecture team owns the vehicle-level mechatronic architecture at Rivian VW Group Technologies. We translate product intent from Brand Product Definition, Program, Cost Engineering, Manufacturing, Strategy and Reliability into parts and function distribution across the vehicle — from product concept through manufacturing.

You are accountable for the architecture of a platform program to sequences on the manufacturing line. You lead the actual architecture — where functions live, which controllers exist, what the vehicle can do without. You build the models and processes that let those decisions be made with data and are reused across programs.

Responsibilities1. Own the Vehicle Architecture

• Lead the vehicle-level architecture for a platform program: controllers and placement, functional allocation across ECUs, LV/HV distribution concept, sensor and actuator distribution, packaging, temperature/environmental and NVH constraints — from concept through production release.

• Lead architecture trade studies with quantified outcomes: cost, mass, range, power, temperature, NVH, complexity, reliability and manufacturability. Derive the cost functions —Trade studies ship with its model, parameters and sensitivity.

• Cost-down by subtraction before optimization: use the model to prove which controllers, harness runs, sensors and requirements the vehicle can do without, and remove them before tuning what's left.

• Translate ambiguous partner asks into architecture decisions and hold them at program gates; own the architecture decision record and its rationale.

• Align architecture to technology roadmaps — evaluating when to adopt new tech, and what it costs the platform.

• Close the loop with the physical vehicle: define the correlation and characterization tests that validate the models, and own each model's error budget.

2. Build the Models and Tooling Behind the Decisions

• Curate and decide first: define the design space — what is fixed, what is free, which attributes matter — select the candidate architectures, weigh the trades and make the call. Then build the AI-assisted pipelines that widen the search: proposing controller allocations, harness topologies and function distributions.

• Build and own the meta-models that connect the architecture: feature → function → controller → physical interface → software interface, with parameters flowing end to end.

• Author first-principles and stack-up models (Python, Julia/Modelica, C++; SysML v2 where it earns its keep) at the fidelity the decision demands. Collaborate with domain systems engineers on correlated models for lock.

• Drive reliability by design: top-down from vehicle attributes and bottom-up from component data.

• Lead the vehicle-level STPA as a design process — surfacing hazards and architecture-level control gaps early and feeding them back into the model — rather than as a gate. As the team matures, that process becomes the basis for quality enforcement.

3. Technical Leadership and Department-Wide Impact

• Negotiate the architecture with VW Group, Rivian brand teams and partner functions and anticipate the next…