One dbt project that proves it
Use DuckDB (free, runs on your laptop) with dbt.
- Load a public dataset, for example Indian government open data or a Kaggle sales file.
- Build staging, intermediate and final models.
- Add at least ten tests and fix what they catch.
- Generate dbt docs and write a short README defining every metric.
Put it on GitHub. The tests and definitions are what interviewers open first.
Your Python habits, translated to dbt
| You already do | What it becomes |
|---|---|
| Kept code in Git with reviews | Version-control every SQL model |
| Wrote unit tests | Add dbt tests: unique, not null, accepted values |
| Cleaned data with pandas | Do the same cleaning in SQL staging models |
| Packaged reusable functions | Write reusable macros and shared models |
The new parts are thinking in SQL first, naming models so analysts can find them, and agreeing metric definitions with people who aren't engineers.
Your realistic 90 days
Analytics teams often lack the habits you take for granted: version control, tests and code review. Analytics engineering is where those habits meet SQL and business metrics. You'll finish with a tested dbt project anyone can run.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Install dbt and DuckDB and run the starter project | dbt run succeeds |
| 2 | Choose a public dataset you find interesting | Dataset downloaded |
| 3 | Write staging models for two tables | 2 models |
| 4 | Add unique and not-null tests | Tests run |
| 5 | Write one final model for a business question | Model builds |
| 6 | Define three metrics in plain English in the README | 3 definitions |
| 7 | Save 10 analytics engineer or data engineer postings | 10 links |
Days 1–30: A tested project
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Finish the models, ten tests and dbt docs | about 12 hours over 3 weeks | repo with docs | Staging only. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Share the repo in one data community and ask for review | about 1 hour | 1 post | Comment on 2 posts. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: Someone else can clone it and run it.
Days 31–60: Show it to analysts
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Build a small dashboard on top of your final models | about 8 hours | dashboard link | One chart. | Save or commit what works now and stop adding. A finished small version beats an unfinished big one. |
| Apply to 8 analytics engineer, data engineer or BI developer roles | about 4 hours | 8 logged | Apply to 4 analytics engineer, data engineer or BI developer roles. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A screening call where you explain a metric definition.
Days 61–90: Interview-ready SQL
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Practise window functions and joins for 20 minutes a day | about 5 hours | 15 sessions | 8 sessions. | Optional. Skip it if the week is full; nothing later depends on it. |
| Ask 2 ex-colleagues in data teams for referrals | about 1 hour | 2 asks | Just one instead of 2. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 90: A SQL round you finish calmly.
The two worries we hear most about this move
My SQL is rusty. Is that a problem? It's the main thing to fix. Twenty minutes of practice a day for three weeks, plus building the dbt project, usually brings it back. Interviews test SQL more than Python. Will I lose my Python skills? Not really. Many analytics engineers still write Python for loading data, tests and automation. It's a useful extra, not the core.
Other worries, such as age, a career gap, no degree, English, family pressure and savings, are covered on the route page and the role page.
One search that fits your background
The full set of search strings for this move is on the route page. They work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so recruiters who want both skills find you first.
Job-hunt moves that matter for this route
- Search 'analytics engineer', 'dbt developer', 'data engineer (SQL)' and 'BI engineer'.
- Product companies, consulting firms and global capability centres list most of these roles.
- Mention dbt and your test count in your headline.
Five honest questions about SQL and testing
(Takes about a minute; answers stay on your device.)
- Is your SQL as comfortable as your Python? (yes / no)
- Have you cleaned a messy CSV with pandas? (yes / no)
- Do you write tests even for small scripts? (yes / no)
- Have you argued about what a metric should mean? (yes / no)
- Would you enjoy making other people's dashboards trustworthy? (yes / no)
Four or five yeses: this bridge is short for you. Two or three: still reachable. Fewer: start with the python developer role page and come back.
Model Lineage
A dashboard number is wrong. Trace it back through the models one hop at a time.
Model Lineage
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Analytics engineering pay: not checked
We haven't verified pay data for analytics engineer roles. Rates differ by city, company and contract type.
Python to analytics engineering: common questions
Is this just data engineering? It overlaps. Analytics engineering sits closer to analysts and business definitions; data engineering covers more pipelines and infrastructure. Do I need a cloud warehouse? Not to learn. DuckDB on your laptop is enough for a proof. Listings often name Snowflake or BigQuery; their concepts transfer.
Data-job scams we've seen described
Be careful with "test tasks" that are really unpaid client work, recruiters asking for fees, or anyone asking for OTPs or UPI PINs. Use official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Next: route page · Python Developer role page · Quiz
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 25 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| DuckDB documentation | duckdb.org |
| What dbt is | docs.getdbt.com |