My application process consisted a phone screen with a recruiter, two technical phone calls with engineers and a 4 hour onsite interview. Phone screen: Streamlined, effective, easy to coordinate. Technical call 1: 10 minutes of conversation about my experience and several real time coding questions, with preference on C++ only. They discouraged python. Problems focused on data structures and algorithms. Technical call 2: 10 minutes of conversation about my experience and several real time coding questions, with preference on C++ only. They discouraged python. Problems focused on data structures and algorithms. Onsite: Invited onsite and placed in a conference room with a whiteboard. One hour time slots with several engineers on the team that I was interviewing for, with each person asking several undergrad-level white board questions on the board. Topics ranged from C++, control, path planning, geometry, etc. in total, they asked me to solve 11 different questions on the white board. Take away: The interview process at Nuro is almost entirely paralleled to the technical problems solving interviews at google. They prioritize the ability to execute on entry level computer science tasks (despite your experience level) and de-value soft skills or application level knowledge. If you can’t solve software trivia questions or math problems that you haven’t seen since college, they’ll pass. Modern engineers use resources at their discretion to solve complex problems, yet they chose to analyze the ability for candidates to memorize software and algorithmic puzzles (how to tell if a polygon is closed, etc). Give candidates a take home project and let them demonstrate their ability to be a developer. White board problems only test a small fraction of a candidates ability.