Your Zoox Prep Plan
- Pass the technical screen: trivia in your own language, then a runnable class build like airline pricing
- Practice the math and problem solving round out loud in short daily sets
- Prepare onsite algorithms with scale-out follow-ups, one robotaxi design and your executive-round stories
Zoox runs a fairly conventional software loop with one round almost nobody else has. Nearly every candidate, software engineers included, sits a Math and Problem Solving round: about an hour of short spoken questions at the level of high school math and physics. Around it sit the pieces you'd expect. A recruiter call comes first, then a one-hour technical screen, then an onsite of usually around five interviews, then a short leader interview with an executive and reference calls. Most of your prep belongs to the screen. It isn't a LeetCode puzzle. Recruiters in 2025 and 2026 described it the same way, as 10 to 15 minutes of rapid trivia about your language followed by an object-oriented problem framed as a real scenario. You write it in an online editor, and it has to run. The plan below follows the loop. Screen first, math every day, then onsite algorithms, design and the people rounds.
- The screen: Trivia, then a class build that runs. About 10 to 15 minutes of questions on the language you picked, then one object-oriented problem in an online editor such as CoderPad. Interviewers judge the class design along with the output. Airline pricing is the long-running screen problem, and roller coaster scoring opened an October 2026 onsite.
- The signature: Math and Problem Solving, out loud. About an hour of short spoken questions in algebra, geometry, probability, physics and estimation. The round comes from the co-founder and CTO and has run since Zoox's early days. How much it weighs varies by team, and your reasoning counts heavily.
- The gate: An executive, then your references. After the panel comes a short leader interview with a VP or C-level executive, and it can turn down a candidate the panel liked. References follow, usually a former manager and a colleague, and the calls go deep.
The plan, phase by phase
Each phase is a share of your prep time, so the plan stretches to a month or squeezes into ten days. The screen gets the biggest share. It's the first gate, and it looks unlike most companies' screens. The math round gets a small daily slot from day one, because it improves with reps far more than with a weekend cram. Algorithms, design and the people rounds follow. Don't move past a checkpoint until you can clear it without notes.
Learn your loop before you plan it
- Read the Zoox interview process and how Zoox decides. Then ask your recruiter four things. Which language you'll use for the screen. Whether the onsite has to be in C++. Whether your loop includes system design. And who you'll meet at the end. Zoox itself says formats vary by role.
- Openings are team specific, and the team shapes the loop. In 2024 and 2025, motion planning and other vehicle teams leaned on C++ and domain rounds. Backend loops in 2025 and 2026 had a design round, and a Senior/Staff loop in 2026 had two. Zoox has published no rule on AI assistants in interviews, so assume a live round without one unless your recruiter says otherwise.
Trivia and a class build that runs
- Start with what Zoox tests in coding, then language trivia. The trivia follows the language you choose, and it's scored. A 2024 senior candidate solved the coding problem and was still rejected on trivia answers. For C++ roles in 2025, the trivia leaned on pointers versus references and on smart pointers. In an October 2026 onsite, a candidate switched to Go to narrow the trivia and got output prediction instead: what a program prints after appending to a sub-slice, and after storing pointers to a loop variable. That last answer changed in Go 1.22, so say which version you're assuming.
- Then build airline pricing. It was the most-asked Zoox screen problem from 2021 through 2025. Input lines look something like "United 150.0 Economy", each airline has its own cost rules, and you price tickets with a base class and one subclass per airline. One follow-up asked how the design holds up with a hundred airlines.
- Then build roller coaster scoring, in the same lesson. It's the newest class-design problem, from the first day of an October 2026 onsite where the candidate called it "the classic roller coaster," and a May 2026 machine learning screen carries the same title. The shape is something like this: read lines describing coasters of several types, then compute each one's result with rules that depend on the type. That candidate finished one type before time ran out. The wrap-up went to design, streaming a large input line by line and registering coaster types instead of switching on them. Build yours so a new type is one new class. On a motion planning team, swap in lane change in C++, asked from 2021 through 2025. On a full-stack loop, practice the chaining calculator in JavaScript, the frontend round of onsites in December 2025 and January 2026.
- Grade yourself the way Zoox does. A 2026 infrastructure candidate got a working answer that skipped Python OOP principles and wasn't invited onsite. Keep classes small with clear names, run the code on a few inputs, and leave a few minutes to say what you'd change.
The math round, out loud
- Read the math and problem solving round. It runs about an hour, and the interviewer explains each question out loud. A Zoox engineer described the level in October 2026 as "high school math and physics." The topics candidates name are algebra, geometry, probability, physics and estimation. The number of questions varies, so don't plan around a count.
- Do a short set every day, starting in week one. Take four or five questions and speak every step as if someone were listening. Mix a probability question (a Bayes update is a good default), a geometry or spatial one, a physics one about motion, and an estimate. A 2024 loop asked for the distance from Earth to the Sun, which is the flavor to expect from an estimation question.
- Practice getting stuck. Zoox says it wants to work through problems with you, and a math interviewer wrote in 2026 that some interviewers weigh communication and behavior "more heavily than even the math answers." Say your plan before you calculate. State assumptions, check units and take a hint without fuss. How much the round counts varies by team, but going quiet never helps.
Onsite algorithms with scale-out follow-ups
- Zoox's internship guide describes its coding questions as similar to LeetCode exercises, and full-time onsite reports match. Start with onsite algorithms, led by the stock-profit family. Candidates were asked it through September 2025, and it's still the onsite staple to expect. The base version asks for the best profit from one buy and one sell. A 2024 loop added the version with unlimited trades.
- Then practice the follow-ups, because that's where the round goes. Loops from 2021 to 2024 followed up by asking candidates to multithread the answer or to split data too big for memory across N machines, in pseudocode in one 2023 loop. Know what each chunk reports back: its lowest price, its highest price and its best profit, so the merge can pair an early low with a later high. The same 2024 round had a math-flavored follow-on, finding array values that satisfy y = a*x + b by hashing one side and matching the other.
- If your team ships code to the vehicle, refresh C++ even if your screen was in Python. A 2024 candidate's recruiter moved the onsite to C++, and a Zoox engineer explained that teams check C++ at the onsite "since that's how we deploy onto our robotaxi." Older Practice Problems covers older C++ asks, like a queue class (2023) and a linked list built on shared pointers (2024). An October 2026 onsite opened its coding round with trivia, so keep that sharp through the onsite too.
One robotaxi design, rehearsed
- Read Zoox system design. Some loops have no design round. Vehicle-team onsites in 2024 and 2025 ran domain rounds instead, while backend loops in 2025 and 2026 had one, sometimes as early as the technical screen. The rounds lean on Zoox's own domain. A Zoox engineer put it plainly in October 2026: they "won't be like design a Uber/Slack."
- Rehearse the live robotaxi map end to end. Prompts reported in 2026 look something like this: take in location updates from the fleet and show authorized clients a near-real-time map, or find moving vehicles near a point that fit some criteria. Prepare for updates that arrive late or out of order, and for hot spots where many cars bunch up in one area. Then go deeper on the backend than feels necessary. A frontend-leaning candidate who failed the round in 2026 told others to do exactly that.
Why Zoox, your project and the executive
- Zoox says it loves to ask "Why Zoox?", so give an answer a rival robotaxi company couldn't share. Zoox builds its own purpose-built, fully driverless vehicle, and a view on what that means for the software you'd write beats a general take on self-driving. The behavioral overview shows a weak and a strong answer.
- Behavioral questions come mostly through the hiring manager and the leaders after, and not every loop has a dedicated behavioral round. Pick one project you drove and know it cold: the problem, your decisions, the numbers, what you'd change. Reported questions from 2024 and 2025 asked for a project you're proud of and why, and for the hardest technical project you'd done recently. A 2024 director asked about the candidate's worst quality and what they wanted from the job. The behavioral overview and questions by theme cover the rest.
- The executive conversation is short, about 20 to 30 minutes, and it's a real gate. Then warn your references, usually a former manager and a colleague, since their answers get checked against yours. Tell them which projects you discussed. The behavioral overview covers both stages.
Picture a four-week runway. The first week belongs to the screen. Spend a day on the process and your recruiter questions, then drill trivia, build airline pricing, and move on to roller coaster scoring. The math sets start that same week and run every day until the onsite. In week two, finish the screen work and start the stock family with its threading and machine-splitting follow-ups. C++ comes in the third week if your team needs it, along with the robotaxi map if your loop has design. The last week is your project story, Why Zoox, a heads-up to your references and a mock or two. Short on time? Keep the order and cut the older problems first.
What Zoox asks right now
These are the Zoox interview questions asked in the last 12 months, newest first. The long-running staples come last, with their years.
- Roller coaster scoring (October 2026 onsite). Parse lines describing coasters of several types and score each one by its type's rules, then talk through streaming the input and a registry. Worked in the class design lesson.
- Language trivia (through October 2026). C++ pointers, references and smart pointers, or Go output prediction on slices and loop variables. It opens the screen and sometimes the onsite coding round.
- The math and problem solving round (2026). Short spoken questions in algebra, geometry, probability, physics and estimation. See the math round lesson.
- A live robotaxi map and nearby vehicle search (May and August 2026). Fleet location updates in, a near-real-time map or a filtered nearby search out. Worked in the robotaxi map design.
- A chaining calculator in JavaScript (December 2025 and January 2026). An object-oriented calculator that shows running results as you chain operations, from the frontend round of a full-stack onsite.
- Older staples, with their years. Airline pricing, the screen staple (2021 to 2025), lane change in C++ (2021 to 2025), and stock profit with threading and multi-machine follow-ups (2021 to 2025).
Why the screen gets the biggest block
The screen comes first and looks the least familiar. A LeetCode habit won't carry you through ten minutes of language trivia, or through a class build where the structure gets judged as hard as the answer. Its problems are also the most predictable, so the prep can be concrete. Onsite algorithms matter, but most candidates already know that format. The math round is unfamiliar too. It responds to small daily sets much better than to a late cram, which is why it starts on day one and runs to the end.
In the room
- Trivia is scored. Drill the language you'll code in, and say which version you're assuming when the answer depends on it.
- Make the class build run. Drill airline pricing and roller coaster scoring. Give each type its own class, register types instead of switching on them, and run a few inputs.
- Talk through the math. Do short daily sets out loud. State your assumptions, check units and take hints.
- Expect the follow-up after the stock problem. Be ready to thread it or spread it across machines, and to merge what each chunk found.
- Treat the executive round as a gate. Bring a specific Why Zoox, one project you know cold, and references who know what you said.
Weight your Zoox prep toward the screen: trivia in your language and a runnable class build like airline pricing. Start daily math sets on day one and say every step out loud. Add the stock family with its scale-out follow-ups, refresh C++ if your team ships to the vehicle, and rehearse the live robotaxi map if your loop has design. Close with a specific Why Zoox and a project story strong enough for an executive.
Key Takeaways
- ✓Spend the biggest block on the screen: language trivia, then a runnable class build like airline pricing or roller coaster scoring.
- ✓Practice the math round daily in short spoken sets, because how you reason counts heavily.
- ✓Prepare the stock-profit family with its threading and multi-machine follow-ups, and refresh C++ for vehicle teams.
- ✓Treat the executive round and the reference calls as real gates, with a specific Why Zoox.
Zoox interview guideKnow what Zoox asks before you walk in.
21 coding · 4 system design · 30 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.