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.
50 matching tickets · Page 2 of 5
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
5 matching projects · Page 1 of 1
Evolve a partner API with explicit compatibility, deprecation, and client migration contracts.
Design bulk record imports with explicit operation state, item errors, and recovery semantics.
Expose a changing catalog through bounded filters, stable cursors, and explicit consistency.
Design scoped partner credentials with revocation, safe errors, and client lifecycle controls.
Expose event subscriptions with immutable envelopes, bounded delivery, and safe replay.
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.