Zoox Interview Questions
& Process

The interview process itself was pretty standard: first a recruiter screen, then an interview with the hiring manager, followed by a panel round with five colleagues from different departments, and finally a last round with the VP or department head. The questions were appropriate for the role, but the recruiting team's communication was really bad. I spoke with the recruiting lead who scheduled a meeting, but he forgot about it and was 45 minutes late, only showing up after I emailed him. During the final rounds, I got a tour and a ride in the Zoox vehicle. The recruiting lead also asked for references right before and mentioned he'd call them. He said he expected an offer soon and would contact me by Friday or Monday with good news, using phrases like 'when you are in the role.' I sent a thank you note that evening. Friday and Monday passed, so I followed up a week later, and then again a week after that, but heard nothing. After three weeks, I contacted the hiring manager directly, which led to a generic rejection email from the recruiting lead saying I wasn't a good match. This was confusing since I made it to the final rounds and my references were apparently good. Despite enjoying the interviews and wanting to join Zoox, the recruiting team's unprofessional ghosting after checking references was extremely disappointing.

The interview had two main parts. First, there was a JavaScript & OOP Fundamentals section for about 25 minutes where I got technical questions on OOP concepts like polymorphism, inheritance, encapsulation, and abstraction, as well as JavaScript basics such as the event loop and event delegation, and web performance. I also had to look at a small JS code snippet and predict its output or fix it. Second, a 25-minute JavaScript Coding part involved one coding problem, and then I had about 5 minutes for my questions. I passed this and went to the onsite/loop stage, which had 4 rounds. The first was a DSA round where I solved four problems. The second was a Math round, focusing on word problems and formulas, which was pretty tough and the interviewer was quite rude. The third was a Technical Lead round where we did a deep dive into a past project, discussing its context, requirements, architecture, trade-offs, optimizations, challenges, and what I'd change. Whiteboarding was an option via Zoom. The fourth was a Frontend Coding round where I had to build a calculator in JavaScript using provided HTML/CSS. I felt I did really well in most rounds, with my technical solutions being solid and my project discussion going great, getting positive feedback. The math round was the only one I felt unsure about. About 1.5 months later, I got an automated rejection email. I suspect the math round might have been a factor, though its relevance to a frontend role wasn't clear. Good luck to others.

I went through technical interviews and felt good about the team and mission. But, the whole process fell apart at the very end during the compensation stage because we were way off on leveling and total pay. After passing all the main technical and cultural parts, I found out that because of Zoox's strict internal rules, the highest level they'd even consider me for was two levels below where I'm at now. The HR person said they couldn't go higher on the base salary. The final offer wasn't competitive at all, with a total compensation that was actually less than what I'm making now. They wouldn't give me any guaranteed liquid stock (like Amazon stocks), which made the whole package look bad financially and risky. Pros: Rigid and Non-Competitive Leveling: Zoox's leveling isn't like other companies, especially for senior/staff roles. Expect to be put at a lower level than you deserve. Bad Total Compensation: They expect people to take a big pay cut just to work there. The pay relies way too much on uncertain stock options (ZAR). HR was unprofessional: The HR person was dismissive, acting like they were doing me a favor and I should just accept less pay because the mission is cool. My advice to management: Match your pay and leveling to what's normal in the Bay Area. Stop wasting senior candidates' time by interviewing them extensively only to offer them a lower-level job than they're qualified for. The mission isn't enough to make up for bad pay.

The interview process was long but they were upfront about it. I have to say, it was the best recruiting experience I've ever had. The recruiters were really clear about what was coming next and even gave me interview tips tailored to the person I'd be speaking with. The interviews themselves weren't too bad. There were four rounds in total, starting with the recruiter screening. The third round involved a take-home assessment where I had 72 hours to prepare a 20-minute presentation on a specific topic. This round also included a 45-minute problem-solving segment. The final interview was a brief 30-minute chat with the VP of Vehicle Development.