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 10 of 115
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.
Estimated field mix
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.
Estimated field mix
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.
Estimated field mix
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.
Estimated field mix
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
138 matching projects · Page 12 of 12
Repair cache identity, cancellation, flaky checks, and feedback latency in a multi-package pipeline.
Replace rebuild-per-environment delivery with verified artifact promotion and reversible rollout.
Validate configuration, secret references, feature changes, and drift without copying sensitive values.
Create reproducible packages, provenance, signing boundaries, retention, and compromise recovery.
Define bootstrap, service readiness, data reset, offline behavior, and cross-platform parity.
Provision isolated previews with bounded cost, tenant-safe data, verified readiness, and deletion recovery.
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.