Data Engineer Roadmap (2026)

SQL comes first because every later stage is written in it. Learn SELECT with joins and GROUP BY with HAVING, and once those are solid, move on to CTEs and window functions. After that, get NULL handling and conditional aggregation right, and know why COUNT(*) and COUNT(col) return different numbers. The time transfers to any data role: in the 2025 Stack Overflow Developer Survey, 61.3% of professional developers reported using SQL, more than the 54.8% who used Python.

You're done when you can write a window function query that handles ties correctly without looking anything up, explain why an INNER JOIN dropped rows you expected to keep, and deduplicate a table to the latest row per key. Ship 1 analysis on a real public dataset that ends in a query you can defend out loud.

Write SQL against a real database instead of reading about it, and let the queries that come back wrong show you where your picture of the data is off. The SQL practice problems check your output against the expected rows, and the SQL interview questions cover the patterns hiring loops return to. Ranking and running totals are there, and so are sessions and gaps and islands.

Python is the second language of the job, the glue around SQL. Learn the standard library for files (CSV, JSON, gzipped logs, nested records) and use dictionaries and generators for data too big to hold at once. In pandas, learn groupby and merge first; pivot can wait until those feel natural. Add enough error handling to tell a script from a job. A class with 3 methods and a test is about the ceiling of the object-oriented work the rounds ask for.

Skip algorithm grinding. Data engineering loops ask you to parse and reshape data and then check that it is valid, while puzzles about trees and graphs are the exception. You're done when you can ingest a messy file, reject the bad rows with a reason for each, and write the good ones to a warehouse table; ship exactly that script. The Python practice problems are built around parsing and transformation for this reason.

Dimensional modeling is the stage most roadmaps treat as a footnote and the one that most often separates mid-level from senior candidates. It's the discipline of shaping tables for analysis: facts that record events, dimensions that describe them, and a grain that says exactly what 1 row means.

Learn the Kimball Group's 4-step dimensional design process: select the business process, declare the grain, identify the dimensions, then identify the facts. The order matters because a candidate who draws tables before stating the grain ends up with a fact table that mixes 1 row per order with 1 row per order line, and every sum on it is wrong.

Then learn slowly changing dimensions. Type 1 overwrites an attribute; Type 2 adds a new row with validity dates so history survives; the choice is a product question about whether past facts should report the old value or the new one. The Data Warehouse Toolkit by Ralph Kimball and Margy Ross (3rd edition, 2013) is the reference for the patterns. Ship a 5 table model for a business you understand, with the grain written above every fact table.

On the practice problems at datadriven.io, this is where people stall: members pass 91% of their attempts at SQL problems and 51% of their attempts at data modeling problems. Practise it aloud with the data modeling interview questions, and read how the data modeling interview round is run before your first loop.

Pick 1 warehouse and learn it past the surface. Snowflake and BigQuery both qualify, and so does Postgres. Learn how it stores and prunes data through partitioning and clustering, how to read a query plan, what a materialized view costs to keep fresh, and which dialect quirks change what is cheap. Surface familiarity with 3 warehouses rarely survives a follow-up question; depth on 1 lets you contribute in your first week.

Cloud works the same way. Choose 1 platform by the companies you target: AWS if you've no preference, Google Cloud where BigQuery is the warehouse, Azure where the employers run Microsoft Fabric. Stop at the depth an interview reaches: how data lands in object storage, how it's partitioned, what a query costs, and how a job authenticates to read a bucket. Everything past that you'll learn on the job.

Stages 3 and 4 overlap on purpose. Build your model in the warehouse you chose, so the grain you declared runs into real partitions and query plans, and a real bill.

Skill doesn't turn into offers on its own. Interviews reward recall under a clock and the ability to narrate a tradeoff out loud, and both are separate from doing the work. Give them their own weeks: timed problems with the output checked, modeling questions answered aloud, and whole loops run end to end.

A data engineering loop usually has a SQL round and a Python round, then a data modeling round and a pipeline or system design round, plus a behavioral round. The mix shifts by level. The data engineer interview prep guide breaks down what each round covers, and a data engineer mock interview is the closest rehearsal. You are done when a full timed loop no longer surprises you.

Skip the tool inventory. Spreading the months before your first application across Kafka, Spark, Flink, dbt, Terraform and 3 clouds leaves each one thin, and thin knowledge fails follow-up questions. Learn Spark when a target job names it; its DataFrame API reads like the SQL and pandas you already know.

Skip streaming before batch. Teams usually run batch pipelines first and add streaming where the latency pays for it, and every streaming idea (late events, watermarks, exactly-once) is easier once batch failures are familiar. Skip certifications as a hiring strategy too, since the rounds probe problem solving rather than vendor knowledge.

A portfolio project helps in the last third of the roadmap, not the first month. Built on shaky SQL, it is a liability in the interview where someone asks you to explain it. Build it after stage 5, on a real dataset, and write up the design choices: the grain, how it reruns, what it costs. The writeup gets read more closely than the code.

AI assistants now draft routine SQL and boilerplate transformations well, so less of a junior role goes to hand-writing a straightforward pipeline than it once did. What they do not remove is the judgment around the code: which grain a table has, whether a load is safe to rerun, what a query will cost, who gets paged when a table is late. Interviews have moved the same way and ask why more often than what.

The US Bureau of Labor Statistics has no separate data engineer occupation. Its closest, database architects, earned a median $139,500 in May 2025, and it projects 4% growth for database administrators and architects together from 2025 to 2035. Stages 3 to 5 of the roadmap, the judgment layer, are the part that gains value as assistants take over the typing.

Beside a full-time job, the constraint is attention more than hours. The usual failure is spending month 4 rereading stage 1 because it feels productive. Give every week a checkable output: a query that returns the right rows, a model with its grain written down, a DAG that survives a deliberate failure.

Keep a data-driven log with 3 columns. Record the problem and whether it passed, and in the third column write what you got wrong. Rework the misses a week later without notes. Once window functions stop being effortful, start the data modeling practice problems even if SQL still feels unfinished; modeling practice keeps your SQL sharp, and the reverse isn't true. At 10 hours a week, 45 focused minutes on weekdays plus a longer weekend session beats 1 lost Saturday.

A certification rarely decides a data engineering offer, because the loop probes problem solving rather than vendor knowledge. It helps in 2 cases: a role or a consultancy that names it as a requirement, and a career switcher who needs a resume line that shows cloud exposure.

If you take one, take a current exam. Microsoft retired the Azure Data Engineer Associate certification (DP-203) on March 31, 2025. Its current data engineer certification is Fabric Data Engineer Associate (DP-700), which covers SQL and PySpark as well as KQL. The AWS Certified Data Engineer Associate (DEA-C01) is 65 questions in 130 minutes, and AWS recommends 2 to 3 years of data engineering experience before it, which places it after this roadmap rather than inside it.