SQL for Data Engineers

Data engineers write SQL that runs every day without anyone watching it. These are real SQL problems from data pipelines - reports, joins, upserts, slow queries, dbt models - on a real database in a live cloud workspace.

Get started - freeLive cloud workspace in your browser · nothing to install

How data engineering SQL differs from analyst SQL

An analyst query runs once and someone reads the answer. A pipeline query runs on a schedule, so it has to be correct at the right grain, idempotent when it runs twice, and fast as the data grows. Window functions, upserts and query plans matter more here.

18 challenges to practice

Build a Kimball Star SchemaData · SeniorWire Data Quality Tests Across a dbt LineageData · SeniorBackfill a Column Safely (Batched + Verified)Data · SeniorHandle Late-Arriving Data in an Incremental LoadData · SeniorBuild an Event-Sourced Projection (CQRS)Data · SeniorFix a Pipeline Silently Dropping RecordsData · MidOptimize Batch Insert Throughput (COPY)Data · MidBuild a Staging-to-Marts dbt ProjectData · MidImplement SCD2 With dbt SnapshotsData · MidChoose the Right Postgres Join AlgorithmData · MidImplement the Outbox Pattern (At-Least-Once)Data · MidDebug a DuckDB Join That Multiplies RowsData · MidMake an ETL Pipeline IdempotentData · JuniorSpeed Up a Slow SQL Report QueryData · JuniorMake a CSV Importer Resilient to Bad DataData · JuniorValidate Data Before Loading ItData · JuniorHandle Orphan Records in an ETL JoinData · JuniorDebug a Broken SQL Revenue AggregationData · Junior

What to practice

Aggregation and window functions first, then joins (and why they multiply rows), upserts with ON CONFLICT, reading EXPLAIN ANALYZE, and modeling with dbt.

Do real production work, free. Live cloud workspaces in your browser - every project you complete lands on your portfolio.

Get started - free
Get started - free