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 3 of 115
A DELIVERED scan arrives at 16:00, followed by a delayed PICKED_UP scan from 08:00. The tracking card switches back to In transit because it uses receipt order.
Estimated field mix
A driver scanned the wrong parcel as delivered. The carrier now sends corrections referencing the original scan; support must see why Delivered became In transit.
Estimated field mix
Parser v3 mislabeled ARRIVED_AT_DEPOT as DELIVERED. Operations needs to rebuild 100,000 synthetic scans while fresh batches continue arriving.
Estimated field mix
After an outage, one carrier sends a day's events in 30 seconds. Memory pressure restarts workers and the API cannot tell which batches were accepted.
Estimated field mix
Every worker is healthy, but Carrier Elm has not sent a batch since morning. No alert fires because all dashboards measure processing failures.
Estimated field mix
Carrier payloads contain recipient notes unnecessary after the exercise's 30-day debugging window. A cleanup script removes artifacts still used by an active replay.
Estimated field mix
Finance subtracts posted refunds from captured charges; product subtracts pending refunds too. Both dashboards use Net sales and disagree for merchant M-17.
Estimated field mix
The warehouse assumes order_id is globally unique, but two merchants both supplied order 7001. Daily deduplication keeps only one.
Estimated field mix
An order with three lines and two refunds becomes six joined rows. The daily mart counts each captured amount several times although the ledger is correct.
Estimated field mix
A 23:30 Los Angeles sale appears on tomorrow's report because the mart groups UTC dates. Merchants cannot reconcile their register totals.
Estimated field mix
M-17 upgrades from Starter to Growth in June. Joining today's merchant record moves all earlier revenue into Growth and rewrites quarterly comparisons.
Estimated field mix
The nightly job filters on order creation date. A refund posted today against a six-week-old order never reaches the mart.
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.