How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Onsite rounds at Motive.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Motive during technical interviews.

Design a delivery system with route visibility

Quick Overview

This question evaluates a candidate's ability to design scalable, low-latency real-time delivery and route-visualization systems, assessing competencies in distributed systems, event-driven architectures, geospatial data processing, API design, operational monitoring, privacy controls, and failure recovery within the System Design domain.

System Design: Real-Time Delivery Logistics and Route Visualization Platform

Context

Design a platform that allows dispatchers and end customers to view couriers' real-time positions and routes for millions of deliveries per day. The system must ingest GPS data from courier apps, compute and render routes, stream live updates to web/mobile clients, and support historical route queries.

Requirements

Functional
- Real-time tracking of couriers on a map (sub-second to a few seconds latency).
- Route computation with ETAs; dynamic re-routing with traffic.
- Live and historical route visualization for dispatchers and customers.
- Order lifecycle: create order, assign courier, update status, complete.
- APIs for orders, assignments, location updates, live/historical route queries.
Non-functional
- Scale to millions of deliveries/day; hundreds of thousands of concurrent couriers.
- Low-latency updates; high availability; multi-AZ deployment.
- Event-driven architecture with durable streams.
- Offline handling for mobile; privacy controls; failure recovery.
- Monitoring, alerting, and capacity estimates (compute, storage, bandwidth).

Deliverables

Detail: service architecture, data model, GPS ingestion pipeline, route computation, map rendering, event streaming, scalability plan, latency vs. consistency trade-offs, offline handling, privacy controls, failure recovery, APIs (orders, assignments, locations, queries), capacity/storage estimates, and monitoring/alerting.

Quick Overview

Context

Requirements

Functional

Real-time tracking of couriers on a map (sub-second to a few seconds latency).
Route computation with ETAs; dynamic re-routing with traffic.
Live and historical route visualization for dispatchers and customers.
Order lifecycle: create order, assign courier, update status, complete.
APIs for orders, assignments, location updates, live/historical route queries.

Non-functional

Scale to millions of deliveries/day; hundreds of thousands of concurrent couriers.
Low-latency updates; high availability; multi-AZ deployment.
Event-driven architecture with durable streams.
Offline handling for mobile; privacy controls; failure recovery.
Monitoring, alerting, and capacity estimates (compute, storage, bandwidth).

Deliverables

Design a delivery system with route visibility

Quick Overview

System Design: Real-Time Delivery Logistics and Route Visualization Platform

Context

Requirements

Deliverables

Solution

Comments (0)

Design a delivery system with route visibility

Quick Overview

System Design: Real-Time Delivery Logistics and Route Visualization Platform

Context

Requirements

Deliverables

Solution

Comments (0)