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.
50 matching tickets · Page 1 of 5
The room shows Connected immediately after a socket opens, even while the last five minutes of events are still missing. Give connection and synchronization separate states.
Estimated field mix
A gateway change sends a string sequence number and crashes every open room tab. Define a versioned event envelope with deliberate unknown-version behavior.
Estimated field mix
A client changes the room ID in its subscribe message and receives a few private timeline entries before the gateway rejects membership. Move authority checks ahead of all history and live delivery.
Estimated field mix
A reconnect overlaps live delivery with replay. The same mitigation note appears twice, and a late earlier event moves a resolved task back to active.
Estimated field mix
A laptop wakes after the room’s replay window has expired. The gateway returns recent events after the old cursor, leaving an invisible gap in the task state.
Estimated field mix
A responder claims Investigate cache saturation, loses the acknowledgement, and retries. The room appends duplicate claims and briefly shows two owners.
Estimated field mix
Closing a laptop leaves its user shown as In room for hours. Presence currently uses the same durable event path as incident notes, making heartbeat traffic dominate replay.
Estimated field mix
A temporary responder is removed while a long history replay is streaming. The established socket keeps receiving new private notes until reconnect.
Estimated field mix
A paused browser cannot consume events, but its send buffer grows throughout a synthetic incident drill. Add bounded per-connection delivery and a recoverable overload path.
Estimated field mix
The team has not tested what room users see during a gateway restart. Create a repeatable drill with one pending claim, a disconnected reader, and a recently revoked member.
Estimated field mix
Missing coordinates are coerced to zero, placing a depot van in the ocean. Validate telemetry before rendering and explain vehicles with no usable position.
Estimated field mix
A van’s last position remains bright green after its device disconnects. Dispatch assigns a nearby job using a point that is twenty minutes old.
Estimated field mix
5 matching projects · Page 1 of 1
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.
Model ephemeral team presence with expiry, reconnects and scoped fan-out.
Keep a synthetic service-status board ordered and replayable over server-sent events.
Coordinate expiring seat holds and live availability in a local simulation.
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.