A consumer-app event pipeline has every beginner-tier failure mode at once: producers ship new field
A medium Pipeline Design mock interview question on DataDriven. Practice with AI-powered feedback, real code execution, and a hire/no-hire decision.
- Domain
- Pipeline Design
- Difficulty
- medium
Interview Prompt
A consumer-app event pipeline has every beginner-tier failure mode at once: producers ship new fields without warning, the loader is strict and rejects unexpected payloads, the daily aggregation buckets by processing_time so late mobile events land in the wrong day, and there is no rerun window so each day's number freezes once it is written. The capstone is the assembled fix from the four beginner sections. Replace the strict loader and warehouse with a flexible-shape destination (lakehouse format with schema_evolution, or VARIANT-typed warehouse columns) so producer additions absorb without code changes; rebucket the aggregation by event_time; add an orchestrator with a seven-day rerun window in its name; replace the append-only destination with one that supports partition overwrite by event_date so reruns are idempotent. The dashboard must read from the final reconciled destination.
How This Interview Works
- Read the vague prompt (just like a real interview)
- Ask clarifying questions to the AI interviewer
- Write your pipeline design solution with real code execution
- Get instant feedback and a hire/no-hire decision