Full-stack ML for
Ads Ranking
Build a coherent understanding of the advertising ML system, from event data and targets to candidate retrieval, ranking, bidding, experimentation and low-latency deployment. Keep this secondary to the active DS job search.
System map
Events & attribution → point-in-time features → candidate retrieval → pCTR / pCVR & ranker → expected value / bid controller → auction & pacing → serving & monitoring → online experiments.
This is a conceptual end-to-end learning project, not a claim about your employer's production architecture.
Suggested capstone
Build a synthetic-data sponsored-search ranking sandbox. Train a pCTR baseline and a tree-based ranking model, estimate expected value, introduce a budget constraint, expose a FastAPI scoring service, and evaluate offline versus simulated online outcomes.
Definition of mastery
- Explain the causal or statistical reason behind a design choice.
- Implement one small reproducible experiment.
- State assumptions, limitations and trade-offs.
- Communicate in an Applied MLE interview format.
This week's lightweight learning block
60–90 minutes: explain the difference between ranking by pCTR, pCVR and expected revenue, and why improving offline NDCG might not improve ROAS. Write one hypothesis and one test. Stop there if job-search tasks need attention.
Full-stack modules
01 · Problem formulation
Week 1–202 · Data & features
Week 3–403 · Baselines and GBDT
Week 5–604 · Learning to rank
Week 7–805 · Neural ranking
Week 9–1006 · Auctions & bidding
Week 11–1207 · Offline → online evaluation
Week 13–1408 · Serving & MLOps
Week 15–16Weekly journal
Record one explanation, one experiment, and one unresolved question. Small entries count.