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 76 of 115
A line chart has only an image label reading Chart. Add a concise summary sourced from the displayed series.
Estimated field mix
Sticky styling replaced table headers with generic containers. Restore native table relationships.
Estimated field mix
Missing intervals are graphed at zero and alter the apparent trend. Define equivalent chart and table representations.
Estimated field mix
Column sorting works only by clicking an unlabeled header. Add named buttons and current sort direction.
Estimated field mix
Invalid date ranges produce a toast that disappears before users reach the fields. Add persistent linked errors.
Estimated field mix
Selecting a chart interval requires dragging across the plot. Add equivalent start/end interval controls.
Estimated field mix
Expanded row details unmount during scrolling and leave focus nowhere. Bound virtualization around active interaction.
Estimated field mix
A completed export opens a modal and interrupts filter editing. Expose a stable download action with a status message.
Estimated field mix
Report lines and selected rows vanish under forced colors. Add structural distinctions using patterns and borders.
Estimated field mix
The team cannot verify that the chart alternative carries the same decisions. Execute a defined fixture-based comparison.
Estimated field mix
Screen readers announce Dialog without a purpose. Connect each settings dialog to its visible heading.
Estimated field mix
Toast close icons have no accessible name and cannot receive focus. Add an explicit dismissal control.
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.