02 — Engineering tracks
Each track is a sequence with a stated end state: modules build on one another and finish in work you can defend.
Start with the language, end with a deployed product you maintain yourself.
9-12 months · 8 builds
Applied machine learning: build, evaluate and serve models in production systems.
8-10 months · 6 builds
Learn how systems break, then learn to defend them with structured practice in a lab.
10-12 months · 7 builds
Automate delivery and run reliable infrastructure you can reason about under pressure.
7-9 months · 6 builds
From SQL to decision-ready analysis, with pipelines that survive contact with real data.
6-9 months · 6 builds
Questions
A module map, the prerequisites that matter, the tooling you will use, and the work you produce at the end. Each module states what you build, not just what you read.
Each track lists an estimated duration based on steady weekly effort. Move faster or slower — nothing expires and nothing is gated by a cohort date.
Yes. Tracks share technology areas deliberately, so a second track reuses what you already built instead of restarting from the basics.
Working software and a written record of the decisions behind it — the same material a reviewer or hiring engineer would ask for.