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 79 of 115
Saving an incident and receiving its stream event produces duplicate activity rows. Correlate the committed operation.
Estimated field mix
A slow status screen accumulates unbounded events. Cap its queue and require reset when it cannot keep up.
Estimated field mix
A disconnected screen says All systems normal because incident cards retain their last values. Add transport freshness.
Estimated field mix
Investigating replay failures currently logs full incident descriptions. Add an allowlisted recovery event schema.
Estimated field mix
The prototype subtracts all historical holds and displays negative seats. Project availability from current authoritative states.
Estimated field mix
A zero-seat request creates a hold and a fractional request breaks counts. Enforce bounded integer quantities.
Estimated field mix
Two clients see one available seat and both reserve it. Serialize capacity consumption at storage.
Estimated field mix
Knowing a hold ID lets another user cancel it. Enforce owner scope in the repository boundary.
Estimated field mix
Confirm and expiry cleanup race, creating reservations from expired holds. Add an atomic transition with one time rule.
Estimated field mix
Timeout retry creates two holds for one user's click. Bind the operation key to the normalized request.
Estimated field mix
Clients see seats disappear for a transaction that later rolls back. Publish committed availability through an outbox.
Estimated field mix
Dropped socket messages leave the workshop full after holds expire. Detect version gaps and refresh a snapshot.
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.