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 4 of 115
A noon backfill finishes after the nightly job. Its older snapshot overwrites May's newer partition and removes refunds received at 18:00.
Estimated field mix
A transformation passes SQL syntax checks while dropping one currency partition. The dashboard refresh succeeds and hides the revenue gap.
Estimated field mix
Removing merchant_id from an export request returns every merchant's sales because the support route passes filters directly to an analyst-wide query.
Estimated field mix
After a mart correction, May net sales changes and analysts need to know which rows moved. Build a synthetic before/after comparison and quantify the delta instead of assuming a target percentage.
Estimated field mix
Two API instances report version latest even though only one received yesterday's build. On call cannot connect a failing request to its deployed artifact.
Estimated field mix
A brief database outage makes the process liveness endpoint fail. The restart policy kills every API instance and turns a recoverable connection issue into a restart loop.
Estimated field mix
The new worker image needs STORAGE_REGION, but its environment is missing the setting. The rollout reports success while every document job fails on first use.
Estimated field mix
A migration renames booking.start to booking.starts_at before old API instances finish draining. Half the requests fail until every instance updates.
Estimated field mix
Two commits deploy simultaneously. The older job finishes last and marks its artifact current after the newer release already passed validation.
Estimated field mix
A release automatically promotes after five error-free canary requests while the stable version serves thousands. Low traffic makes an untested version look healthy.
Estimated field mix
During release, an instance exits halfway through a report download. The load balancer keeps sending new requests during its shutdown grace period.
Estimated field mix
Worker v8 enqueues a new payload shape. Rolling back to v7 starts a retry storm because v7 cannot parse jobs already accepted by v8.
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.