Learn SQL modeling, version control in Git, tested transformations in dbt and a cloud warehouse, so the numbers every dashboard shows come from one trusted place. Every exercise is checked, and the pathway ends in warehouse projects, a timed assessment across the tools and the interview.
Take the steps in this order. Each step is a set of units from one course, not the whole course: the units this role uses. Open a unit to start its first lesson.
1
SQL and data modeling
Analytics engineers write SQL all day. You query, summarize and join tables, use subqueries and window functions, design schemas and model data for analytics: facts, dimensions and the grain of every table.
Models are code, and code is reviewed. You commit, inspect history, stage part of a change, branch and merge, the way a dbt project moves from a branch to production.
dbt is where the job happens. You set up a project, declare sources, build and test models, reuse logic with Jinja, add data quality tests and documentation, process incrementally, keep history and use packages.
Your models run in a cloud warehouse. You learn Snowflake's way around, query it, write report logic with windows, change data safely and govern who sees which reports, with query profiles to find what is slow.
Build reusable warehouse fields and measures, test join grain and save a dashboard definition. Use access filters for regional restrictions and check the source totals before sharing.
Each project starts from a fictional company's brief and moves between tools the way the job does: what you build in one stage is where the next one starts. Every brief is free to read.
Copperline Freight
SnSnowflakedbtdbtTbTableau
Project
Move the on-time report into the warehouse
Copperline's on-time report is a spreadsheet someone rebuilds every Monday. Rebuild it on the warehouse: one current row per shipment in Snowflake, a tested dbt model, and a Tableau view operations can trust.
Wayfriend wants to know whether friends who plan to meet actually spend time together. Clean the raw events, model meetups, measure success and plan the next day of work.
Operations reports one on-time rate and finance reports a lower one, for the same month. Find out why, write the measure both teams agree on, and recommend which number goes to customers.
When you finish the units, test yourself across the tools of the job at once: 15 practical tasks in 60 minutes, each in the tool it is about and checked automatically. The clock keeps running if you close the page.
Tool
Tasks
Minutes
Looker and LookML
3
11
SQL
3
11
Git
3
11
dbt
3
13
Snowflake SQL
3
11
How it is scored
Each tool
Ready when you get two thirds of its tasks right or more, Close at one third, otherwise Not yet. A coding task earns the share of its tests that pass.
Ready for interviews
75% or more overall, and every tool at Ready.
Nearly ready
50% or more overall, and no tool at Not yet.
Keep practicing
Anything else. The report lists every task you missed with the lesson that teaches it.
The assessment is free. The result is practice feedback in the Interview Hub's report format, not a hiring decision. Retakes draw different tasks where the question pools allow.
The interview
The Interview Hub runs the analytics engineer interview round by round, at a fictional employer: you answer out loud or in writing, the interviewer follows up, and the report quotes your answers.
The first unit of every course, with no account: 4 of the 34 units on this pathway. Every project brief is free to read, and the job-readiness assessment is free.
One Course
One course in full. On this pathway that is one of these: SQL (9 units), Git (5 units), dbt (9 units), Snowflake SQL (6 units), Looker and LookML (5 units).
All Access
The whole pathway: every unit, every project stage and spoken interview practice.
An analytics engineer sits between data engineering and analysis. They take the raw tables that land in the warehouse and build the clean, tested models everyone else reports from: one definition of revenue, one table of active customers, one on-time rate. They write SQL in dbt, review each other’s changes in Git and add tests so a broken source shows up before a wrong number reaches a dashboard.
From a query to a tested model
SQL and modeling come first because every later step is SQL. Git follows because dbt projects live in repositories. dbt is the longest step and the heart of the job. The warehouse comes last, when you know what you are running in it.
Showing what you can do
Copperline’s on-time report is a spreadsheet someone rebuilds every Monday. You move it onto the warehouse: one current row per shipment in Snowflake, a tested dbt model and a view operations can trust. At Wayfriend you model meetups from raw events. Both are the kind of project analytics engineering interviews ask about. The assessment then shows which tool to practice before you apply.
Common questions
What is the difference between an analytics engineer and a data engineer?
A data engineer gets data into the warehouse and keeps the pipelines running. An analytics engineer turns those raw tables into tested, documented models that analysts and dashboards use. The data engineer pathway adds Python and orchestration; this one goes deeper into modeling and dbt.
Do I need to know Python?
Not to start. Analytics engineering is mostly SQL, dbt and Git. Python helps later, and the Python course is there when you need it.
How long does it take?
The lessons on this pathway add up to about 45 hours. We don't promise how long getting hired takes.
What does it cost?
The first unit of every course is free, with no account. One Course opens one course in full; All Access opens the whole pathway. The pricing page shows every plan and its price.