There was the first interview with the hiring manager to discuss overall competencies and experience.
Then there were four one-hour interviews with people from software, vehicle, hardware, and behavioral.
At the end of it all, HR called back saying that I didn't tick all the boxes but they were impressed. And then completely ghosted.
No response, no feedback.
It was pretty anticlimactic to an actually thorough and well-thought-out interview process.
What makes zonal architecture more effective?
What's the advantage of having a central supervisor controller to arbitrate safety-critical decisions?
How to optimize for throughput vs. latencies?
How to decompose overall latencies to subsystems?
The following metrics were computed from 1 interview experience for the Rivian System Architect role in Detroit, Michigan.
Rivian's interview process for their System Architect roles in Detroit, Michigan is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Rivian's System Architect interview process in Detroit, Michigan.