Financial data fundamentals
Working with OHLCV data, handling missing values, identifying lookahead bias — the issues that break models before training even starts.
Six modules, each building on the previous. The first two weeks are deliberately slow — participants spend time understanding data quality issues in financial datasets before touching any model. Weeks three through six introduce supervised learning, cross-validation strategies specific to time-ordered data, and interpretability tools like SHAP. Every module ends with a graded assignment using real market data.
Working with OHLCV data, handling missing values, identifying lookahead bias — the issues that break models before training even starts.
Building lag features, rolling statistics, and domain-informed signals. Understanding which features add information versus which inflate apparent performance.
Decision trees, gradient boosting, and linear models tested on classification and regression tasks — with financial framing, not toy datasets.
Walk-forward validation, purging and embargo techniques. Standard k-fold fails on time series — this module explains exactly why and what to do instead.
SHAP values, permutation importance, partial dependence plots. Understanding what a model actually learned matters as much as its accuracy score.
Packaging a model for repeated use, tracking prediction drift, and knowing when to retrain. A working pipeline, not just a notebook.
Concrete skills take time to form. This program is designed for people who can commit around eight hours per week. Those who do tend to finish with a working project they can discuss in professional settings.
Participants build and submit a full ML pipeline — data ingestion through prediction output — using a dataset of their choice from a curated list. The final assignment is reviewed by a program instructor with written feedback.
scikit-learn, pandas, SHAP, and matplotlib are used throughout. Not as isolated exercises — as tools inside a coherent workflow. By module four most participants stop looking things up and start adapting code on their own.
Knowing what questions to ask about a model — how was it validated, what features dominate, does the performance hold out-of-sample — is as useful as building one. The program trains this critical reading alongside technical construction.
This site uses cookies to improve your workshop experience and measure engagement with learning materials. You can accept all cookies or decline non-essential ones.