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 57 of 115
Slow registration is blamed on SQL even when requests are waiting for a connection.
Estimated field mix
A network interruption causes clients to resubmit successful registrations.
Estimated field mix
A slow notification provider makes accepted registrations appear failed.
Estimated field mix
A database write outage should not make the entire course catalog disappear.
Estimated field mix
Every process warms the same popular course pages simultaneously after deployment.
Estimated field mix
The cheapest configuration passes average load but fails when one worker is unavailable.
Estimated field mix
Operators lack a shared decision point for pausing registration during a surge.
Estimated field mix
A green test report obscures that external quotas and target-environment recovery remain unverified.
Estimated field mix
Inventory exports mix byte counts, rounded sizes, and missing owners.
Estimated field mix
A storage-only estimate ignores the cost of regenerating and downloading exports.
Estimated field mix
A broad expiry rule would remove the only copy of finalized reports.
Estimated field mix
Operators cannot see which objects a new rule would affect.
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.