Real, anonymous reports from people who interviewed for Software Engineer at Motional, newest first and distilled into what to expect across the loop.
After a recruiter call, I talked through the role and what the team was responsible for, and we also covered my background and why I was interested in the company. The tone felt upbeat and straightforward, and it mostly matched what I expected from an HR screen.
My process felt fairly structured and mostly technical from the start. I began with a recruiter conversation, then moved into a hiring manager round, followed by an on-site with four panel interviews. What stood out was that the on-site was entirely technical—no separate behavioral round.
The interview process typically begins with a recruiter call that covers the role, team responsibilities, and the candidate's background. This initial interaction is generally described as friendly and straightforward, setting a positive tone for the process.
Candidates can expect multiple technical interviews focusing on coding, system design, and domain-specific knowledge, often with a mix of LeetCode-style questions and discussions related to sensor calibration and computer vision. The difficulty is usually average, but some candidates noted a high bar in specific areas.
The on-site interviews often involve multiple rounds with different interviewers, focusing on both technical skills and cultural fit. These sessions can feel intense due to their length and the number of interviewers, but they are structured to assess fit from various perspectives.
Candidates reported varying experiences with communication throughout the process, with some noting delays and a lack of transparency regarding next steps. This inconsistency can lead to frustration and uncertainty about the outcome.
The general atmosphere of the interviews is described as friendly and supportive, with many candidates appreciating the relaxed vibe despite the technical rigor. However, some reported negative experiences due to distracted interviewers or unclear instructions.
Many candidates did not receive offers, often reflecting on how the process felt aligned with the role's requirements, even if they were not selected. Common takeaways include the importance of preparation for specific technical areas and the need for clear communication throughout.