A daily orders aggregation works fine when nothing goes wrong
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 daily orders aggregation works fine when nothing goes wrong. Tonight at 3am the on-call engineer gets paged: the dashboard is empty. Stdout from the run scrolled past hours ago, no run identifier ties one log line to a specific run, and the only failure signal is a nonzero exit code nobody is watching. The section names five things a script lacks (run identity, durable visibility, failure signal, recovery, idempotent restart). Spot the operability gap by adding the operational shell on the canvas: a structured-log destination, a metric-store destination, a paging destination, and a heartbeat that lets on-call see the pipeline is making progress.
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