Preparing the next view without exposing private workflow data.
Engineering task library · Version 5
Work that feels like work.
Design a system. Diagnose tail latency. Ship a migration. Recover a failed rollout. Pick a focused ticket or follow a project through its delivery phases.
A synthetic depot near the date line has vans at longitudes 179.8 and -179.7. Fit selection zooms to the whole world because the bounding box takes the long route.
A device buffers updates through a tunnel, then sends them out of order. The marker jumps to an older point and the arrival-age label resets incorrectly.
The dashboard downloads a vehicle snapshot and opens the live stream afterward. Updates during that gap never arrive, so a van appears stale until its next fix.
A dispatcher moves from North depot coverage to East, but an existing stream continues delivering North vehicle coordinates. Hidden markers remain in the browser store.
Dispatch needs to know what remains usable when telemetry stops but assignment storage still works. Write a fixed-data outage rehearsal and an operator decision note.
Coordinate expiring seat holds and live availability in a local simulation.
10 tickets · 3 phases
Take the brief into your own workflow.
For engineers
Practice scoped changes, keep a portable implementation and verification record, and learn to explain operational tradeoffs. Choose a ticket whose prerequisites you can provide.
For companies
Use realistic work to structure onboarding, internal practice, and conversations about engineering decisions. Each project names the delivery benefit. Agree scope and compensation before requesting company-specific work.
CSV contains one row per ticket. Map fields and issue types in your tracker; project grouping and dependency keys are descriptive. JSON preserves the complete project structure. These downloads do not synchronize with Jira.