# Design a fleet management system: system design interview question

> Vehicle telemetry can arrive late, but assignments and maintenance rules must remain correct.

Source: https://sysround.com/questions/design-fleet-management-system
Updated: 2026-11-05


Difficulty: hard. Levels: Senior, Staff+.

## How the interviewer opens it

"Design a platform that helps companies manage their commercial vehicles, assignments, and maintenance. The platform also receives telemetry from the vehicles."

## What to clarify first

- Fleet size and telemetry volume
- Operator traffic and read-to-write ratio
- Telemetry content and delivery
- Assignments
- Maintenance rules
- Latency
- Consistency and availability
- Durability
- Retention
- Scope limits

## Scope of a strong answer

Core requirements:

- Register vehicles and show their current operational state.
- Assign vehicles and drivers without conflicts.
- Accept vehicle telemetry and show recent history.
- Track maintenance dates, distance thresholds, service completion, and due alerts.

Usually out of scope:

- Route optimization and automatic dispatch
- Future assignment reservations
- Remote vehicle control
- Cross-region failover

## What interviewers probe

### Telemetry delays and device changes

Reports can repeat, arrive late, or come from a replaced device. Current position and lifetime distance require different update rules.

### Assignments and vehicle availability

Assignments compete for both vehicles and drivers. Service transitions and delayed command responses create more races.

### Maintenance dates and distance

Distance reports can skip thresholds. Calendar rules must work without telemetry, and service completion changes the meaning of later reports.

## Common mistakes

- One status field mixes connectivity, assignment state, and maintenance state.
- The last received report overwrites newer vehicle state.
- A cache check serves as the only assignment conflict check.
- Every raw report enters the command database and competes with assignment transactions.
- Maintenance depends only on telemetry and misses calendar deadlines.
- The design accepts assignments during a long state delay without an explicit safety policy.

## The bar by level

- **Senior:** Protects both vehicle and driver assignments. Defines device order, service cycles, command retries, and calendar checks. Explains durable intake, replay, and delayed-state behavior.
- **Staff+:** Defines authority across telemetry and operational stores. Sets enforceable delay and recovery limits. Handles device replacement, tenant isolation, service races, and capacity during replay.

Practice this question with an AI interviewer: https://sysround.com/practice/new?problem=fleet-management


---
SysRound (https://sysround.com) is an AI practice tool for system design interviews. It has a voice or typed AI interviewer and a shared whiteboard. At the end, you get feedback on each skill and a model answer. The AI feedback can be wrong.