Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Data modeling
Organise data into linked tables and describe each column
What you'll learn
Table grain
Primary key
Table relationships
Normalised design
Star schema
Model levels
Transactional and analytical
Practice
Spot What Is Wrong With This Table Design15 min
Chapter 5
Data transformation
Write and test one step that reshapes raw tables
What you'll learn
Transformation layers
Model grain
dbt materializations
Schema tests
Data lineage
Model references
The model graph
Templated SQL
Kinds of test
Practice
Choose a Materialisation for Five Models20 min
Five Claims About a Model, Three Kinds of Test25 min
Turn One Analyst Question Into a Model Plan20 min
Chapter 5
SQL
Write queries that filter and summarise data and join tables
What you'll learn
Query output shape
Join logic
Grouping level
Query plan
Practice
Write SQL Queries to Join, Filter, and Summarize15 min
Refactor a tangled query into tested steps30 min
Chapter 5
Cloud data platforms
Query a cloud database and check costs before adding data
What you'll learn
Cloud service choice
Object storage
Managed warehouse
Cloud costs
Permission basics
What a query costs
Reading less data
Practice
Run a SQL Query in a Free Cloud Sandbox20 min
Chapter 6
Git
Save clear changes to a project's history and request review
What you'll learn
Change states
Short-lived branches
Merge conflict
Useful commit message
Pull request review
Practice
Make a Commit and Undo a Mistake15 min
Chapter 6
Documenting data work
Write data field definitions that others can use unaided
What you'll learn
Metric definition
Data lineage
Assumptions and trade-offs
Documentation types
Practice
Create a Mini Data Dictionary for 15 Metrics30 min
5 more in the plan
Data qualityWrite checks for a table and run them before sharingCh 6
What you'll learn
Data checks
Plausible values
Root cause fix
Practice
Decide How to Handle Bad Data Under Deadline15 min
Problem solvingTest each possible cause of a problem instead of guessingCh 7
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 7
What you'll learn
The hidden assumption
Argue the other side
The base rate
Fact vs inference
Wanting it to be true
Practice
Challenge Your Own First Take20 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 8
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Write a Request That Makes It Easy to Say Yes10 min
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~1 wk
See what analytics engineer work involves
StartFree
2~1 wk
Model data others can build on
Skills
31–2 wks
Build a funnel metric dictionary
Project
4~1 wk
Talk to an working analytics engineer
People
5~1 wk
Turn raw data into tested tables
Skills
6~1 wk
Check data and document changes in Git
Skills
7~1 wk
Find the cause before you fix it
Skills
8~1 wk
Make yourself understood across a team
Skills
91–2 wks
Capstone: build tested, documented tables from raw data
Project
10~1 wk
Answer the questions interviewers ask
Interview
11~1 wk
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Analytics Engineer does
Takes a company's raw stored data and turns it into clean, tested, documented data sets. Analysts and dashboards then all share one trusted set of numbers.
The work
Build dbt models that transform raw warehouse tables into clean datasets
Define the metric layer so every team measures numbers the same way
Write tests and documentation so models stay correct and trusted
Refactor messy SQL into reusable, modular, version-controlled transformations
Work with analysts to turn reporting needs into shared models
Review code, manage pull requests, and keep transformations maintainable
Track model performance and warehouse cost to keep pipelines efficient
A typical day
Check model test failures and freshness alerts from the overnight run
Meet an analyst to clarify what a metric means and how detailed the data should be
Build or refactor a dbt model, then run tests on sample data
Open a pull request, review a teammate's models, and merge changes
Update documentation and answer questions about a metric definition
How long does it take to become a analytics engineer with Welica?
The plan is 12 chapters, 3 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in data analytics, computer science, statistics, or information systems, bachelor degree in economics, math, or business plus strong SQL practice, online courses or bootcamps focused on dbt, SQL, and data modeling, or self-taught path with a portfolio of dbt projects and practical certificates.
What is free?
Chapter 1, See what analytics engineer work involves, is free for good. Premium unlocks the rest of the plan.