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. Scheduling was generally orderly, but there was a strange gap of about a month before one meeting. Later I completed an online coding test with a staff engineer from the US. The technical work was approachable, yet I did not get an offer and was left wondering whether I had missed something small.

Location: Palo Alto, CA. Overall feedback: positive. Offer status: no offer.