Preserve conflicting offline visit notes for explicit resolution
Two emulators edit one visit offline and last-write-wins removes a paragraph. Surface both revisions.
Estimated field mix
- Mobile50%
- Distributed systems50%
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 73 of 115
Two emulators edit one visit offline and last-write-wins removes a paragraph. Surface both revisions.
Estimated field mix
Killing the process mid-sync leaves operations marked Sending forever. Add a recoverable lease state.
Estimated field mix
Attachment cache consumes emulator storage. Add per-visit cleanup that preserves authored drafts.
Estimated field mix
A disconnected emulator retries uploads continuously and drains resources. Add capped backoff with manual retry semantics.
Estimated field mix
A global Sync complete banner hides a failed visit. Show per-visit pending, conflicted, and acknowledged states.
Estimated field mix
Debugging a stuck route requires durable state without sharing account tokens. Provide a previewed local recovery bundle.
Estimated field mix
Unmeasured courses show 0 MB and users assume downloads are free of storage cost. Display size uncertainty.
Estimated field mix
Returning to the shelf shows Download while a transfer is active. Render controls from one persisted lifecycle.
Estimated field mix
A malformed manifest filename can escape its course directory. Restrict all destinations to a scoped cache root.
Estimated field mix
A paused transfer resumes after content changed and produces mixed bytes. Bind ranges to a manifest version.
Estimated field mix
A truncated transfer is marked complete because the connection closed normally. Verify length and declared digest.
Estimated field mix
A nearly full emulator accepts several downloads and fails unpredictably. Reserve a bounded budget before writing.
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.