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.
50 matching tickets · Page 2 of 5
The journey card distinguishes Line 4 from Line 8 only by color. Riders using grayscale or a screen reader cannot tell where to change.
Estimated field mix
The departures screen keeps displaying an old prediction after a feed outage. A rider mistakes a 12-minute-old estimate for a live arrival.
Estimated field mix
Canceling the 08:10 Line 4 also marks tomorrow’s 08:10 as canceled because the cache key contains only the route. Reconcile alerts by departure identity.
Estimated field mix
Opening several saved journeys starts several permanent refresh loops. The app continues polling all of them in the background and occasionally displays the wrong result.
Estimated field mix
A rider enables a reminder after denying notifications, then assumes an alert will arrive. Rescheduled departures also leave the old reminder behind.
Estimated field mix
A timetable refresh replaces station and trip data while a route calculation still reads the old version. The result combines a new platform with a removed connection.
Estimated field mix
The first screen demands location before showing any journeys. A rider who declines cannot search by station even though the timetable supports it.
Estimated field mix
Most checks cover a clean daytime trip. Before the pilot, rehearse a saved late-night commute through feed outage, cancellation correction, and app restart.
Estimated field mix
Visit notes appear an hour early after an emulator zone change. Distinguish stored instants from displayed local times.
Estimated field mix
An offline refresh replaces the route with an empty screen. Retain downloaded visits and identify staleness.
Estimated field mix
Back navigation occasionally loses the last sentence. Commit local edits before acknowledging navigation.
Estimated field mix
The same offline note uploads twice after a timeout. Persist an operation ID alongside each queued change.
Estimated field mix
5 matching projects · Page 1 of 1
Keep assigned maintenance work usable without reception and reconcile changes safely when connectivity returns.
Make saved journeys, departures, and service alerts useful when feeds or device permissions change.
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.
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.