BEGINNER · 8 MODULES · 64 LESSONS

Data Engineering Foundations

Go from writing code to thinking like a data engineer: model your first tables, validate the data, and build a pipeline you can rerun without duplicates.

For you if
You already code in Python and want to get into data engineering with solid foundations, not just tool names.
By the end
You'll know how to choose batch or streaming based on the business, tell ETL from ELT, and backfill without breaking anything.
You need
Intermediate Python and Python 3.11 or later on your laptop. Everything runs locally, no cloud account.
  1. 01What Is Data Engineering8 LESSONS
    1. Guide overview: from loose files to a pipeline you can trust
    2. What is data engineering in 2026?
    3. The data engineering lifecycle
    4. Upstream and downstream stakeholders
    5. Meet Kiosko: the case
    6. Read your first data file
    7. From raw rows to Python objects
    8. Mini-project: explore two days of Kiosko's raw data
  2. 02Batch Vs Streaming And The Sla8 LESSONS
    1. Module overview: the question that comes before any tool
    2. Batch processing: what it is and why it exists
    3. Streaming processing: what it is and why it exists
    4. The SLA question, before any tool
    5. Does Kiosko need batch or streaming?
    6. Extracting multiple files with pathlib
    7. Parsing a full week of orders
    8. Mini-project: Kiosko's daily extraction job
  3. 03Etl Elt And The Warehouse8 LESSONS
    1. Module 3 overview: what changed when storage stopped being expensive
    2. ETL vs ELT: what changed with the cloud warehouse
    3. OLTP vs OLAP: two different jobs
    4. The map: the warehouse, the lake, and the lakehouse
    5. Columnar storage and why Parquet is different
    6. Loading raw data with SQLite: your first ELT
    7. A first look at DuckDB
    8. Mini-project: Kiosko's landing zone
  4. 04Modeling Your First Tables8 LESSONS
    1. Module 4 overview: Kiosko's first data model
    2. Facts and dimensions: a first look
    3. Designing Kiosko's fact_orders table
    4. Designing Kiosko's dimension tables
    5. Joining facts with dimensions in Python
    6. Computing derived columns
    7. Writing the transform_fact_orders function
    8. Mini-project: Kiosko's first fact table
  5. 05Data Quality Gates8 LESSONS
    1. Module introduction: the gate before the load
    2. What can go wrong in a pipeline
    3. Schema checks and required fields
    4. Null and type checks
    5. Range and business rule checks
    6. Quarantining bad rows instead of crashing the pipeline
    7. Writing a validation report
    8. Mini-project: Kiosko's quality gate
  6. 06Idempotency And Backfill8 LESSONS
    1. Module introduction: why running the pipeline twice shouldn't duplicate anything
    2. Why pipelines must be safe to re-run
    3. The overwrite-partition pattern
    4. Making Kiosko's load step idempotent
    5. Proving idempotency: running twice
    6. What is a backfill
    7. Writing a backfill function
    8. Mini-project: Kiosko's safe rerun
  7. 07Partitioning And Orchestration8 LESSONS
    1. Module introduction: partitioning and chaining
    2. Why partition by date
    3. Designing Kiosko's partition layout
    4. Chaining the pipeline steps
    5. Logging what the pipeline did
    6. Handling a failed step without losing the run
    7. When a Python script stops being enough
    8. Project: Kiosko's end-to-end pipeline over the week
  8. 08Project Kioskos Batch Pipeline8 LESSONS
    1. Module introduction: Kiosko's capstone
    2. The brief: Kiosko needs a daily report
    3. Building the bronze layer
    4. Building the silver layer
    5. Building the gold layer with DuckDB
    6. Running the full pipeline for a week
    7. What Kiosko still needs
    8. Mini-project: Kiosko's first production pipeline
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab