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 4 of 5
One large tenant fills every waiting slot and blocks smaller tenants.
Estimated field mix
The team must choose between a larger queue and earlier rejection.
Estimated field mix
Degradation switches on and off rapidly near the threshold.
Estimated field mix
Product support cannot explain which features disappear during overload.
Estimated field mix
The launch plan says 'ten times traffic' without a base rate or request mix.
Estimated field mix
The database pool and email adapter have different limits and failure semantics.
Estimated field mix
Slow registration is blamed on SQL even when requests are waiting for a connection.
Estimated field mix
A network interruption causes clients to resubmit successful registrations.
Estimated field mix
A slow notification provider makes accepted registrations appear failed.
Estimated field mix
A database write outage should not make the entire course catalog disappear.
Estimated field mix
Every process warms the same popular course pages simultaneously after deployment.
Estimated field mix
The cheapest configuration passes average load but fails when one worker is unavailable.
Estimated field mix
5 matching projects · Page 1 of 1
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.
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.