Learning Path

Data Engineering Roadmap (2026)

SQL is the most frequently tested skill in data engineering interviews, followed by Python. Data modeling rounds appear in roughly a third of loops. This roadmap is sequenced by interview frequency so you learn the highest-value skills first.

Five phases, 18 weeks, specific milestones. Built for people who want to get hired, not people who want to read about data engineering.

Start Phase 1Download iOS App
18

Weeks total

5

Phases

45 min

Daily practice

The 5-Phase Roadmap

Phase 1: SQL Foundations
4 weeks+
  • SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY
  • JOINs: INNER, LEFT, RIGHT, FULL OUTER, CROSS, self-joins
  • Subqueries: scalar, correlated, EXISTS, IN
  • CTEs and recursive CTEs
  • Window functions: ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD, frame clauses
  • NULL handling: COALESCE, NULLIF, IS NULL, three-valued logic
  • Date functions: DATE_TRUNC, DATE_DIFF, EXTRACT, intervals

Milestone

You can solve a 3-step SQL problem (filter, aggregate, window function) in under 15 minutes without referencing documentation.

Phase 2: Python for Data Engineering
4 weeks+
  • Data structures: lists, dicts, sets, tuples, and when to use each
  • String processing: split, join, regex, f-strings
  • File I/O: reading CSV, JSON, and line-delimited files
  • Error handling: try/except, custom exceptions, logging
  • Functions: closures, decorators, generators, itertools
  • Collections module: defaultdict, Counter, deque
  • Basic OOP: classes for data models, dataclasses

Milestone

You can write a Python script that reads a JSON file, transforms the data, handles edge cases, and writes clean output. No copy-pasting from Stack Overflow.

Phase 3: Data Modeling and Schema Design
3 weeks+
  • Normalization: 1NF through 3NF, when to denormalize
  • Star and snowflake schemas for analytics
  • Slowly changing dimensions (SCD Type 1, 2, 3)
  • Fact tables vs dimension tables
  • Cardinality reasoning: one-to-many, many-to-many, bridge tables
  • Schema trade-offs: read vs write optimization, storage vs query speed
  • Entity-relationship diagrams and how to whiteboard them

Milestone

Given a business scenario, you can design a normalized schema, explain your choices, and discuss trade-offs in a 30-minute interview round.

Phase 4: Pipeline Architecture
3 weeks+
  • Batch vs streaming: when to use each, latency trade-offs
  • ETL vs ELT patterns and their implications
  • Orchestration: DAGs, dependencies, retries, idempotency
  • Schema evolution: backward compatibility, additive changes
  • Data quality: validation, monitoring, alerting, SLAs
  • Partitioning and bucketing strategies
  • Cost optimization: compute vs storage trade-offs

Milestone

You can whiteboard a data pipeline for a given business requirement, name specific tools you would use, and explain why you made each design choice.

Phase 5: Interview Prep
4 weeks+
  • Timed SQL practice: 5 questions in 60 minutes
  • Timed Python practice: 3 problems in 45 minutes
  • Schema design mock interviews with trade-off discussion
  • Pipeline design discussion practice
  • Behavioral questions: conflict resolution, project ownership, failure stories
  • Weak spot drills: focused practice on your lowest-scoring areas
  • Full mock interview simulations

Milestone

You can complete a full mock interview loop (SQL round, Python round, system design round, behavioral round) and pass all four.

What to Skip (and What Not To)

Skip these (for now)

Learning Spark or Hadoop first+
SQL and Python are the two most-tested skills by far. Spark appears in neither top category. Learn Spark after you get the job. Your first month on the team is the right time, not during prep.
Building a portfolio project before you know the fundamentals+
A portfolio project built on shaky SQL skills wastes time. Get your fundamentals solid first. The portfolio project is week 14, not week 1.
Memorizing syntax for 5 different cloud platforms+
Pick one cloud (AWS, GCP, or Azure). Understand the services at a high level for system design discussions. Do not memorize CLI commands.
Reading about data engineering instead of practicing+
Reading blog posts feels productive but does not build interview skills. The ratio should be 80% hands-on practice, 20% reading.

Do not skip these

✓Window functions. SQL is the most-tested interview skill, and window functions are the most common advanced topic within the SQL category.
✓NULL handling. Tricky NULL behavior is a favorite interview topic across the 32.7% of rounds that are phone-screen SQL.
✓Data modeling. Roughly a third of interview loops include it. Many candidates skip this and fail the schema design round.
✓Timed practice. Knowing the material and performing under pressure are different skills.

Data Engineering Roadmap FAQ

How long does it take to become a data engineer?+
With focused daily practice (45-60 minutes per day), most people can be interview-ready in 16-20 weeks. This assumes you are starting with basic programming literacy. If you already have SQL or Python experience, the timeline is shorter. The roadmap above covers 18 weeks total across 5 phases.
Do I need a CS degree to become a data engineer?+
No. Many successful data engineers come from analyst, business intelligence, or self-taught backgrounds. Interviews test your ability to write SQL, code in Python, and reason about data systems. A CS degree helps with some fundamentals but is not required at most companies.
Should I learn SQL or Python first?+
Start with SQL. It is the most-tested skill in DE interviews, appearing more often than any other topic. SQL is also easier to learn if you have no programming background. Python comes in Phase 2 after you have a solid SQL foundation.
What tools should I learn for data engineering?+
For interview prep: SQL (any dialect), Python, and schema design tools. For on-the-job readiness: one cloud platform (AWS, GCP, or Azure), one orchestration tool (Airflow is most common), and one data warehouse (Snowflake, BigQuery, or Redshift). Do not try to learn all of these before your first interview.

Start the Roadmap Today

DataDriven covers Phase 1 through Phase 5. Data engineers earn well above the tech industry median, with top performers earning nearly double. The gap is explained by interview performance. Start practicing.

Begin Your First Lesson

Related Guides

Analyst to Data Engineer

Transition plan for analysts who already have some SQL experience

DE Study Plan

Daily and weekly study schedules for working professionals

What Is Data Engineering?

The fundamentals of the field before you start the roadmap