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 22 of 115
A busy service desk loads every future slot; several slots disappear from the second page when a new slot is inserted.
Estimated field mix
Two customers reach checkout together and each receives a valid hold token for the same appointment.
Estimated field mix
An expiry worker reads an old hold while checkout confirms it; the worker then frees a slot already sold.
Estimated field mix
A reschedule releases the old appointment before reserving the new one, leaving customers unbooked if the target is taken.
Estimated field mix
A policy update changes the cancellation deadline for appointments sold under yesterday's terms.
Estimated field mix
A simulated outage leaves holds whose expiry jobs were never dispatched; operations needs a bounded reconciliation command.
Estimated field mix
A failed reschedule currently returns the target booking object, exposing the name and contact information of its owner.
Estimated field mix
Checkout commits successfully, then the connection closes. A customer retries while the expiry worker is also running.
Estimated field mix
Sales requested a formula textbox; evaluating arbitrary expressions would make quote behavior difficult to bound and audit.
Estimated field mix
Two promotions match the same part and the chosen discount depends on database return order.
Estimated field mix
A promotion with its end before its start passes draft review and can never apply.
Estimated field mix
A buyer accepts a quote after a promotion edit and receives a different total from the amount previously displayed.
Estimated field mix
138 matching projects · Page 12 of 12
Repair cache identity, cancellation, flaky checks, and feedback latency in a multi-package pipeline.
Replace rebuild-per-environment delivery with verified artifact promotion and reversible rollout.
Validate configuration, secret references, feature changes, and drift without copying sensitive values.
Create reproducible packages, provenance, signing boundaries, retention, and compromise recovery.
Define bootstrap, service readiness, data reset, offline behavior, and cross-platform parity.
Provision isolated previews with bounded cost, tenant-safe data, verified readiness, and deletion recovery.
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.