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.
50 matching tickets · Page 1 of 5
A customer rename updates its main row but leaves case and attachment references pointing to the old code.
Estimated field mix
The migration needs stable customer identity while current clients continue using external codes.
Estimated field mix
Case rows need the new relationship without requiring a single locking rewrite of the entire dataset.
Estimated field mix
A single UPDATE holds locks too long and cannot explain where to resume if the migration job stops.
Estimated field mix
Old clients create cases using a code while new clients use IDs; both must produce equivalent relationships during rollout.
Estimated field mix
A rename races a batch lookup and attaches a legacy case to the wrong customer when the old code is reused.
Estimated field mix
The team wants to mark new references non-null, but missing mappings are hidden by a dashboard that counts only completed batches.
Estimated field mix
Application checks pass, but a direct import can still create a case with an absent new customer identity.
Estimated field mix
The new writer is deployed, but detail routes still resolve mutable codes and can display the wrong record after a rename.
Estimated field mix
Dropping old columns would end binary rollback to old readers, but the release checklist does not mention that boundary.
Estimated field mix
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
5 matching projects · Page 1 of 1
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.
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.