Display workshop hold countdown as advisory
A client clock skew shows time remaining after the server expired the hold. Label countdown and reconcile server refusal.
Estimated field mix
- Frontend70%
- Real-time systems30%
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 80 of 115
A client clock skew shows time remaining after the server expired the hold. Label countdown and reconcile server refusal.
Estimated field mix
Cleanup scans every historical hold on each tick. Add bounded cursor batches with repeat-safe transitions.
Estimated field mix
The upload API accepts ambiguous separators and empty names. Define an opaque object-name contract.
Estimated field mix
A session ID can currently be reused against a different object. Require its original scope on every part operation.
Estimated field mix
The coordinator accepts an unlimited part list. Bound declared object size and per-session part count.
Estimated field mix
A timeout after part acceptance leads to duplicate receipts with different checksums. Bind retries to part number and digest.
Estimated field mix
Completion silently omits a middle part and produces a shorter object. Check the requested manifest before finalization.
Estimated field mix
Provider completion succeeds but the assembled bytes differ from the expected digest. Introduce a verification state.
Estimated field mix
A crash after provider completion leaves the session looking incomplete. Reconcile provider outcome without creating another object.
Estimated field mix
Abandoned sessions retain billable parts. Add expiry cleanup with a guarded session transition.
Estimated field mix
Progress reaches 100 percent before the provider accepts the final part. Count acknowledged bytes separately from verification state.
Estimated field mix
Support dumps provider receipts containing temporary access URLs. Add an allowlisted diagnostic projection.
Estimated field mix
138 matching projects · Page 2 of 12
Repair public-service booking across keyboard use, zoom, timeouts, and changing availability.
Improve navigation, text adaptation, annotations, and revision recovery in an internal document reader.
Build a bounded live coordination room with ordered events, reconnect recovery, and clear authority.
Reconcile synthetic vehicle locations, assignment changes, and stream interruptions in an operations dashboard.
Build a local release assistant that prepares reviewable plans and survives interrupted release steps.
Shorten a local monorepo check loop while retaining correctness when inputs, dependencies, or tools change.
Build a deterministic checkout regression suite around pricing, accessibility, payment failures, and isolated test data.
Create a local webhook laboratory that reproduces duplicates, disorder, signature failures, and interrupted delivery.
Build a retrieval workflow that respects document access, cites exact revisions, and declines unsupported answers.
Build a routing assistant that suggests queues, validates model output, and preserves accountable human corrections.
Build a vendor inventory connector with stable identity mapping, resumable ingestion, reconciliation, and tenant-safe operations.
Build a calendar booking workflow with time-zone rules, conflict handling, idempotent provider calls, and safe reconnect behavior.
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.