← Zoox Interview Insights

Zoox·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Apr 2026

Summary

Zoox system design round for a software engineer role. The whole session was basically one big OOP design question that kept branching into design pattern territory. Not the most brutal interview I've had, but it required more depth than I expected going in.

Questions Asked (1)

Q1

Design an object-oriented Roller Coaster system that supports multiple coaster types (e.g., Wooden, Steel, Inverted, Hyper) and multiple scoring strategies (e.g., speed-based, height-based, thrill rating). Include class diagrams and key methods, and discuss whether scoring logic should live in the class hierarchy via polymorphism or be decoupled using the Strategy pattern.

System DesignTechnical Trade-offsData Modeling
Author's notes

I started with the inheritance route because it felt natural.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and identifying the core entities (coasters, scoring strategies). Then propose a class hierarchy for coaster types and a Strategy pattern for scoring, explaining why decoupling is preferable. Finally, discuss trade-offs and provide a simple class diagram.

Pro tip: Emphasize that the Strategy pattern allows scoring algorithms to evolve independently of coaster types, which is crucial for maintainability and extensibility in a real-world system like Zoox's autonomous vehicles.

1. Clarify Requirements

Ask about expected coaster types, scoring strategies, and whether scoring may change dynamically. Confirm if multiple scoring strategies can apply simultaneously.

2. Design Class Hierarchy

Define an abstract Coaster class with common attributes (name, speed, height) and methods. Create subclasses for Wooden, Steel, Inverted, Hyper, etc., each potentially overriding behavior.

3. Introduce Strategy Pattern

Define a ScoringStrategy interface with a method like calculateScore(Coaster). Implement concrete strategies (SpeedBased, HeightBased, ThrillRating). Inject the strategy into Coaster or a separate Scorer class.

4. Discuss Trade-offs

Compare polymorphism (scoring in subclasses) vs. Strategy pattern. Highlight that Strategy promotes composition over inheritance, avoids class explosion, and allows runtime changes.

5. Present Class Diagram

Sketch a simple UML diagram showing Coaster hierarchy, ScoringStrategy interface, and concrete strategies. Mention key methods like getScore() and setStrategy().

Key Points to Mention

  • Open/Closed Principle: Strategy pattern allows adding new scoring without modifying coaster classes.
  • Composition over inheritance: avoids deep hierarchy and code duplication.
  • Runtime flexibility: scoring strategy can be changed dynamically.
  • Separation of concerns: coaster data vs. scoring logic.
  • Potential use of Factory pattern to create coasters and strategies.
  • Consider performance implications if scoring is called frequently.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.