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 64 of 115
Adding a new CA to the trust store accidentally imports every certificate from a shared bundle.
Estimated field mix
A revoked peer retains a long-lived authenticated connection.
Estimated field mix
A long overlap helps slow clients but extends acceptance of old credentials.
Estimated field mix
On-call staff need a safe response when one peer fails certificate validation.
Estimated field mix
The importer accepts any URL beginning with a trusted-looking string.
Estimated field mix
User-info syntax and encoded separators confuse destination checks.
Estimated field mix
An approved hostname resolves to an address outside the permitted destination range.
Estimated field mix
An approved endpoint redirects the importer to an unapproved destination.
Estimated field mix
A response exceeds memory limits before its declared size can be checked.
Estimated field mix
Each redirect gets a fresh timeout, extending one import indefinitely.
Estimated field mix
The importer trusts a response header and sends arbitrary bytes to the wrong parser.
Estimated field mix
An endpoint is removed from policy but previously queued work still fetches it.
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.