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 69 of 115
Creating many client keys bypasses a per-key request limit.
Estimated field mix
Organization owners cannot see who expanded a client scope.
Estimated field mix
Existing integrations depend on broad keys and cannot all migrate at once.
Estimated field mix
Documentation encourages hardcoding keys and retrying every unauthorized response.
Estimated field mix
Event payloads mirror internal shipment rows and change whenever the schema changes.
Estimated field mix
A caller can subscribe its endpoint to another organization's shipment events.
Estimated field mix
An arbitrary callback URL could direct the sender toward unapproved network resources.
Estimated field mix
Partners cannot verify signatures after the sender serializes the same event differently on retry.
Estimated field mix
The platform advertises one delivery even though connection loss can cause duplicates.
Estimated field mix
The sender retries every response indefinitely, including malformed-endpoint failures.
Estimated field mix
Partners assume events arrive in the order they happened, but parallel delivery reorders them.
Estimated field mix
Support repairs a payload during replay and leaves the same event ID representing different facts.
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.