The Six-Month Schedule
A curriculum without a calendar is a wish. This chapter turns the eight courses into a realistic, month-by-month plan you can actually live with — honest about the hours involved, flexible enough for a faster or slower pace, and built so you finish instead of fizzling out around month three.
The time math
Let's start with the number nobody likes to say out loud. Going from "I can write a basic query and a small script" to "I'm job-ready as a data platform engineer" takes roughly 300 to 500 hours of focused effort. Not hours with the video playing in another tab — hours where you're typing, breaking things, and fixing them. That's the real range, and it's the same whether you do it in three months or twelve.
Why such a wide range? Because it depends on your starting point and how much you build versus skim. Someone with a software background who does every exercise lands near 300. A true beginner who needs to reread the foundations and debug their own capstone lands near 500. Both numbers are normal. Neither means you're behind.
Here's how that translates into a calendar at different weekly commitments:
| Hours / week | What that looks like | Time to job-ready (~400 hrs) |
|---|---|---|
| 5 hrs | One weeknight + a slow Sunday morning | ~12 months |
| 8–12 hrs | Two or three evenings + a weekend block | ~6 months |
| 25 hrs | Near full-time; between jobs or on a bootcamp pace | ~3 months |
This curriculum is tuned for the middle row: 8–12 hours a week for about six months. That's the pace most career-changers can sustain alongside a job or family without quietly giving up.
The word that matters most here is consistent. Eight hours every week for six months beats forty hours in one heroic week followed by three weeks of nothing — every single time. Skills built on a steady drip stick; skills crammed evaporate. A "consistent" week doesn't mean a perfect week. It means you touched the material on most of your planned days and shipped one small thing.
If a course promises "job-ready in 4 weeks," it is selling you the feeling of progress, not the skill. Real competence in data platform engineering is a months-long build. The upside of being honest with yourself now: you'll set a schedule you can keep, instead of one you'll resent and abandon by week three.
The six-month plan
Here is the centerpiece — the full plan at the 8–12 hrs/week pace. Each month maps to a course (or the handoff between two), a weekly focus, and a concrete deliverable. Notice the last column: your companion repo grows every single month, so by month six it's a portfolio, not a pile of notes.
| Month | Course(s) | Weekly focus | Milestone / deliverable | Companion repo grows to… |
|---|---|---|---|---|
| 1 | 1 Roadmap → 2 Orientation & Setup; start 3 Foundations | Read the roadmap, install your toolkit (git, Python, Docker, a local warehouse), run your first tiny pipeline | A working dev environment + a one-file pipeline that loads a CSV into a table you can query | Initialized repo, a README, your first load.py |
| 2 | 3 Foundations | How databases, warehouses, and lakes really work; storage, indexes, query execution | Explain (in your README) why a query is slow and how an index fixes it; a normalized schema you designed | A schema diagram + SQL scripts + notes folder |
| 3 | 3 Foundations finish → start 4 The DE Craft | Dimensional modeling, idempotency, the shape of a real pipeline; first dbt models | A star schema modeled by hand, then your first dbt project running locally | A dbt/ project with staging + a fact model |
| 4 | 4 The DE Craft | Ingestion patterns, transformations, orchestration, data quality & tests | An orchestrated pipeline (ingest → transform → test) that runs end to end on a schedule | An orchestrator DAG, dbt tests, a quality check |
| 5 | 5 Tooling & Modern Stack; start 6 Capstone | git fluency, Docker, CI/CD, cloud object storage; scaffold the capstone | Your pipeline containerized with a green CI run; capstone project scaffolded | A Dockerfile, a CI workflow, the capstone skeleton |
| 6 | 6 Capstone finish → 7 Career | Build & operate the mini-platform; then polish the repo, resume, and your story | A working mini data platform you can demo, plus a portfolio README and resume bullets | The finished platform — your portfolio centerpiece |
Course 8 (Glossary & Cheat Sheets) isn't a month — it's a reference you keep open the whole way through. Dip into it whenever a word stops you.
Every deliverable above lands in one git repository that you grow week by week. Recruiters and hiring managers can't see the hours you put in — they can see the repo. By month six it's the single most persuasive thing you own, and you built it incrementally without ever doing a "portfolio sprint."
Faster & slower variants
Six months is the default, not the law. The same ~400 hours of work can be compressed or stretched. Pick the lane that matches your actual life right now — and know you can switch lanes mid-curriculum.
| Variant | Pace | Length | Best suited to… |
|---|---|---|---|
| Intensive | ~25 hrs/week | ~3 months | Between jobs, on a career break, or treating this like a full-time bootcamp. Fast — but you must protect rest days or you'll flame out. |
| Standard | 8–12 hrs/week | ~6 months | Working or studying part-time. The sweet spot for most people: sustainable, with room for a bad week now and then. |
| Relaxed | ~5 hrs/week | ~12 months | A demanding job, caregiving, or just a steady-and-sure temperament. Slower, but consistency makes it work. The risk is losing thread — so finish each course before pausing. |
To use the six-month plan above at a different pace, just rescale: each "month" in the table becomes roughly two months on the relaxed track, or two weeks on the intensive track. The order and the deliverables don't change — only the calendar around them does.
Pacing without burning out
Finishing is a pacing problem far more than an intelligence problem. The people who quit rarely quit because the material got too hard — they quit because their schedule was a fantasy, or they hit a flat stretch and read it as failure. Here's how to avoid both.
Set fixed weekly study blocks. Don't "find time" — time is never found. Put two or three named slots on your actual calendar (e.g. Tue 8–10pm, Thu 8–10pm, Sun 9am–noon) and defend them like meetings. A recurring time beats willpower because the decision is already made.
Define your minimum viable week. Some weeks will fall apart. For those, decide in advance what the smallest acceptable amount is — say, "one 90-minute block and ship one tiny thing." A minimum-viable week keeps the streak alive without guilt, and a streak you never fully break is one you can always rebuild from.
Rest on purpose. At least one full day off the material, every week. Learning consolidates during the gaps, not just during the work. Especially on the intensive track, scheduled rest isn't slacking — it's how the previous days actually stick.
Around month three, the novelty is gone, the easy wins are behind you, and the finish line still feels far. Almost everyone feels a flat, "am I even getting anywhere?" stretch here. You are not failing — you're in the middle, which always feels like this. Push through with two tricks: shrink your goals to tiny shippable wins for a couple of weeks, and look back at your month-one repo to see how far you've come. The dip passes, and the second half is where it starts feeling real.
Confidence milestones
Hours and chapters are inputs. These are the outputs — concrete "I can now do this" markers. Use them as a compass: if you reach the end of a month and can honestly check the box, you're on track, regardless of how the hours added up.
| By the end of… | You can… |
|---|---|
| Month 1 | Run a local pipeline that loads a file into a queryable table, with your whole toolkit installed and a repo started. |
| Month 2 | Explain how storage, indexes, and query execution work — and design a normalized schema from scratch. |
| Month 3 | Model data dimensionally and transform it with dbt — staging models, a fact table, all running locally. |
| Month 4 | Stand up an orchestrated pipeline that ingests, transforms, tests, and runs on a schedule end to end. |
| Month 5 | Containerize your work, get a green CI run, and have a working mini-platform scaffolded in the cloud. |
| Month 6 | Demo a complete (small) data platform and talk through its design — with a portfolio repo and resume to match. |
Notice these are all things you do, not things you know. That's deliberate — it's also exactly how interviews evaluate you.
✓ Check yourself
Before moving on, make sure you can answer "yes" to these:
- Can you state, honestly, roughly how many total hours this takes (and why the range is wide)?
- Do you know which variant — intensive, standard, or relaxed — matches your life right now?
- Can you name what your companion repo should contain by the end of month three?
- Do you have a plan for the month-three dip before you hit it?
Exercise — Draft your personal weekly schedule (do it now)
In the note where you wrote your "why," add two things: (1) your named study blocks for a normal week, and (2) your one weekly "ship goal" — the small thing you commit to producing each week. Then write your minimum viable week for the bad weeks. Here's a filled-in example for someone on the standard track with a day job:
# My weekly plan (standard track, ~9 hrs/week, target: 6 months)
## Fixed study blocks (on my calendar, treated as meetings)
- Tue 8:00–10:00pm (2h) reading + small exercises
- Thu 8:00–10:00pm (2h) hands-on / typing code
- Sun 9:00am–12:00pm (3h) the week's main build + ship
- Wed 7:00–8:00am (1h) review last session, fix what broke
- Rest day: Saturday — fully off the material
## Weekly ship goal
Commit one working thing to my companion repo every Sunday,
with a one-line note in the README about what it does.
## Minimum viable week (for the weeks that fall apart)
One 90-min block + ship ONE tiny commit. Streak stays alive.
There's no single right answer — yours should fit your real calendar, not an ideal one. The point is that the decisions are made before the week starts, so you're never negotiating with yourself at 8pm on a Tuesday.
Next
You have a destination, a map, and now a calendar. The last piece of orientation is technique — how to make all this effort actually stick. → How to Use This Curriculum