Problem Statement: Corporate Fleet & Telematics Platform
Problem Statement: Corporate Fleet & Telematics Platform — corporate fleet interview depth
Problem Statement: Corporate Fleet & Telematics Platform
Design a corporate fleet management platform (Samsara/Geotab/Verizon Connect class) for operators running delivery vans, service trucks, and mixed commercial assets. The system ingests continuous telematics, powers a live fleet map, triggers maintenance workflows, and supports dispatch—not passenger marketplace matching.
| Concern | Design stance |
|---|---|
| Ingest truth | At-least-once with dedupe key device_id:ts:seq |
| Live map | AP layer in Redis GEO; stale samples greyed |
| Operations CP | Postgres for vehicles, jobs, work orders |
| Compliance | Append-only audit for ELD/speed events |
Section focus (sec-001): B2B fleet operators need live vehicle state, maintenance compliance, and dispatch—not consumer ride matching.
Capacity signal: 85K connected assets; 12K GPS samples/s sustained; 48K dispatcher websocket subscribers
1 public record TelemetryKey(String deviceId, long sampleEpochMs, int seq) {}
1 def dedupe_key(device_id: str, ts_ms: int, seq: int) -> str: 2 return f"{device_id}:{ts_ms}:{seq}"
1 export function isStaleFix(tsMs: number, nowMs: number, maxAgeMs = 30000): boolean { 2 return nowMs - tsMs > maxAgeMs; 3 }
Operational trace (sec-001)
OBD gateway batches GPS + DTCs → ingest LB → Kafka → stream processor → Redis live map + Timescale history.
On-call metrics: ingest_lag_p95_ms, map_tile_staleness_pct, open_critical_dtc_count — page when ingest lag p95 > 30s or critical DTC notify delay > 2m.
Interview pivot: If interviewer conflates with Uber, separate telematics firehose from trip marketplace QPS.
Why interviewers care
a Corporate Fleet Management System interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.
Interview checkpoint
Name one failure story for Problem Statement: Corporate Fleet & Telematics Platform that proves you understand real outages, not happy-path diagrams.
Key Highlights
- •Multi-tenant org_id isolation (sec-001-0)
- •Telemetry dominates CRUD QPS (sec-001-1)
- •Maintenance work orders need CP semantics (sec-001-2)
- •ELD/HOS compliance as audit path (sec-001-3)
Section Rescue Kit
Buzzwords to use:
Safe statements:
- "Before databases on Problem Statement: Corporate Fleet & Telematics Platform, I'll quantify telemetry QPS and choose live vs history stores."
- "MVP is fleet truth + maintenance—not consumer ride matching."