Task library SYNC Integrations · Phased project Inventory sync that survives a vendor outage A fictional retailer receives stock from two vendor warehouses. The vendor API paginates snapshots and emits change events, but retries and deleted products have caused unexplained stock drift. Work against a local vendor simulator.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 23h 15m + setup
Suggested stack TypeScript · NestJS · PostgreSQL · BullMQ 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 SYNC-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice external contracts, cursor recovery, mapping conflicts, and reconciliation under partial failure.
What the team gains Inspect whether integration changes protect inventory correctness and give operators a clear recovery path.
Before you start Create a local vendor API simulator with cursor pages and stock events. Use synthetic tenants, SKUs, and warehouse records; no vendor account is required. Delivery agreement A simulated vendor connector, reconciliation workflow, drift report, and outage runbook.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Validate external records before affecting stock.
PHASE 2 Handle cursors, duplicates, disorder, and API limits.
PHASE 3 Find drift and apply only reviewable corrections.
Understand vendor identity and data Validate external records before affecting stock.
SYNC-101 Entry ticket; project setup still required Estimated field mix
Integrations 70% Data engineering 30% SYNC-102 Depends on SYNC-101 Estimated field mix
Integrations 40% Security 30% Database engineering 30% Ingest changes safely Handle cursors, duplicates, disorder, and API limits.
SYNC-103 Depends on SYNC-102 Estimated field mix
Integrations 40% Database engineering 40% Data engineering 20% SYNC-104 Depends on SYNC-102 Estimated field mix
Integrations 50% Data engineering 30% Database engineering 20% SYNC-105 Depends on SYNC-103 Estimated field mix
Integrations 50% Distributed systems 30% Site reliability 20% SYNC-106 Depends on SYNC-103, SYNC-104 Estimated field mix
Integrations 50% Data engineering 30% Distributed systems 20% Recover and operate Find drift and apply only reviewable corrections.
SYNC-107 Depends on SYNC-103 Estimated field mix
Integrations 60% Data engineering 40% SYNC-108 Depends on SYNC-106, SYNC-107 Estimated field mix
Integrations 40% Database engineering 40% Security 20% SYNC-109 Depends on SYNC-105 Estimated field mix
Site reliability 50% Integrations 50% SYNC-110 Depends on SYNC-108, SYNC-109 Estimated field mix
Integrations 60% Quality engineering 20% Site reliability 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.