I had two interviews and one follow-up call after that.

The first interview was with the HR person. We covered the company and job details, as well as my experience and background. It was a usual initial interview, which was very nice and friendly.

The second interview was with a technical lead. We covered some additional details related to the stack they are using, the tools, and the way work is done on their end. I also shared my experience and some details about the projects and technical challenges I've worked on.

Finally, in the follow-up call a few days later, they let me know they didn't want to proceed with my application. They also shared some valuable feedback about what I could have done better, which I think is great.

I made a mistake by not providing more technical details when sharing information about some things I was working on. So, my advice to anyone who has an interview with them is to share as many details as possible in cases like that (about the code workflow, the DB structure, the API usage, etc.).

The interviews and the follow-up call were nice and pleasant. Regardless of the outcome, I can only share positive feedback about Rivian's interviewing process.

Imagine the best software engineer. How would you describe them in three words?

Can you give more details about what you mean by "accountability"?

You mentioned that you are currently working at [Company Name] and are specifically focused on [Project/Technology/Framework]. Can you explain in more detail what you are working on?