Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

7 stories

Likes earn the author +10 XP for the first 3 likes each day

RivianSoftware EngineerSenior+
Sep 2026

Sensors, Camera Failures, and a False-Positive Case Study

A recruiter contacted me, and I then interviewed with the hiring manager for an autonomous-vehicle systems role. The interview lasted one hour and began with brief introductions from both of us. The manager then gave me a set of driving capabilities and asked how I would choose the types and placement of sensors needed to support those capabilities. Next, I was asked about the external failure mo…

Technical Screen1
RivianSoftware Engineer
Reported Jul 2026

Rivian Software Engineer Interview Experience: OOP problem and delayed progression

After a recruiter screen, I answered resume-based behavioral questions and then had a technical interview built around an object-oriented problem tailored to the team. It seemed focused on how I reasoned, not only whether I could write code. There was also a short hiring-manager meeting, followed by bundled technical rounds: a coding round and a conceptual round, about half an hour each. Scheduli…

HR Screen0
RivianBackend Engineer
Reported May 2026

Rivian Backend Engineer interview with delayed feedback and missing follow-ups

I went through a frustrating, logistics-heavy interview process for a Software Engineer role. The difficulty felt average, and communication was often delayed or missing. The recruiter or HR screen covered basic engineering questions, production-line and equipment questions, and behavioral topics. The hiring manager meeting included more role-fit questions, after which communication slowed down.…

No responseHR Screen0
RivianSoftware Engineer
Reported May 2026

Rivian Software Engineer interview with panel interviews and a project presentation

I went through a fairly organized, conversation-heavy process. It started with an HR call, followed by a longer meeting with the hiring manager. After that, I had panel-style interviews with several interviewers from different teams. Each round included time for questions and follow-ups. The format combined behavioral and technical fit without feeling like a trick. In one of the later sessions, I…

RejectedHR Screen0
RivianSoftware Engineer
Reported May 2026

Rivian Software Engineer interview with robotics debugging

The process felt fairly straightforward from the beginning. The interviewers were friendly, and we spent a lot of time discussing my actual projects and what I worked on day to day. Early on, I realized the role had been described in a way that blended into a systems engineering focus in the autonomy space, and the questions matched that impression. One round focused on systems thinking and how I…

0
RivianSoftware Engineer
Reported May 2026

Rivian Software Engineer interview: nearly a month waiting for feedback

My recruiter and the early rounds went smoothly. The recruiter was responsive and welcomed my questions, so the first part of the process was easy to navigate. After the second interview, the tone shifted because of what happened afterward. I waited almost a month to hear back about the rejection. When I asked for feedback, I didn't receive any, and no one gave me useful pointers about what speci…

0
RivianSoftware Engineer
Reported Apr 2026

Rivian Software Engineer interview: project discussion and high-voltage experience

My screening was laid-back and centered mostly on my resume and projects. I talked through my previous work, and the first interview went into more detailed technical questions related to one of my projects. I was also asked about my high-voltage experience. There were some additional technical questions, but they weren’t overly complicated. It felt like they were checking whether my past work tr…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP