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.
The assignment list looks ready in the depot, but opening a work order downstairs produces an endless spinner. Distinguish listed work from fully downloaded details.
A technician takes an equipment photo, answers a phone call, and returns to a blank attachment tile. The draft stored a temporary camera URI that no longer exists.
Dispatch reassigns a job while the original technician is underground. That device later uploads completion against the old assignment. Preserve the technician’s work while honoring current server authority.
One 12 MB equipment photo repeatedly fails halfway through and blocks all completed visits. Integrate the resumable-upload contract and isolate attachment progress from unrelated operations.
Two technicians share a tablet between shifts. Sign-out currently leaves cached addresses for the next user, but blindly deleting storage would also erase unsynced repairs.
Depot support cannot distinguish a device waiting for Wi-Fi from one stuck on an expired upload. Add an account-local sync health page and a safe support bundle.
Central Station becomes Central Exchange in a feed update and a saved commute disappears. Save journeys by station identity and let riders keep a personal label.
A Saturday service departing after midnight appears under Sunday and disappears from the late-night search. The feed expresses service-day times beyond 24:00.
Handle deep links, expired sessions, and interrupted navigation using local identity stubs.
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.