Four Teams, One Topic, No Agreement
A hard Pipeline Design mock interview question on DataDriven, with an AI interviewer who asks follow-up questions and a hire or no-hire decision at the end.
- Domain
- Pipeline Design
- Difficulty
- hard
- Seniority
- L5
Interview Prompt
Four teams publish to one shared event topic, and three streaming jobs read it, the dashboard team's real-time job among them. How would you design the pipeline so an incompatible schema change is refused when it is published, not discovered when a job crashes, and an event a job still cannot read is kept durably for replay?
Summary
Everybody is writing to it. Nobody documented it. Now production is fragile.
How This Interview Works
- Read the vague prompt (just like a real interview)
- Ask clarifying questions to the AI interviewer
- Draw your pipeline on the design canvas: sources, transforms, storage and checks
- Answer the interviewer's follow-up questions, then get a hire or no-hire decision