# A SaaS team built two pipelines off one Kafka topic: Dashboard ETL and Feature ETL each pull from Ka

Canonical URL: <https://datadriven.io/problems/a-saas-team-built-two-pipelines-off-one-kafka-topic-dashboa-49e6f292>

Domain: Pipeline Design · Difficulty: medium

## Problem

A SaaS team built two pipelines off one Kafka topic: Dashboard ETL and Feature ETL each pull from Kafka independently. Last week Feature ETL filtered out bot traffic, Dashboard ETL did not, and the two views drifted; the bot-filter logic now exists in two places. Apply the section's split-in-curated framing so Kafka is consumed once into a shared raw zone, one curated transform owns bot filtering, and the two consumer-shaped paths branch from the curated layer.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/a-saas-team-built-two-pipelines-off-one-kafka-topic-dashboa-49e6f292)
- [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.