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 68 of 115
Pagination drops shipments when several rows have the same update timestamp.
Estimated field mix
A shipment changes status between pages, and partners expect a snapshot the endpoint never promised.
Estimated field mix
A fast first page still waits for an expensive exact count.
Estimated field mix
A permitted filter scans every shipment despite bounded page size.
Estimated field mix
The client SDK retries invalid cursors forever instead of telling callers to restart.
Estimated field mix
Partners use an interactive list endpoint as if it were a financial or audit export.
Estimated field mix
A single automation scope permits every operation in the organization.
Estimated field mix
A valid credential can be paired with another organization ID in the URL.
Estimated field mix
Partners can distinguish nonexistent records from records belonging to another organization.
Estimated field mix
The parent resource is authorized, but nested record IDs bypass tenant checks.
Estimated field mix
Customers need rotation overlap, but old keys remain valid forever.
Estimated field mix
Revoked clients retain access until a long cache TTL expires.
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.