Software Engineer applicants have rated the interview process at Zoox with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 52% positive. To compare, the company-average is 42.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 23 days to get hired, when considering 58 user submitted interviews for this role. To compare, the hiring process at Zoox overall takes an average of 29 days.
Common stages of the interview process at Zoox as a Software Engineer according to 58 Glassdoor interviews include:
Phone interview: 34%
One on one interview: 16%
Presentation: 14%
Skills test: 11%
Group panel interview: 8%
Background check: 6%
Personality test: 5%
IQ intelligence test: 2%
Drug test: 2%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Zoox
Interview
Phone call, technical screen and then onsite.
The overall process is pretty bad. Each interviewer wants a techbook dictionary response. There's a strong sense of I'm smarter/better than you throughout the entire process. It was not a fun/enjoyable experience.
Their math/science section is a massive waste a time. It is an interview designed to make the interviewer feel intelligent. It is one of those brain teaser interview questions.
Interview questions [1]
Question 1
build a calculator,
system design a point/graph chart
Recruiter call to go over resume and position, tech screen (coding challenge), onsite with four rounds (coding challenge, system design, math and problem solving (MAPS), and one with team manager), leadership call.
interviewed at zoox for software engineer. had their famous brain teaser, a c++ round, 1 domain problem solving and 1 hiring manager. the hiring manager apparently has no interest and was unprofessional. The feedback from him is an unfinished sentence, according to my recruiter. Others are ok.
It was a live coding screening. It lasted an hour. It was a planning problem involving a lane change maneuver given other vehicles on road. There wasn’t much dialogue, just coding.