Role roadmaps / Analytics Engineer Role roadmap
The dbt-shaped role: models, tests, CI, and a metric finance can reuse. Between analyst questions and engineer pipelines.
Also called: Analytics Developer, Metrics Engineer
You ship: Versioned marts, contracts, and a metric layer someone else can query.
8–16 weeks if you already write SQL
Roadmap Coding Interview Question bank Switch roleData Analyst BI Analyst Data Engineer Analytics Engineer Data Scientist ML Engineer MLOps Engineer AI Engineer Data Architect Nearby roles:Data Analyst , Data Engineer , BI Analyst
→
Skill check10 questions Already working in this role? Answer honestly and the roadmap ticks what you have done, then points you at the first gap.
Take the 2-minute skill check 1 of 10
Can you do this?
1 Yes, I have done this2 Partly3 Not yet
Back Keys 1, 2 and 3 answer while the check has focus.
Result
Ticks are only added, never removed. Partly and Not yet leave a skill unticked.
Checked skills
0% · pick any skill to see its syllabus, links and practice.
Journey Map List
− Fit + Print Clear checks
RTE
Stop 1 of 17
◀ Prev StopNext Stop ▶ Auto Cruise
Click any bus stop to drive there and inspect the complete syllabus, or scroll the highway to follow the bus.
Terminal Start · Station 1 of 17
Click to stop Start · Analytics Engineer Versioned marts, contracts, and a metric layer someone else can query. Inspect station brief →
Checkpoint · Station 2 of 17
Click to stop Foundations The tools you cannot fake in week one Inspect station brief →
Bus Stop · Station 3 of 17
Click to stop SQL at mart grain Windows, grain tests, and anti-joins. You will write more SQL than the DE. Open Syllabus →
Bus Stop · Station 4 of 17
Click to stop Git as a team sport PRs, reviews, and why main is protected. Open Syllabus →
Bus Stop · Station 5 of 17
Click to stop Warehouse dialect Pruning, clustering, clones. Know who pays for the explore. Open Syllabus →
Checkpoint · Station 6 of 17
Click to stop Daily craft What you actually do on a Tuesday Inspect station brief →
Bus Stop · Station 7 of 17
Click to stop dbt the way CI survives Staging 1:1 with sources, marts at a grain, slim CI. Open Syllabus →
Bus Stop · Station 8 of 17
Click to stop Tests on grain unique + not_null on the grain. Relationships to dimensions. Fail the build. Open Syllabus →
Bus Stop · Station 9 of 17
Click to stop Docs that get read Descriptions, exposures, and a metric page a PM can open. Open Syllabus →
Checkpoint · Station 10 of 17
Click to stop How you ship Production habits, not extra courses Inspect station brief →
Bus Stop · Station 11 of 17
Click to stop Slim CI and defer Build what changed. Defer to prod for the rest. State artifacts. Open Syllabus →
Bus Stop · Station 12 of 17
Click to stop Source contracts Breaking a column should break CI, not a dashboard at 9am. Open Syllabus →
Bus Stop · Station 13 of 17
Click to stop Metrics, not workbooks One definition. Many consumers. Semantic layer when the org is ready. Open Syllabus →
Checkpoint · Station 14 of 17
Click to stop Career moves How this role talks in interviews Inspect station brief →
Bus Stop · Station 15 of 17
Click to stop AE interview SQL, dbt structure, and “how do you stop two revenues?” Open Syllabus →
Bus Stop · Station 16 of 17
Click to stop Next role DE if you want streaming. Analyst lead if you want narrative. Architect if you want platforms. Open Syllabus →
Final Destination · Station 17 of 17
Click to stop Keep practicing SQL + Python for this role Inspect station brief →
Start · Analytics Engineer Foundations SQL at mart grain Windows, grain tests, and anti-joins. You will write more SQL than the DE. Git as a team sport PRs, reviews, and why main is protected. Warehouse dialect Pruning, clustering, clones. Know who pays for the explore. Daily craft dbt the way CI survives Staging 1:1 with sources, marts at a grain, slim CI. Tests on grain unique + not_null on the grain. Relationships to dimensions. Fail the build. Docs that get read Descriptions, exposures, and a metric page a PM can open. How you ship Slim CI and defer Build what changed. Defer to prod for the rest. State artifacts. Source contracts Breaking a column should break CI, not a dashboard at 9am. Metrics, not workbooks One definition. Many consumers. Semantic layer when the org is ready. Career moves AE interview SQL, dbt structure, and “how do you stop two revenues?” Next role DE if you want streaming. Analyst lead if you want narrative. Architect if you want platforms. Keep practicing Phase 1: Foundations SQL at mart grain Windows, grain tests, and anti-joins. You will write more SQL than the DE. Git as a team sport PRs, reviews, and why main is protected. Warehouse dialect Pruning, clustering, clones. Know who pays for the explore. Phase 2: Daily craft dbt the way CI survives Staging 1:1 with sources, marts at a grain, slim CI. Tests on grain unique + not_null on the grain. Relationships to dimensions. Fail the build. Docs that get read Descriptions, exposures, and a metric page a PM can open. Phase 3: How you ship Slim CI and defer Build what changed. Defer to prod for the rest. State artifacts. Source contracts Breaking a column should break CI, not a dashboard at 9am. Metrics, not workbooks One definition. Many consumers. Semantic layer when the org is ready. Phase 4: Career moves AE interview SQL, dbt structure, and “how do you stop two revenues?” Next role DE if you want streaming. Analyst lead if you want narrative. Architect if you want platforms.
SQL at mart grain Windows, grain tests, and anti-joins. You will write more SQL than the DE.
If you cannot say the grain, you are not ready to write the model.
Checked automatically: you solved the linked practice problems.
SQL at mart grain. If you cannot say the grain, you are not ready to write the model.
Time to learn You will write more SQL than the DE. Treat the pad as the job.
Prerequisites Mart grain vs source grain Windows for latest What you need SQL tracks A dbt project Interview SQL Concepts to study Mart grain vs source grain Windows for “latest” and running metrics Anti-joins for quality marts Incremental models and unique keys Tech stacks dbt SQL — The jobWarehouse dialect — Pruning, clusteringThis site SQL tracks — The padHow to study Write one mart with unique+not_null on the grain. SQL interview questions; foundations + windows tracks. What to produce fct_orders grain in one sentence unique + not_null on that grain Practice on this site SQL questions; coding tracks Pitfalls A mart that is a SELECT * from bronze Grain that changes when a join is added Interview prompts Say the grain of fct_orders in one sentence. Links
Previous skill Next skill
Mark as done Search DataLane All Articles Stacks Practice Learn Pages
No results. Try analyst, numpy, snowflake, or roadmap.
↑↓ navigatealt ↑↓ jump group↵ openesc closeAliases: sf, numpy, analyst, mlops