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 28 of 115
The staging build passes, but production rebuilds the same commit with different transitive dependencies.
Estimated field mix
A scan service times out and the build pipeline treats absence of findings as a clean result.
Estimated field mix
A CI runner loses the promotion response and retries, creating competing rollout records for one digest.
Estimated field mix
Registry cleanup removes an image still running in a quiet environment because its tag is old.
Estimated field mix
A new runtime starts successfully but fails on records created by the previous release.
Estimated field mix
Incident responders receive three different tag names for what appears to be the same release.
Estimated field mix
A token marked read-only can still trigger an export job because the handler treats every authenticated token equally.
Estimated field mix
The token-management page retrieves complete credentials from the database every time an administrator opens it.
Estimated field mix
An export identifier from another organization succeeds because the service checks token validity but omits tenant scope.
Estimated field mix
A token expires in storage but remains usable because the cached authentication result has no expiry check.
Estimated field mix
Customers need to replace credentials without downtime, but unrestricted overlap leaves old tokens valid indefinitely.
Estimated field mix
An administrator revokes a leaked token, but one process continues accepting its cached authority.
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.