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 29 of 115
The rotation response is lost and a retry creates another active successor that the customer never receives.
Estimated field mix
Security needs failed-access context, but the existing logger captures the Authorization header and request body.
Estimated field mix
A fictional customer reports that a token was pasted into a public issue; operations needs a tested containment sequence.
Estimated field mix
Administrators interpret an empty last-used field as proof that a token was never used, despite audit ingestion gaps.
Estimated field mix
A customer enters a non-HTTP URI that the generic import library attempts to interpret as a local resource.
Estimated field mix
One tenant configures an approved host and another tenant unexpectedly inherits permission to fetch from it.
Estimated field mix
A public-looking hostname resolves to an internal address during import and reaches a service unavailable to the user.
Estimated field mix
An approved download host redirects to an unapproved internal URL after the first request passes validation.
Estimated field mix
A response declares a small Content-Length but streams indefinitely, occupying a worker slot.
Estimated field mix
A remote server labels an executable-looking payload as text and the importer publishes it under a trusted document type.
Estimated field mix
A response drops after storage completes; retry publishes a second document with a different identity.
Estimated field mix
A signed download URL appears in an operator error message after a timeout.
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.