Task library QUEUE Platform engineering · Phased project Bring document processing back under control A fictional internal document portal creates previews through a trusted mock renderer. Large batches crowd out small teams, failed documents retry forever, and operators lack a safe replay command. This exercise never executes uploaded code or real document macros.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 29h + setup
Suggested stack TypeScript · BullMQ · Redis · PostgreSQL · Object storage 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 QUEUE-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice asynchronous lifecycle control, fair scheduling, bounded retries, and artifact recovery with a deterministic provider.
What the team gains See how an engineer accounts for accepted work and reduces operational toil without granting operators broad data access.
Before you start Queue semantics Database transactions Operational metrics Delivery agreement Ten tickets in intake, resilience, and operations phases; use only synthetic document metadata and a trusted deterministic renderer.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Create traceable jobs with bounded inputs.
PHASE 2 Control retries, concurrency, cancellation, and worker loss.
PHASE 3 Expose useful lag signals and safe repair operations.
Account for accepted work Create traceable jobs with bounded inputs.
QUEUE-101 Entry ticket; project setup still required Estimated field mix
API design 40% Platform engineering 30% Backend 30% QUEUE-102 Entry ticket; project setup still required Estimated field mix
Platform engineering 50% Performance engineering 30% API design 20% QUEUE-103 Depends on QUEUE-101, QUEUE-102 Estimated field mix
Distributed systems 40% Database engineering 30% Platform engineering 30% Handle failures deliberately Control retries, concurrency, cancellation, and worker loss.
QUEUE-104 Depends on QUEUE-103 Estimated field mix
Platform engineering 60% Site reliability 40% QUEUE-105 Depends on QUEUE-103, QUEUE-104 Estimated field mix
Platform engineering 50% Performance engineering 30% Distributed systems 20% QUEUE-106 Depends on QUEUE-104, QUEUE-105 Estimated field mix
Distributed systems 60% Platform engineering 40% QUEUE-107 Depends on QUEUE-106 Estimated field mix
Backend 50% Platform engineering 30% Distributed systems 20% Make recovery routine Expose useful lag signals and safe repair operations.
QUEUE-108 Depends on QUEUE-104, QUEUE-105 Estimated field mix
Site reliability 70% Platform engineering 30% QUEUE-109 Depends on QUEUE-104, QUEUE-106 Estimated field mix
Platform engineering 40% Backend 30% Security 30% QUEUE-110 Depends on QUEUE-106, QUEUE-107, QUEUE-109 Estimated field mix
Storage systems 50% Platform engineering 30% Distributed systems 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.