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 2 of 12
Repair public-service booking across keyboard use, zoom, timeouts, and changing availability.
Improve navigation, text adaptation, annotations, and revision recovery in an internal document reader.
Build a bounded live coordination room with ordered events, reconnect recovery, and clear authority.
Reconcile synthetic vehicle locations, assignment changes, and stream interruptions in an operations dashboard.
Build a local release assistant that prepares reviewable plans and survives interrupted release steps.
Shorten a local monorepo check loop while retaining correctness when inputs, dependencies, or tools change.
Build a deterministic checkout regression suite around pricing, accessibility, payment failures, and isolated test data.
Create a local webhook laboratory that reproduces duplicates, disorder, signature failures, and interrupted delivery.
Build a retrieval workflow that respects document access, cites exact revisions, and declines unsupported answers.
Build a routing assistant that suggests queues, validates model output, and preserves accountable human corrections.
Build a vendor inventory connector with stable identity mapping, resumable ingestion, reconciliation, and tenant-safe operations.
Build a calendar booking workflow with time-zone rules, conflict handling, idempotent provider calls, and safe reconnect 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.