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 63 of 115
A slow upstream creates an unlimited queue behind a finite connection pool.
Estimated field mix
A cancelled report download continues consuming upstream bandwidth.
Estimated field mix
The proxy retries a POST after its connection breaks, potentially duplicating a write.
Estimated field mix
Buffering simplifies upstream retries but large reports exhaust proxy memory.
Estimated field mix
Configuration reloads close active report streams immediately.
Estimated field mix
Operators need to distinguish header rejection, pool waiting, and upstream disconnects.
Estimated field mix
A certificate signed by the internal CA is accepted for any service name.
Estimated field mix
A workaround accepts self-signed certificates by disabling all verification.
Estimated field mix
Renewal is noticed only when connections begin failing.
Estimated field mix
Long-lived connections keep using the old client identity after new credentials are loaded.
Estimated field mix
Handshake errors include large diagnostic objects containing sensitive material.
Estimated field mix
Routine renewal should not require every client to restart simultaneously.
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.