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 93 of 115
A client disconnects after its deadline, but the carrier lookup continues and consumes one of the few available connections.
Estimated field mix
Multi-stop quotes fan out immediately. A burst exhausts the carrier stub connection pool and slows unrelated single-stop traffic.
Estimated field mix
The largest multi-stop responses correlate with event-loop delay. The team has proposed adding workers before confirming where time is spent.
Estimated field mix
At overload, a larger queue increases completed work but most quotes arrive after the dispatch screen has already given up.
Estimated field mix
A promising result came from a generator sharing the API CPU quota. It slowed its own arrivals and reported a workload the service never received.
Estimated field mix
The team can demonstrate one fast run, but it has no rule for accepting noisy results or reverting a change that prices correctly only at low concurrency.
Estimated field mix
The existing fixture spreads rows evenly across tenants. It cannot reproduce the large account whose open-work view is slow.
Estimated field mix
The ticket says the query takes seconds but contains no plan, parameters or indication of whether the cache was warm.
Estimated field mix
The main SQL query is quick, but the API loads the latest assignee separately for every visible work order.
Estimated field mix
Fetching one assignee per work order makes latency increase with page size even after the main inbox query is tuned.
Estimated field mix
Only a small fraction of work orders remain open. A broad index makes the open inbox faster but adds substantial storage and maintenance cost.
Estimated field mix
An operator reaches old open work through hundreds of pages. Each offset request scans and discards an increasing number of matching rows.
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.