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 2 of 115
Two checkouts both read one remaining wheelset before either writes a reservation. Both succeed, leaving the warehouse with available stock of minus one.
Estimated field mix
A flaky mobile connection retries the reserve call every minute. Each retry adds another ten minutes to the hold and can change the requested quantity.
Estimated field mix
Payment confirmation and the expiry sweeper reach reservation R-42 at the same instant. Today both handlers succeed and a paid order loses its stock.
Estimated field mix
An order for a cassette and chain reserves the cassette, then fails on the chain. The abandoned partial hold blocks another buyer for ten minutes.
Estimated field mix
A warehouse count finds two damaged lights while three lights are reserved. Operations needs to record the loss without silently cancelling customer holds.
Estimated field mix
The old table has one quantity per SKU. The East/West launch needs a warehouse key, but a one-shot table rewrite blocks checkout on the large synthetic inventory fixture.
Estimated field mix
The product page shows an old available count for five minutes after a warehouse adjustment. A failed adjustment also evicts unrelated retailers' cached stock.
Estimated field mix
Support needs to explain why an order lost its hold. The current workaround is database access that exposes customer addresses and permits accidental stock edits.
Estimated field mix
A 200-event batch contains one scan with an empty parcel reference. The importer rejects all 200, leaving valid deliveries invisible until the next carrier export.
Estimated field mix
Support found a delivery scan that neither carrier recognizes. The normalized table contains no batch hash, row position, or parser version to trace its origin.
Estimated field mix
Carrier Cedar retries yesterday's batch. Most event IDs are identical, but one delivery timestamp changed from 14:03 to 14:30 and is overwritten silently.
Estimated field mix
A carrier sends 2025-11-02 01:30 in its configured New York time zone. The importer guesses one occurrence during the clock change and displays delivery before pickup.
Estimated field mix
138 matching projects · Page 1 of 12
Reconcile payment settlements against invoice records without hiding money movement or retry failures.
Build reservation and allocation behavior for a small retailer with two warehouses and unreliable checkout retries.
Ingest delayed, duplicated, and corrected parcel events into an explainable tracking timeline.
Replace a fragile daily sales query with versioned, reconcilable warehouse metrics.
Build a release workflow that can distinguish a healthy process from a safe application version.
Operate an asynchronous document pipeline through retries, poison jobs, worker loss, and tenant bursts.
Make partner access explicit across list APIs, batch commands, invitations, cached sessions, and exports.
Introduce explicit credential versions, safe rotation, redacted diagnostics, and recovery for a webhook integration.
Repair queue navigation, reply composition, and agent handoffs in a customer support workspace.
Make purchase requests accurate, recoverable, and reviewable across revisions.
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.
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.