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.
60 matching tickets · Page 4 of 5
A deleted record reappears when an old update is replayed.
Estimated field mix
Support needs to find mismatches without exporting every contact's personal data.
Estimated field mix
A corrupted cursor requires a new import while staff continue editing customer records.
Estimated field mix
Support sees only 'sync failed' and repeatedly restarts imports.
Estimated field mix
An all-day absence becomes a twenty-four-hour UTC interval and shifts across local dates.
Estimated field mix
A recurring appointment lands in a nonexistent local hour during a timezone transition.
Estimated field mix
An unbounded recurrence rule exhausts the availability request.
Estimated field mix
An old series update recreates a cancelled individual appointment.
Estimated field mix
The provider invalidates a sync token, and the app interprets it as an empty calendar.
Estimated field mix
Availability responses leak private appointment titles to bookers.
Estimated field mix
Revoked calendars remain cached and continue receiving background refreshes.
Estimated field mix
Two bookers see the same open slot before either reservation is committed.
Estimated field mix
6 matching projects · Page 1 of 1
Build a vendor inventory connector with stable identity mapping, resumable ingestion, reconciliation, and tenant-safe operations.
Build a calendar booking workflow with time-zone rules, conflict handling, idempotent provider calls, and safe reconnect behavior.
Reconcile local order state with a simulated provider under duplicate and delayed delivery.
Keep customer records consistent across a local application and a simulated CRM.
Reconcile availability and event changes across a scheduling app and a local calendar provider.
Support two incompatible notification providers while keeping domain decisions, instrumentation, and overload behavior explicit.
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.