Real, anonymous reports from people who interviewed for Software Engineer at Nuro, newest first and distilled into what to expect across the loop.
After a recruiter reached out about my availability, I did an initial screening call focused on my background and experience. It felt like a fairly standard first conversation—mostly setting context and getting a clear picture of what I’d done. About a week later, I moved into a technical interview with the hiring manager, and that’s where the process got much more domain-specific.
I applied online and went through the usual early flow—first a recruiter screen where the focus was quick logistics and getting set up for a technical phone screen. The tech screen was the main event and it was noticeably intense: I had an hour and the interviewer pushed several tasks in that time, including Bash scripting debugging and at least one LeetCode-style problem. It threw me off because it didn’t feel like the most modern, well-paced technical interview setup, and it also felt like the interviewer wasn’t very experienced.
The interview process typically begins with a recruiter call focused on logistics and the candidate's background, setting the stage for subsequent technical evaluations. Candidates noted that this initial interaction was generally friendly and informative, but the depth of discussion varied.
Candidates experienced a technical phone screen that often included coding challenges, with a mix of algorithmic problems and domain-specific questions related to systems engineering or robotics. The intensity and structure of these screens varied, with some candidates feeling the pace was too rapid to demonstrate their reasoning effectively.
Following the initial screens, candidates faced multiple technical interviews that delved deeply into systems design, coding, and domain-specific knowledge, often requiring clear explanations tied to past experiences. The emphasis was on assessing depth of knowledge and problem-solving under pressure.
The onsite interviews were described as intensive, often consisting of several back-to-back technical rounds with minimal breaks. Candidates noted that the format could be stressful, with some interviewers exhibiting varying levels of engagement and professionalism, impacting the overall experience.
Candidates reported mixed experiences regarding communication throughout the process, with some feeling left in the dark after interviews and others receiving little to no feedback post-interview. This lack of clarity contributed to feelings of frustration and uncertainty about their performance.
Many candidates reflected on the need for better preparation for the specific technical demands and the importance of understanding the interviewers' expectations. A common takeaway was the desire for more structured guidance during technical assessments to alleviate stress and improve performance.