Record first-attempt results separately from rerun results
A green rerun erases the original failure from the summary.
Estimated field mix
- Quality engineering100%
Loading noCV…
Preparing the next view without exposing private workflow data.
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 46 of 115
A green rerun erases the original failure from the summary.
Estimated field mix
One test fails only after a preference-setting test runs first.
Estimated field mix
An integration test reads records inserted by an earlier test and passes for the wrong reason.
Estimated field mix
A trial-expiry test fails around UTC midnight and daylight-saving changes.
Estimated field mix
A fixed delay is either too short on CI or unnecessarily long locally.
Estimated field mix
Background polling continues after a test completes and changes the next test's state.
Estimated field mix
An unavailable local dependency and an incorrect application response currently look identical.
Estimated field mix
Quarantined tests have accumulated without owners or a return date.
Estimated field mix
Twenty green reruns are being presented as proof that a defect is gone.
Estimated field mix
New contributors copy retry-heavy tests and perpetuate the same failure patterns.
Estimated field mix
The existing contract copies entire sample responses, making harmless changes fail.
Estimated field mix
Contracts depend on whichever orders happen to exist in a shared test database.
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.