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 71 of 115
Repeated spaces create separate search requests. Define normalization without altering case-sensitive part codes.
Estimated field mix
Shared search links conceal which filters excluded parts. Render removable facets from validated URL values.
Estimated field mix
A live region reads counts after every keystroke. Announce committed search outcomes without moving focus.
Estimated field mix
More results races with facet changes and appends unrelated products. Scope pages to query identity.
Estimated field mix
Returning from a part detail resets a long search to the top. Restore the visited item.
Estimated field mix
An old part bookmark renders a blank page. Distinguish removal from failed loading.
Estimated field mix
Selected filters disappear when counts reach zero, trapping the query. Separate selection from availability.
Estimated field mix
Browsing many searches grows memory indefinitely. Introduce capacity and expiry with deterministic eviction.
Estimated field mix
Printed shortlists include removed entries. Use a dedicated projection resolved by current item IDs.
Estimated field mix
Search failure metrics currently include potentially sensitive part queries. Add bounded operational events.
Estimated field mix
Entered 19.90 becomes 19.9 and later rounds. Separate edit text from validated minor units.
Estimated field mix
Required fields missing gives no location. Add field errors and a navigable summary.
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.