Task library FLEET Real-time systems · Phased project A dispatch map that does not invent certainty The fictional Cedar delivery depot dispatches vans through a browser map and accessible list. Synthetic telemetry arrives through a gateway with device sequence numbers. This is operational fleet software practice; no real driver tracking, employee scoring, or routing safety guarantee is part of the project.
Practice brief · Version 5
Project scope 10 tickets / 4 phases
Total focused work estimate 23h + setup
Suggested stack TypeScript · React · MapLibre · Node.js · PostgreSQL Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with FLEET-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice geospatial boundaries, stream ordering, snapshot recovery, and concurrent operational commands.
What the team gains Inspect whether a developer keeps dispatch decisions grounded in current authorized data and exposes uncertainty during outages.
Before you start Synthetic vehicle telemetry with device sessions and sequence numbers Dispatch assignment and authorized region API contracts Delivery agreement Use a fixed synthetic depot and replayable location traces. Each ticket is independently bounded by its declared prerequisites.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Validate coordinates and show age and identity clearly.
PHASE 2 Handle device ordering and reconnect boundaries.
PHASE 3 Keep assignments, filters, and access consistent.
PHASE 4 Maintain responsiveness and verify failure recovery.
Establish a truthful map Validate coordinates and show age and identity clearly.
FLEET-101 Entry ticket; project setup still required Estimated field mix
Data engineering 40% Real-time systems 30% Frontend 30% FLEET-102 Depends on FLEET-101 Estimated field mix
Real-time systems 60% Frontend 40% FLEET-103 Depends on FLEET-101 Reconcile live telemetry Handle device ordering and reconnect boundaries.
FLEET-104 Depends on FLEET-102 Estimated field mix
Real-time systems 70% Data engineering 30% FLEET-105 Depends on FLEET-103, FLEET-104 Estimated field mix
Real-time systems 60% Distributed systems 40% Support operational decisions Keep assignments, filters, and access consistent.
FLEET-106 Depends on FLEET-105 Estimated field mix
Real-time systems 40% Backend 30% Frontend 30% FLEET-107 Depends on FLEET-102, FLEET-106 Estimated field mix
Frontend 60% Real-time systems 20% Accessibility 20% FLEET-108 Depends on FLEET-105, FLEET-106 Estimated field mix
Security 40% Real-time systems 30% Privacy engineering 30% Bound and rehearse the system Maintain responsiveness and verify failure recovery.
FLEET-109 Depends on FLEET-104, FLEET-107, FLEET-108 Estimated field mix
Performance engineering 50% Real-time systems 30% Frontend 20% FLEET-110 Depends on FLEET-105, FLEET-106, FLEET-108, FLEET-109 Estimated field mix
Real-time systems 40% Site reliability 30% Quality engineering 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.