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 8 of 115
An agent navigating by keyboard loses their place after closing ticket details. Define focus behavior for opening, closing, and removing the selected row.
Estimated field mix
Two leads assign the same ticket within a second. One console displays its optimistic assignment forever even though the API rejected the stale revision.
Estimated field mix
Closing 25 conversations returns 22 successes, two permission denials, and one revision conflict. Today a green toast appears and every selected row disappears.
Estimated field mix
The server accepts a reply, but Wi-Fi drops before acknowledgement. Clicking Send again duplicates the email. Model an uncertain result and recover through operation lookup.
Estimated field mix
An 800-message synthetic conversation makes expanding attachments slow. Reduce initial rendering while preserving chronological reading and position when older messages load.
Estimated field mix
On-call receives screenshots saying It stopped working with no clue whether loading, assignment, or sending failed. Add redacted diagnostics and a release handoff.
Estimated field mix
An incomplete request produces only Invalid request. Add field feedback and an error summary for vendor, business reason, and delivery date.
Estimated field mix
Three items at 19.99 sometimes display extra decimal digits. Finance also found a preview total that differed from the payload after a quantity edit.
Estimated field mix
Selecting Marketing / Events and then changing to Engineering leaves Events hidden in the payload. The reviewer has to send the request back.
Estimated field mix
A requester edits quantities in one tab and the explanation in another. Background autosave overwrites whichever tab saved first.
Estimated field mix
Quotes look attached immediately even though the upload service can reject or quarantine them. Requesters submit before learning the reviewer cannot open the PDF.
Estimated field mix
After clarification, a requester changes both the explanation and amount. The review page says Updated without identifying which lines changed.
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.