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
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
An error spike starts near a deploy, but the dashboard has no release event or stable artifact link. Engineers compare screenshots and guess which change was live.
Estimated field mix
The release checklist says rollback tested, but nobody has timed recovery or tried it with an expanded database schema and pending worker jobs.
Estimated field mix
The portal shows Processing for both queued and permanently rejected documents. Support cannot tell whether a file is waiting, rendering, or never going to finish.
Estimated field mix
A client submits 50,000 document references in one call. Validation exhausts API memory before the queue sees a single job.
Estimated field mix
5 matching projects · Page 1 of 1
Build a release workflow that can distinguish a healthy process from a safe application version.
Operate an asynchronous document pipeline through retries, poison jobs, worker loss, and tenant bursts.
Validate, version and distribute runtime configuration with bounded staleness.
Provision bounded review environments with explicit ownership and cleanup.
Produce reproducible service images and promote exact artifacts 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.