rivianvw.tech Sr. Staff Vehicle Systems Architect leads vehicle-level mechatronic architecture for platform programs at Rivian VW Group Technologies. They build models and tooling to support architecture decisions from concept through production.
Responsibilities
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.
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.
Qualification
BS/MS in Electrical12+ years in automotiveStrong PythonCost engineering fluency — should-costSTPA
Required
BS/MS in Electrical, Mechanical, Systems, Aerospace or Computer Engineering, or an equivalent demonstrated record.
12+ years in automotive, aerospace or electromechanical systems engineering, including at least one full program cycle owning system- or vehicle-level architecture decisions from concept to production.
Demonstrated first-principles and stack-up modelling: you have built the physics or system model that decided an architecture. AI assistance is welcome, not required.
Fluency across at least two of — E/E architecture (zonal, LV/HV power, network), vehicle controls SW, thermal and packaging, mechanical integration.
Worst-case and tolerance analysis practice (WCCA, Monte Carlo, DOE) applied to real designs.
Strong Python; comfortable in C++ or Julia/Modelica/Spice; git-native.
Ability to bind ambiguous asks into decisions and defend them with numbers to executives and Brands.
Preferred
Systems-of-systems and meta-modelling experience: SysML v2, FMI/FMU co-simulation, parameter management across model hierarchies.
Hands-on with LLM or agentic tooling applied to engineering artifacts — pipelines that generate or analyze designs.