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 107 of 115
A producer signals just before a worker begins waiting; queued work then sleeps until another submission arrives.
Estimated field mix
A cancelled indexing job resolves the same completion channel as a finished job, so callers publish an empty index.
Estimated field mix
A continuous stream of interactive jobs keeps cache-maintenance tasks queued indefinitely.
Estimated field mix
The worker holds the queue lock while acquiring a result lock; the joining thread holds the result lock while closing the queue.
Estimated field mix
A lock-free experiment publishes a slot index before all job fields are visible, producing rare partially initialized reads on a weakly ordered target.
Estimated field mix
Shutdown closes submissions but waits forever for a worker blocked on an external test double that never returns.
Estimated field mix
A rare stall produces per-poll logs from every worker, changing timing and obscuring the last useful state transition.
Estimated field mix
A build tool and a request server both plan to reuse the pool despite different fairness, blocking, and shutdown requirements.
Estimated field mix
A diagnostic string contains a newline and splits one response into two apparent messages.
Estimated field mix
A child inherits the supervisor listener and keeps it open after the parent exits, preventing clean restart.
Estimated field mix
Two conversions finish in reverse order and the supervisor resolves the first waiter with the second result.
Estimated field mix
A library warning written to stdout is parsed as a reply and closes the worker connection.
Estimated field mix
138 matching projects · Page 6 of 12
Reconcile local order state with a simulated provider under duplicate and delayed delivery.
Keep customer records consistent across a local application and a simulated CRM.
Reconcile availability and event changes across a scheduling app and a local calendar provider.
Define customer-facing reliability indicators and actionable budget policies.
Diagnose and recover delayed background work without duplicating effects.
Verify that database and object-store backups can reconstruct a coherent service.
Protect essential reads when optional workloads saturate a service.
Prepare a small service for a predictable launch surge through capacity and dependency review.
Make storage growth and transfer costs inspectable without compromising retained records.
Validate infrastructure changes as bounded plans with drift and recovery context.
Replace static service credentials with bounded workload identity and tested rotation.
Promote immutable application artifacts through environments with inspectable provenance.
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.