Domain 11: ML Systems Engineering
ML systems engineering: the ML lifecycle, pipelines, platform tools, feature stores, deployment strategies, monitoring and drift, and an end-to-end ML platform.
Unlock all 8 lessons with Unrolled Pro
Full production code, quantitative capacity math, failure recovery playbooks, and interview coaching.
Lessons
8 lessonsThe ML Lifecycle — From a Notebook to a System That Keeps Working
A model is a snapshot of the world at training time, and the world keeps moving.
ML Pipelines — Reproducible, Incremental, Validated
A pipeline turns the lifecycle into code a machine runs: ingest, validate, build features, train, evaluate, register, as a graph of steps with explicit dependencies.
ML Platform Tools — What MLflow, DVC, Docker, Ray and Friends Actually Do
The ML tooling landscape is crowded, and tools overlap: MLflow tracks experiments *and* serves models; Kubeflow orchestrates *and* tunes; cloud platforms bundle all of it.
Feature Infrastructure — Point-in-Time Correct, Fresh, Consistent
Features are where most production ML bugs live, because the same feature is needed in two very different places: training reads millions of historical rows and must see each one exactly as it was at the time; serving reads one entity's latest values in milliseconds.
Model Deployment — Batch, Online, Async, and Shipping Without Fear
Deployment is where a model meets real traffic, latency budgets and failure.
Model Monitoring — Drift, Delayed Labels and Alerts People Trust
A deployed model doesn't fail with an error message. It degrades quietly as the world drifts away from its training data, and the ground truth that would prove it often arrives weeks later.
Capstone: An End-to-End ML Platform — From Raw Events to Monitored, Self-Refreshing Models
Each piece of D11 solves one problem; a platform makes them work together so that every model gets the same guarantees for free: reproducibility (any model can be rebuilt from its code, data and config versions), safe deployment (shadow, canary, automatic rollback), observability (drift and performance monitored per model and segment), and freshness (retraining when data or performance says so, through the same gated pipeline).
Bridge: From Serving Models to Serving LLMs
Atlas now has pipelines, a feature store, safe rollouts and monitoring. Then the team self-hosts an open 8B model for the tutor to cut API costs.