What Zoox Tests in Coding
- Know the two coding formats: the trivia plus class-design screen and the algorithmic onsite
- Know what gets scored, from your class hierarchy to your trivia answers
- Know which language to pick and how ML, data, QA, embedded and mobile rounds differ
Zoox has two coding formats, and they test different things. The technical screen is about an hour. It opens with rapid-fire trivia about the language you chose, then hands you one object-oriented problem framed as a small real-world scenario. You write it in CoderPad or a similar pad, and it has to run against the input you're given. The onsite is closer to what you'd expect from a big tech loop: algorithm problems from the LeetCode family, often with a follow-up that asks how the answer scales.
More than a dozen candidates from 2023 to mid-2026 describe the same screen script, and recruiters in August 2025 and May 2026 described it in nearly the same words. One of them told a candidate to expect "something that is not leetcode." Here's how each round runs and what gets people cut, then the problems candidates are getting now. The lessons after this one work them in full.
The Zoox technical screen: trivia, then a class-design problem
The trivia. Recruiters in 2025 and 2026 put it at 10 to 15 minutes, and some older screens ran up to 30. It follows your language. C++ candidates get pointers versus references, smart pointers, virtual functions and polymorphism. Python candidates have been asked about static versus dynamic typing, the different kinds of methods, and what happens when you copy a dictionary. It moves fast, and it counts. A 2024 senior candidate solved the coding problem correctly and was still rejected, because the trivia answers didn't match what the interviewers expected. The full drill set is in Language Trivia.
The problem. What's left of the hour goes to one practical build. Candidates describe a base class, a few derived classes and some logic that runs through them. In the two problems candidates name most, the input is plain lines of text, and each item gets a result from its own type's rules. A 2024 candidate said it "needed to run and get the correct answer," and another described test cases to pass inside the time limit. So this isn't a whiteboard sketch. It's working code, and the code gets read.
The shape looks something like this. You read lines, look up the right handler for each one, and let the subclass supply the rule that differs. A registry keeps a new type to one small class, and building each handler once follows a 2024 candidate's advice to avoid unnecessary instances.
PRICERS = {}def register(name): def add(cls): PRICERS[name] = cls() # one instance per type, built once return cls return addclass Pricer: def operating_cost(self, base_fare, cabin): raise NotImplementedError def ticketing_cost(self, base_fare, cabin): raise NotImplementedError def price(self, base_fare, cabin): return self.operating_cost(base_fare, cabin) + self.ticketing_cost(base_fare, cabin)def price_lines(lines): # lines like "United 150.0 Economy" for line in lines: # one at a time, so big input never sits in memory airline, base_fare, cabin = line.split() yield airline, PRICERS[airline].price(float(base_fare), cabin)Each airline then becomes a short subclass with @register("United") on top, overriding only the costs that differ. That fits the long-running airline pricing problem, and roller coaster scoring takes the same skeleton with a scoring method in place of the costs. Both are worked in full in Class Design: Roller Coaster Scoring & Airline Pricing.
Onsite coding is algorithmic, with a scale-out follow-up
The onsite is usually around five interviews. Coding sits next to system design, a hiring manager conversation and the math and problem solving round that nearly every Zoox candidate sits. Zoox's own internship page describes its coding questions as similar to exercises on platforms like LeetCode, and Zoox says intern questions are similar to the ones full-time hires get.
The onsite can open the same way the screen does. One October 2026 candidate's first onsite day started with trivia, then moved to coding, and the problem was roller coaster scoring, which the candidate called "the classic roller coaster." So class design isn't only a screen skill. Bring it to the onsite too.
The algorithm side has one recurring family: buying and selling a stock for the most profit. A September 2025 candidate said their hardest onsite question "effectively boiled down to the stock trade question." Zoox then pushes on scale. A 2024 loop asked to multithread and parallelize it. In 2023 one loop wanted pseudo-code for running it on multiple machines, and a senior C++ loop asked for code that splits work too big for memory across N machines. Know the one-pass answer cold, then have a plan for chunking the prices and merging the partial results.
When the stock problem comes back as "now make it parallel," each chunk has to return more than its best trade. It also needs its own lowest and highest price, so the merge can catch a trade that buys in one chunk and sells in a later one.
Zoox coding interview questions, newest first
The screen problems repeat, so the families below are worth knowing by name. Here's what candidates are getting, newest first.
Roller coaster scoring. The newest class problem came from the first coding round of an October 2026 onsite. You parse lines describing coasters of several types and score each one with rules for its type. The candidate finished one type before time ran out, and the interviewer said the rest were near copy-paste. The closing talk was about streaming large input line by line and registering each coaster type instead of switching on it. A May 2026 ML engineer screen carried the same title, with the same parsing-and-scoring shape.
Airline ticket pricing. The screen staple, asked of about a dozen candidates from 2021 to September 2025, and a cost estimation class problem was still being asked in October 2026. Input lines read like "United 150.0 Economy," each airline has its own operating and ticketing cost rules, and the follow-up asks what happens with 100 airlines. One 2022 interviewer kept steering the candidate toward more object-oriented structure instead of just making the code work.
The frontend calculator. Full-stack loops can add a frontend round. In a January 2026 onsite it was an Apple-style calculator in JavaScript, built object-oriented, that shows running results as you chain operations like 1 + 5 + 4. The frontend round lesson builds it in full.
Stock profit and onsite algorithms. The stock family, asked from 2021 through June 2026. Next to it sits a task of finding values that fit y = a*x + b at distinct indices, solved by hashing both sides (2023, 2024 and a May 2026 screen). Both are in Onsite Algorithms.
Lane change in C++. Autonomy and motion planning teams use this instead of the airline problem. It's an object-oriented C++ problem about changing lanes, sometimes by extending code you're handed, one scenario at a time. A June 2025 candidate called it "C++ data structure heavy" and got through only one scenario. Candidates describe it from 2021 to 2025, and a June 2026 screen added a motion simulation. See Lane Change & Vehicle Motion in C++.
Older problems. Interns and some early-career roles reported a two-question, 90-minute online assessment in 2025. Full-time software candidates get a live screen instead. Six problems from 2018 to 2024, among them the calculator and horse puzzle that older OAs paired, are in Older Practice Problems. They're good reps once the current families feel solid.
Which language to use in the Zoox coding interview
You choose, and the trivia follows your choice. C++ or Python covers most teams. JavaScript is the language for frontend and full-stack rounds. Go was accepted in October 2026: one candidate switched from Python to Go to narrow what the trivia could cover, and was then asked to predict a Go program's output without running it. Java showed up in 2021 and 2022 reports.
Pick the language you can defend at the trivia level, not just the one you code fastest in. And if your team ships code onto the vehicle, be ready for C++ either way. In 2024 one candidate's recruiter moved the onsite from Python to C++, and a Zoox engineer explained why: "teams need to check c++ at on-site stage since that's how we deploy onto our robotaxi." A Python screen doesn't guarantee a Python onsite.
How the rounds are scored
You can fail the screen three ways. Trivia has sunk candidates who solved the problem. Code that doesn't run, or gives the wrong output on the input, won't pass. And a working answer without real class design didn't pass either, as the 2026 infrastructure candidate found. A 2024 engineering manager candidate summed up the expected shape as "base class + some derived class definitions, then call some logic in the base class for a calculation."
Finishing every part matters less than a design that obviously extends. The October 2026 roller coaster candidate wrote one type out of several and was told the rest were copy-paste. That has limits, though. A 2025 lane change candidate got through one scenario and wasn't called back. Running out of time is common, and a clean hierarchy with one type working reads better than a long function that handles all of them. Be ready for a scale question too. One 2025 recruiter said the problem would be "highly scalable," and that's where streaming input and a registry come in.
Onsite algorithm rounds are graded the usual way: a correct, efficient answer, explained as you go, plus a sensible plan for the follow-up. Zoox's hiring article says its interviews aren't set up with "gotcha" questions, and that if you hit a problem the interviewer wants to work through it with you. Talk while you code, so there's something to work through.
ML, data, QA, embedded and mobile rounds
Other tracks swap in their own coding formats. These are the formats candidates have described, each with its dates.
- Machine learning engineer (2024). A recruiter described an extra onsite round where you write a runnable model in PyTorch, TensorFlow or numpy. Exact API recall wasn't expected, and you could ask for the reference.
- Data engineer (May 2026). The first technical screen was an hour of SQL: three queries on one schema, which the candidate called very straightforward.
- QA and integration (2023 to 2025). Python code review and code-analysis questions. Separately, one 2023 software engineer onsite had a dedicated C++ debugging round.
- Embedded (2021 to 2023). A single two-hour coding test. Parsing an ASCII or binary message packet came up, with questions on struct padding. See Older Practice Problems.
- Mobile (2024). An intern loop had iOS trivia with a LeetCode-style problem, then an app-building exercise in SwiftUI.
Practice by problem family
The lessons follow the sidebar. Start with class design, since it decides the screen, then the onsite algorithms. Lane change and the frontend calculator are for their tracks. Most loops have the math round, trivia opens most screens, and the older problems come last.
Class Design: Roller Coaster Scoring & Airline Pricing
The screen shape: parse lines, apply per-type rules behind a clean hierarchy, then extend it.
Onsite Algorithms: Stock Profit, Scale-Out & Line Math
Stock profit with multithreading and multi-machine follow-ups, and the y = a*x + b line task.
Lane Change & Vehicle Motion in C++
The autonomy and motion planning screen, worked scenario by scenario in C++.
The Frontend Round and Its Chaining Calculator
An Apple-style JavaScript calculator that shows running results as you chain operations.
The Math & Problem Solving Round
Short spoken questions in algebra, geometry, probability, physics and estimation.
Language Trivia: C++, Python & Go
The scored warm-up, by language, including the 2026 Go output-prediction questions.
Older Practice Problems (2018-2024)
C++ ownership, a queue class, packet parsing, the calculator and the horse puzzle.
Common questions
Is the Zoox coding interview LeetCode?
The screen usually isn't. Recruiters describe it as trivia plus an object-oriented problem with a real-world scenario, and one called it "not leetcode." The onsite is more LeetCode-like. Zoox's own internship page compares its coding questions to LeetCode exercises, and the stock profit family keeps coming back with scale-out follow-ups.
What coding questions does Zoox ask?
In the screen, class-design builds: airline ticket pricing is the staple through September 2025. Roller coaster scoring is the newest, from an October 2026 onsite, and a May 2026 ML screen carried the same title. Autonomy teams use a C++ lane change problem. Onsite, expect the stock profit family with multithreading or multi-machine follow-ups. Full-stack loops can add a JavaScript calculator.
What language should I use?
C++ or Python for most teams, JavaScript for frontend and full-stack, and Go has been accepted. The trivia follows your pick, so choose the language you know at the textbook level. On-vehicle teams may want C++ at the onsite even after a Python screen, as one 2024 candidate found.
How is the Zoox technical screen scored?
On trivia, working code and class design, and a weak result on any one of them can end it. Candidates have been rejected with correct code, once over trivia answers and once over missing object-oriented structure. A clean base class with one subclass working beats every case crammed into one function.
Does Zoox have an online assessment?
Not for most full-time software roles, where candidates get a live screen. Interns and some early-career roles reported a two-question, 90-minute OA in 2025, and embedded roles had a single two-hour problem from 2021 to 2023.
How do I prepare for the Zoox coding interview?
Build roller coaster scoring and airline pricing from scratch under an hour each, with a registry and line-by-line input. Drill trivia in your language until the answers come out like a textbook. Then work the stock problem and its parallel version, and do short daily sets for the math round.
Key Takeaways
- ✓The Zoox screen is scored trivia plus one runnable object-oriented problem, and weak class design can fail you even with correct output.
- ✓Airline pricing is the screen staple through 2025. Roller coaster scoring, the same shape, opened an October 2026 onsite.
- ✓Onsite coding is algorithmic, led by the stock profit family with multithreading and multi-machine follow-ups.
- ✓Pick C++ or Python by team, and be ready for C++ on vehicle teams even after a Python screen.
Free Zoox interview pages
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.