D8A Academy © Portfolio Platform
Build · Validate · Get Hired
Free introLeaderboardBlogCheatsheetsCommunity
Sign inGet started
← All articles
Career·July 28, 2026·3 min read

Data engineer in 30 days: what you can actually build (free Notion template)

You cannot become a data engineer in 30 days, and anyone selling that is lying. What you can do: design a real schema, ship a working ETL pipeline, and transform data with dbt, three portfolio pieces that most junior applicants don't have. Free Notion template included.

Let's start with the honest version: data engineering is the deepest of the four data career paths, and 30 days gets you nowhere near job-ready. So why run a 30-day DE challenge at all? Because the three things you can build in a month, a proper relational schema, a working ETL pipeline, and a dbt project, are exactly the artifacts that separate "interested in data engineering" from "started doing data engineering".

This is the Data Engineer track of our free 30 Days of Data Notion template: one session a day, 40 to 60 minutes for this track, three shipped projects by day 30. For a feel of the actual job, read a day in the life of a data engineer.

The 30-day outcome, honestly stated

1
working ETL pipeline pulling from a live API into PostgreSQL
1
star schema you designed and can defend in an interview
1
dbt project with tested, layered transformations

Notice what is not on the list: Airflow, Kafka, Docker, Terraform, BigQuery. All of that is in the full path, and none of it fits honestly into a month alongside the fundamentals. A junior candidate with a defensible schema and a pipeline that actually runs beats one who name-drops eight orchestration tools.

The 30-day plan

  1. Days 1-3
    Foundations

    Free SQL intro course

    An hour of SQL fundamentals. DE demands the strongest SQL of any path, so do the exercises even if they feel easy.

  2. Days 4-10
    Project 1

    SQL and data modeling

    Design a normalized schema and a star schema for a real e-commerce domain, and defend the trade-offs in your README. Solo alternative: model Kaggle's Olist dataset in PostgreSQL.

  3. Days 11-18
    Project 2

    Python ETL pipeline

    An incremental pipeline from a live API into PostgreSQL: extraction, validation, idempotent loads, logging. Solo alternative: the OpenWeather API. This is the project interviewers ask about, because it is the daily job in miniature.

  4. Day 19
    Milestone

    Portfolio v1 goes live

    Schema and pipeline online, each with a write-up: the problem, your design decisions, what broke and how you fixed it. DE write-ups earn extra credit for war stories.

  5. Days 22-26
    Project 3

    dbt transformations

    The tool that reshaped analytics engineering: layered models, tests, documentation. Solo alternative: dbt's own jaffle_shop tutorial, extended with your own models on top.

  6. Days 27-30
    Finish line

    Polish, publish, share

    Recruiter test on day 28, publish day 29 with #30DaysOfData, retro day 30.

Months two to four
The full DE path continues with Airflow orchestration, a BigQuery warehouse, Docker and infrastructure as code, Kafka streaming, AI-enhanced data quality, and a production-platform capstone that is a genuine multi-week build. The 30-day challenge is the on-ramp, not the destination, and the template keeps the whole roadmap visible so you know exactly what comes after day 30.

Guided or solo

Each project has a guided route on D8A Academy, with the brief, the environment steps, GitHub validation and an auto-built portfolio page, and a solo route with the free alternatives above. DE is the path where guidance pays off most: environment setup is where solo learners lose entire weekends, and a stepped brief turns that into an hour.

Day 0 takes ten minutes: pick DE, pick your mode, filter the library, block your slot. Make today day 0.

Keep reading