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 36 of 115
Rows marked assigned sometimes have no assignee or lease deadline, making recovery ambiguous.
Estimated field mix
Jobs created at the same instant appear in a different order on each poll, making starvation difficult to reproduce.
Estimated field mix
The job list is scoped in the controller, but the claim repository accepts a globally valid job ID.
Estimated field mix
Two polling clients select the same pending job before either writes its assignment.
Estimated field mix
A disconnected reviewer reconnects after its job was reassigned and still holds a token that appears current.
Estimated field mix
A late heartbeat runs after completion and changes the row back into an apparently active assignment.
Estimated field mix
A result is visible while its job remains assigned because completion and result linking commit separately.
Estimated field mix
A sweep selects expired jobs, then reclaims one that was renewed before its update executes.
Estimated field mix
Operators need to choose a polling interval and concurrency limit based on observed contention in the local prototype.
Estimated field mix
After an outage, operators need to resume assignments without redoing completed work or accepting stale reviewer results.
Estimated field mix
A test restore contains tables but cannot start the application because expected roles and extensions are absent.
Estimated field mix
Operators find three similarly named dump files and cannot tell which migration version or time each represents.
Estimated field mix
138 matching projects · Page 4 of 12
Turn a document-processing brief into reviewable boundaries, contracts and failure probes.
Specify consistency, routing and recovery for a regional customer read experience.
Separate notification intent, delivery attempts and user-visible receipt semantics.
Choose storage, indexing and deletion semantics for a bounded audit archive.
Define fair scheduling, bounded work and recovery for a report service.
Replace a legacy customer key through additive schema changes and verified backfill.
Claim, renew and finish work without duplicate authority or stranded assignments.
Build a bounded backup inventory and rehearse restoration with consistency checks.
Make cross-organization relationships impossible through database and repository constraints.
Separate stable document fields from versioned bounded metadata and migrate safely.
Elect one active scheduler while preventing expired owners from mutating shared state.
Recover a multi-step return workflow across inspection, shipping and refund providers.
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.