The Serving Layer

Concepts covered: paMedallion

The serving layer is where most candidates go thin. They spend 25 minutes on ingestion and transformation, then say 'and then analysts query it.' That's a missed opportunity. How data is consumed drives the entire upstream design - and interviewers know it. Consumer Archetypes Different consumers need different data shapes. Analysts writing SQL dashboards need pre-aggregated, denormalized gold tables with low query latency. Data scientists building ML features need wide tables with historical snapshots. Reverse ETL consumers (pushing data back to Salesforce, Braze, Iterable) need narrow, frequently-refreshed tables keyed on user_id. Name the consumer explicitly in your answer - it justifies your entire transformation design. Materialized Views vs. Pre-Computed When dashboards need sub-

About This Interactive Section

This section is part of the Design a Pipeline: Intermediate lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live PostgreSQL database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.