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 11 of 12
Evolve a quoting module as partner contracts diverge, while keeping calculations reproducible and abstractions proportional to the problem.
Build a bounded browser editor whose tree operations, history, subscriptions, and exports remain coherent under failures and repeated use.
Support two incompatible notification providers while keeping domain decisions, instrumentation, and overload behavior explicit.
Replace a growing set of warehouse eligibility switches with a small, bounded rule language that support can inspect and engineers can evolve.
Evolve a long-lived account module while preserving tenant boundaries, client contracts, and a credible route back from partial migration.
Coordinate return inspection, replacement stock, and refunds across controllable provider boundaries while keeping uncertain outcomes visible.
Build a bounded arena with explicit alignment, lifetime and corruption behavior.
Implement bounded scheduling, cancellation and shutdown without hidden liveness failures.
Build framed IPC, bounded buffering, process lifecycle control and restart-safe request identity.
Implement decoding, stack safety, resource budgets and compatible bytecode revisions.
Design a safe FFI contract with explicit ownership, error mapping and compatibility.
Wrap files, timers and readiness notifications with explicit partial-result and portability behavior.
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.