Three pipelines on the canvas have schedule mismatches the section just named
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
Three pipelines on the canvas have schedule mismatches the section just named. The monthly close pipeline runs at midnight on the 1st (cron is correct: wall-clock alignment with a calendar moment). The webhook-driven payments pipeline polls Stripe via cron every 15 minutes, but Stripe emits webhooks; an event trigger fires precisely when there is work, not on a fixed cadence. The Kafka offset poller runs every 5 minutes via cron; the wall-clock time doesn't matter, only the gap between runs (an interval schedule would be more idiomatic). Apply the schedule-selection framing this section just taught and re-tag each pipeline with the right schedule form. Tag the monthly close as Cron (correct as-is). Tag the webhook-driven pipeline as Event-Trigger (or Sensor, Webhook, or Dataset) so it fires on Stripe webhook arrival. Tag the Kafka poller as Interval so it runs every N units without anchoring to a wall-clock time.
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