Preparing the next view without exposing private workflow data.
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.
1380 tickets · 138 projects · 26 engineering fields · Four difficulty levels
Field counts and the engineering field filter use each project's primary field. Estimated ticket labels can span multiple fields.
1380 matching tickets · Page 9 of 115
A 15-second response prompts a refresh and second submission. Finance receives two approval requests. Coordinate submission identity with saved revisions and uncertain responses.
Estimated field mix
An approver leaves the page open past delegation expiry. Approve fails, but controls remain active and the page incorrectly labels the request handled.
Estimated field mix
At 200% zoom, a sticky total covers the final row and horizontal scrolling separates quantity inputs from labels. Fix the equipment-request layout.
Estimated field mix
Form tests passed, but the last release lost a quote when finance returned a request. Add a deterministic journey through return, edit, and resubmission.
Estimated field mix
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.
Estimated field mix
A technician checks Replace intake filter and force-closes the app. On reopening, the check is gone even though the screen showed Saved.
Estimated field mix
A technician increases system text size. Pass/Fail controls overlap equipment names, and the last input disappears beneath the keyboard.
Estimated field mix
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.
Estimated field mix
Finish visit is disabled with no explanation when a required reading or photo is missing. Technicians tap through every section to find the blocker.
Estimated field mix
Reception returns briefly and drops again during sync. The same completed visit is sent twice, while a later note disappears after a failed batch.
Estimated field mix
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.
Estimated field mix
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.
Estimated field mix
138 matching projects · Page 8 of 12
Build navigable search and result recovery for a public directory.
Repair conditional fields, draft recovery, and deliberate submission.
Keep synthetic visit notes reliable through offline use and process restarts.
Manage resumable public-content downloads and safe local playback state.
Handle deep links, expired sessions, and interrupted navigation using local identity stubs.
Make scheduling interactions operable with keyboard, magnification and assistive technology.
Give charts, sortable tables and exports equivalent understandable information.
Make dialogs, menus, toasts and nested workflows predictable across input methods.
Model ephemeral team presence with expiry, reconnects and scoped fan-out.
Keep a synthetic service-status board ordered and replayable over server-sent events.
Coordinate expiring seat holds and live availability in a local simulation.
Build a local multipart-upload coordinator with scoped identities and integrity checks.
Practice scoped changes, keep a portable implementation and verification record, and learn to explain operational tradeoffs. Choose a ticket whose prerequisites you can provide.
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.