Preparing your design workspace

Loading the problem and your latest saved attempt…

Design Robot-Assisted Restaurant Orchestration

Coordinate restaurant orders, kitchen readiness, and autonomous delivery robots without duplicating or losing a meal.

Problem statement

For this exercise, assume a restaurant uses autonomous indoor robots to move prepared dishes from kitchen pickup stations to dining tables.

Staff enter dine-in orders, the kitchen marks each dish ready, an orchestrator groups compatible dishes into delivery jobs, and an available robot accepts, transports, and confirms each handoff. Staff can pause a robot, reassign a stalled job, and inspect the authoritative status of an order, dish, job, and robot.

A retry or robot reconnect must not deliver the same dish twice, while a robot that becomes unreachable must not leave a prepared dish permanently stranded. Assume robots expose location, battery, load capacity, health, and a monotonically increasing command sequence.

Indoor mapping and obstacle avoidance run on the robot and are outside scope; design the fleet and fulfillment control plane, not the motion-planning algorithm.

What to build

  1. For this exercise, assume staff can read the authoritative lifecycle of each order, dish, delivery job, and robot.
  2. For this exercise, assume the system can group ready dishes into capacity-safe jobs and assign each job to one eligible robot.
  3. For this exercise, assume a robot or staff member can confirm pickup and table handoff without applying a duplicated report twice.
  4. For this exercise, assume staff can pause robots and safely reassign or resolve stalled jobs while preserving an auditable history.

At scale

  • For this exercise, assume 1,000 restaurants, up to 80 robots and 500 active tables per restaurant, and a global peak of 20,000 dish-ready events per second.
  • For this exercise, a ready dish should normally receive a robot assignment within two seconds and staff status reads should complete within 300 milliseconds p95.
  • For this exercise, robot connectivity may disappear for two minutes; commands and telemetry may be duplicated or arrive out of order after reconnect.
  • For this exercise, never allow two live jobs to own the same dish or robot assignment lease, and retain enough transition evidence to investigate reassignment conflicts.