Last updated: October 2026
The Analytics Engineer’s Field Guide
dbt, Snowflake and Airflow
Three jobs make an analytics engineer, three tools answer them, and three engineers in this guide each live one of them.
34 lessons, each ending with a quiz. About 4 hours of reading, 2 to 12 minutes a lesson.
Developed by Ismail Mezzour. Published by DataFrost Consulting.
What this guide covers, and who it follows
Three engineers, three jobs that fit together: transform the data, run it on schedule, and make the warehouse fast and cheap.
An analytics engineer turns raw data into tables the business can trust, and keeps them running. Three things make that real, and the guide is built in that order:
- Transform the data with dbt, so a SQL query becomes a tested, documented, dependency-aware table.
- Run it on schedule with Airflow, so the whole pipeline refreshes in order, retries on failure, and tells you when something breaks.
- Make it fast and cheap by tuning Snowflake, so all of that work reads less data and burns fewer credits.
Each one follows a person with that problem.
How to use it: read the parts in order, because each one builds on the last. Every lesson ends with a three-question quiz, and your progress is saved automatically. Already know some of it and want a reference? Every lesson is open, and a lesson counts as read once you reach the end of its text or click Next.
The three engineers
Problem 1: transforming data (Alice)
Alice writes a SQL query that cleans and joins raw tables. It works once, in her editor. But there's no standard way to turn it into a real table, no test to catch bad data, and no record of what depends on what. Next week she copies an old query, swaps the table names, and hopes. Knowledge lives in her head, not in the platform.
SELECT. dbt builds the table, tests it, documents it, and tracks what depends on what. One way to transform data, the same for every engineer.Problem 2: running it on schedule (Thomas)
Thomas has the tables. Now they need to refresh every morning at 6am, in the right order, and someone has to know the moment one breaks. He starts with a cron job, then a second. Then a model fails at 2am and everything downstream quietly serves stale data until a manager notices at 9. Cron has no memory, no retries, no alerts.
Problem 3: a slow, expensive warehouse (Ismail)
The tables are built and they run on time, but a dashboard takes four minutes to load and the Snowflake bill doubled this quarter. Nobody wrote a bad query on purpose. The same query reads a billion rows when it only needed a million, a warehouse stays on all night doing nothing, and the same numbers get recomputed a thousand times a day. Speed and cost have one cause: work you didn't need to do.
How it fits together: sources, Snowflake, dbt, Airflow
It's one pipeline. Raw data leaves your sources and lands in Snowflake, dbt transforms it there, inside Snowflake, into trusted tables, and those feed your BI dashboards. Airflow drives the whole run on a schedule. Follow the data along the arrows, and each engineer owns one piece.
Snowflake
stores the data · runs the SQLIsmail tunes SnowflakeAlice builds with dbtThomas runs Airflow
Where the analytics engineer sits
Analytics engineering is the seam between two older roles. The data engineer moves raw data into the warehouse, the analyst turns trusted tables into decisions. You own the middle, turning raw into trusted with software discipline. dbt, Airflow and Snowflake are what let one person hold that whole middle.
From here, the guide follows Alice as she learns dbt, then Thomas as he puts it on a schedule with Airflow, then Ismail as he makes Snowflake run all of it fast and cheaply.

