Task library BINCIDENT Site reliability · Phased project Queue backlog incident response A fictional document service has a rising processing backlog. Operators cannot tell whether arrivals, worker failures, or a slow dependency is responsible.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 26h + setup
Suggested stack TypeScript · BullMQ · Redis Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BINCIDENT-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice incident timelines, queue diagnosis, and measured recovery.
What the team gains Produce a repeatable response that preserves work integrity and exposes customer delay.
Before you start Create a bounded local queue simulation with synthetic jobs and controllable worker/dependency failures. Delivery agreement Deliver local incident instrumentation, recovery controls, and a tabletop report.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Separate queue age, throughput, and failure symptoms.
PHASE 2 Control arrivals and retries while preserving job identity.
PHASE 3 Drain work and validate recovery decisions.
Observe backlog Separate queue age, throughput, and failure symptoms.
BINCIDENT-101 Entry ticket; project setup still required Estimated field mix
Site reliability 80% Platform engineering 20% BINCIDENT-102 Depends on BINCIDENT-101 Estimated field mix
Site reliability 60% Performance engineering 40% Contain safely Control arrivals and retries while preserving job identity.
BINCIDENT-103 Depends on BINCIDENT-102 Estimated field mix
Platform engineering 60% Site reliability 40% BINCIDENT-104 Depends on BINCIDENT-102 Estimated field mix
Site reliability 50% Platform engineering 30% Security 20% BINCIDENT-105 Depends on BINCIDENT-103 Estimated field mix
Distributed systems 50% Platform engineering 30% Site reliability 20% BINCIDENT-106 Depends on BINCIDENT-103, BINCIDENT-104 Estimated field mix
Site reliability 60% Integrations 40% Recover and learn Drain work and validate recovery decisions.
BINCIDENT-107 Depends on BINCIDENT-102, BINCIDENT-106 Estimated field mix
Performance engineering 60% Site reliability 40% BINCIDENT-108 Depends on BINCIDENT-104, BINCIDENT-105, BINCIDENT-107 Estimated field mix
Performance engineering 60% Site reliability 40% BINCIDENT-109 Depends on BINCIDENT-108 Estimated field mix
Site reliability 80% Data engineering 20% BINCIDENT-110 Depends on BINCIDENT-109 Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.