Documentation rots; CI does not
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
Documentation rots; CI does not. A contract that lives as a YAML file in a wiki page is fiction within six months because the producer evolves and the wiki does not. The section's mechanism is a versioned contract checked into the producer's repo and validated in CI on every change so violations cannot ship. The contract names schema (primary key, fields, types, nullability), guarantees (operational SLA, quality SLA), and evolution policy. Author the contract by adding a CI runner node on the producer side that validates the contract on every PR, and an ingestion-gate quality check on the pipeline side that enforces the same contract on real events.
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