Reject stale stock updates without losing drafts
Two buyers edit the same row and the second overwrites the first. Handle revision conflicts.
Estimated field mix
- Frontend60%
- API design40%
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.
60 matching tickets · Page 3 of 5
Two buyers edit the same row and the second overwrites the first. Handle revision conflicts.
Estimated field mix
Arrow keys sometimes move cells while users edit text. Introduce explicit navigation and editing states.
Estimated field mix
A blind Undo would erase a colleague's newer stock value. Add one guarded inverse update.
Estimated field mix
A spreadsheet paste includes headers and an extra column. Show its target mapping before writing.
Estimated field mix
Bulk edit says Saved when one row failed. Return stable per-row outcomes.
Estimated field mix
Support needs grid state but copying rows exposes inventory. Add an opt-in diagnostic download.
Estimated field mix
Repeated spaces create separate search requests. Define normalization without altering case-sensitive part codes.
Estimated field mix
Shared search links conceal which filters excluded parts. Render removable facets from validated URL values.
Estimated field mix
A live region reads counts after every keystroke. Announce committed search outcomes without moving focus.
Estimated field mix
More results races with facet changes and appends unrelated products. Scope pages to query identity.
Estimated field mix
Returning from a part detail resets a long search to the top. Restore the visited item.
Estimated field mix
An old part bookmark renders a blank page. Distinguish removal from failed loading.
Estimated field mix
6 matching projects · Page 1 of 1
Repair queue navigation, reply composition, and agent handoffs in a customer support workspace.
Make purchase requests accurate, recoverable, and reviewable across revisions.
Make spreadsheet-like stock editing predictable across validation and concurrent updates.
Build navigable search and result recovery for a public directory.
Repair conditional fields, draft recovery, and deliberate submission.
Build a bounded browser editor whose tree operations, history, subscriptions, and exports remain coherent under failures and repeated use.
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.