Topic hub

Analytics Engineering

The role, the skills, the toolchain, and the path from your first dbt model to a job offer — built by working analytics engineers.

Analytics engineering sits between the data analyst and the data engineer. The analyst writes the queries the business runs on. The data engineer ships the pipelines that move bytes. The analytics engineer owns the transformation layer — the dbt models, the data tests, the semantic layer, the marts — that turn raw warehouse data into trusted, modeled inputs for everyone downstream.

It's one of the fastest-growing roles in data because it solves the problem every company has: somebody who understands the business writes raw SQL that nobody else can re-use, and somebody who knows engineering ships pipelines without enough business context. Analytics engineers fix that gap by owning the layer between them.

This hub is the curated starting path. The articles below cover the role itself, the daily work, the toolchain, and the realistic comparisons to adjacent jobs. The exercises and projects in the practice library drill the SQL, dbt, and modeling work the role actually does. The course is the structured end-to-end version.

What you'll learn

By the end of this path you can…

  • Explain what an analytics engineer does on a typical day
  • Contrast the role against data analyst, data engineer, and BI developer
  • Map the modern data stack — warehouse, transformation, BI, orchestration
  • Identify the SQL, dbt, modeling, and warehouse skills hiring managers screen for
  • Build a learning plan with realistic timelines and milestones
  • Decide whether the role is a fit for your background, with eyes open
The learning path

From beginner to job-ready.

  1. 01 · The role

    What analytics engineering is, who it reports to, what a typical day looks like, and the work products that come out of it.

  2. 02 · The comparison

    How analytics engineering differs from analytics, data engineering, BI, and ML engineering — and where the role's leverage actually is.

  3. 03 · The stack

    The modern data stack at a glance: warehouse → ingestion → transformation (dbt) → BI → orchestration → observability.

  4. 04 · The skills

    SQL, dbt, data modeling, and one warehouse — the technical floor. Communication, documentation, and review hygiene — the part that gets people hired.

  5. 05 · The path

    Becoming hireable without a CS degree, what companies actually screen for, and the portfolio that proves it.

Articles

Read the playbook.

All resources →
In the course

Welcome to Analytics Engineering

16 lessons in this module

Common questions

Common questions about this topic.

What does an analytics engineer actually do?

An analytics engineer owns the transformation layer of the data stack. They write dbt models on top of raw warehouse data, define and document marts, write data tests, set up CI for the project, and partner with analysts and PMs on what gets shipped. Day-to-day it's a lot of SQL, code review, and conversations about which metrics are which.

How is analytics engineering different from data engineering?

Data engineering owns the bytes — ingestion, infrastructure, scaling. Analytics engineering owns the transformation — what those bytes become once they hit the warehouse. The two roles overlap on schema design and orchestration but separate on platform vs. semantic layer.

Do I need a CS degree?

No. Most analytics engineers came from analyst, marketing, finance, or operations backgrounds. What matters is SQL fluency, dbt experience, a clean GitHub project that demonstrates the work, and the ability to walk through it in an interview.

What's the salary range?

In the US, $110k–$180k base for senior analytics engineers at mid-to-large data teams is common; staff and lead roles push higher. Remote-first companies pay competitively. The role has compressed less than data engineering because it's still demand-heavy and supply-light.

How long does it take to become hireable?

From zero coding experience: six to twelve months of consistent practice. From data analyst with strong SQL: three to six months. The bottleneck is rarely concepts; it's having a portfolio project hiring managers can actually look at.

Start practicing this topic.

Graded exercises with hints, worked solutions, and a GPT tutor. Free to start, no credit card.