# A growth team's curated marts have no formal quality program Canonical URL: Domain: Pipeline Design ยท Difficulty: medium ## Problem A growth team's curated marts have no formal quality program. Each pipeline has ad-hoc checks (or none); thresholds are hard-coded; the same producer drifts every quarter; orphan keys silently understate revenue; nobody can answer 'is the data good' without a Slack thread. Build the quality program. Add schema validation at the source-to-raw boundary, distributional checks at the curated layer, referential-integrity checks between fct and dim, environment-aware thresholds, and the five-pillar suite at the serving layer. Block-class fires route to a paging destination; warn-class fires route to a non-paging notification channel. The dashboards keep reading from their existing Snowflake marts. ## Related - [All practice problems](https://datadriven.io/problems) - [Mock interview mode](https://datadriven.io/interview/a-growth-teams-curated-marts-have-no-formal-quality-program-4191a1c6) - [System Design Interview Questions](https://datadriven.io/data-engineering-system-design) - [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep) - [Daily Challenge](https://datadriven.io/daily) --- Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.