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 67 of 115
A timeout after admission causes the partner to submit the same catalog import again.
Estimated field mix
An item conflict response includes details about a catalog record owned by another tenant.
Estimated field mix
A worker restart reapplies successful items and duplicates side effects.
Estimated field mix
Clients assume cancelling an import undoes all previous item updates.
Estimated field mix
Large result lists exceed response limits and change order while the client reads them.
Estimated field mix
The UI computes ninety-nine percent from queued jobs even when several items are unresolved.
Estimated field mix
Some imports contain parent and child catalog records, making arbitrary independent item processing unsafe.
Estimated field mix
Partners have only a happy-path example that treats HTTP acceptance as completion.
Estimated field mix
Different clients interpret date ranges and empty status lists differently.
Estimated field mix
Clients can pass arbitrary sort expressions into query construction.
Estimated field mix
An optional organization filter can replace the caller's tenant predicate.
Estimated field mix
A cursor from one status filter is reused with another and skips records.
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.