Real, anonymous reports from people who interviewed for Software Engineer at Nuro, newest first and distilled into what to expect across the loop.
I went through a long, robotics-focused sequence with several technical stages and a heavy emphasis on walking through my past work.
I had a shorter, more direct technical track where the interviews moved quickly into coding without much setup or back-and-forth.
Most candidates start with a recruiter screen that discusses their background and the role, but experiences vary from engaging to disengaged interactions. This initial call sets the tone for the rest of the process.
Candidates typically face a technical coding screen that includes algorithmic problems, often in a LeetCode-style format, with varying levels of guidance and difficulty. Performance in this round is crucial for advancing.
The onsite process usually consists of multiple back-to-back interviews that cover coding, system design, and sometimes behavioral questions, often under time pressure. The format can vary significantly, impacting candidate experience.
Interviews often emphasize robotics and domain-specific knowledge, particularly in safety and autonomy, requiring candidates to connect their experience to Nuro's work. This focus can be a key differentiator in evaluations.
Candidates report mixed experiences regarding communication throughout the process, with some feeling left in the dark after interviews. Clear communication and timely follow-up are noted as critical for a positive experience.
Despite strong performances in technical rounds, many candidates did not receive offers, often citing unclear criteria or fit as reasons. Feedback is sometimes lacking, leaving candidates uncertain about their standing.
