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 43 of 115
A read for revision 7 starts before an edit, then finishes after revision 8 has already been cached and overwrites it.
Estimated field mix
An old invalidation arrives after a fresh fill and deletes valid data, triggering avoidable refresh work across instances.
Estimated field mix
A popular product expires and every API instance refreshes it simultaneously, increasing pressure on the source database.
Estimated field mix
A Redis outage makes every request retry repeatedly, overwhelming the authoritative database while users wait.
Estimated field mix
A new release changes product projection shape while old and new API instances share cached envelopes.
Estimated field mix
The dashboard shows a high hit rate as proof the product data is correct, though hit count says nothing about revision freshness.
Estimated field mix
A root compiler change passed CI although an unchanged package no longer compiled. Inventory inputs the planner must treat as shared.
Estimated field mix
The planner must inspect an unfamiliar checkout without triggering install hooks or repository commands.
Estimated field mix
Two shared packages depend on each other through development tooling, and recursive traversal never finishes.
Estimated field mix
A package deletion disappears from the current workspace map and incorrectly produces an empty plan.
Estimated field mix
Maintainers cannot review a large affected set because the tool prints only package names.
Estimated field mix
Generated client code changed after a tool upgrade while the cache reused an old successful result.
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.