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 23 of 115
An unusually broad rule set makes checkout evaluate thousands of predicates per item and blocks unrelated quotes.
Estimated field mix
A shared cache returns one customer's negotiated rate to another account requesting the same product list.
Estimated field mix
Sales wants to explain an unmet minimum quantity, but the current debug endpoint exposes every account's price rules.
Estimated field mix
A promotion revision fixes bulk orders but may unintentionally discount small carts.
Estimated field mix
A reviewer approves a draft while an editor changes its discount; publication currently activates content nobody reviewed.
Estimated field mix
Support receives a disputed total after three rule releases and cannot reproduce which calculation the buyer accepted.
Estimated field mix
Operators see a failed file name but cannot identify the original bytes or the parser version used.
Estimated field mix
A tiny compressed batch expands far beyond the ingestion worker's memory budget.
Estimated field mix
Two device models emit watt-hours and kilowatt-hours under the same field name.
Estimated field mix
A process dies after inserting rows but before marking the file complete; replay doubles reported usage.
Estimated field mix
A malformed timestamp makes the ingestion job fail with a stack trace and no indication of the source row.
Estimated field mix
A device sends a corrected cumulative reading two days late; a blind upsert destroys the value used in yesterday's report.
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.