A producer team has filed three proposed schema changes for the orders event: rename amount to amoun
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 producer team has filed three proposed schema changes for the orders event: rename amount to amount_cents, add an optional refund_reason field with default null, and remove the deprecated legacy_sku field. The section's classification is direct: adding an optional field with a default is additive (safe), renaming or removing fields downstream code reads is destructive (forces coordinated deploy), and the safe path for a rename is the expand-contract pattern under the hood. On the canvas, classify each proposed change by adding three classification nodes downstream of the producer, one per change, whose names state which class the change belongs to (additive, destructive, or coordinated rename via expand-contract).
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