Home / Certificates / Data Science
Pro Advanced

Professional Certificate in Data Science

Stop interpreting other people's models. Build your own — frame it, train it, prove it works, ship it, defend it — with AI writing the code and you catching what it gets wrong.

10 modules 26 hours 4 weeks Certificate

Why this instead of a traditional degree?

The Usual Data Science Bootcamp
  • $7,000-$18,000 and three to six months of your life
  • Weeks of Python syntax before you touch a real modelling decision
  • Clean teaching datasets where nothing leaks and nothing is ambiguous
  • Model accuracy as the goal, with no decision attached to it
  • Ends at the notebook — no deployment, no bias audit, no model card
Professional Certificate in Data Science
  • Included with Pro subscription
  • AI writes the code from lesson one; you learn to read and interrogate it
  • One realistic business runs through every module, with the traps planted
  • Every model is judged against a baseline and a cost, never a bare score
  • Ends with a deployed app, a bias audit, a model card, and a solo capstone

What you'll learn

Frame a modelling problem end to end — define the prediction target as a rule, fix the unit of analysis and prediction window, and write down the baseline the model must beat before any code is written

Audit a column list for leakage at design time, and diagnose the four failure families — leakage, overfitting, wrong target or metric, and drift — from the symptoms each one produces

Direct an AI assistant through a full modelling workflow and read the code it returns critically, catching the silently dropped rows and the transform applied on the wrong side of the split

Design an experiment rather than read one — choose the randomisation unit, set the minimum detectable effect from the business, compute the sample size, and pre-register the stopping rule

Build features that encode domain knowledge, keep them point-in-time correct, and assemble them into a pipeline that does the same thing twice

Choose cross-validation that matches the structure of the data, tune without contaminating the test set, and diagnose a model from its train-versus-validation gap

Assess a model against the decision it supports — the right metric, calibrated probabilities, a threshold placed where the costs say, and the errors read rather than the score

Ship a model — reproducible notebook, batch scoring with schema validation, a small app with a URL, drift monitoring, and a handoff engineering can act on

Build your own model's fairness audit and model card, and compose a written deployment recommendation — including the recommendation not to deploy

Outcome

A model that beats a stated baseline, a deployed app, a bias audit, a model card — and a capstone you scoped alone.

Curriculum

10 modules · 47 lessons · capstone

Orientation — From Reading Models to Building Them

1.25h · Workbench + verification method

See the full road from wherever you stand now to a working data scientist, take an honest five-question self-assessment, open your first notebook from nothing installed, and learn the method for having AI teach you a subject you cannot yet judge.

Your Path From Analyst to Data ScientistPrerequisite Self-AssessmentSet Up Your Modelling WorkbenchLearning Data Science With AI as Your Tutor

Portfolio Deliverable: A working notebook, a reusable AI context block, and the four verification checks

Start Module

The Model Builder's Operating Model

1.5h · First model + code read-through

The division of labour that runs the whole programme — you frame, AI writes, you verify, the data decides. Train your first model inside twenty minutes, then learn the load-bearing skill: reading code you did not write well enough to catch what it quietly did.

The Line You Just CrossedYour First Trained ModelReading Code You Didn't WriteThe Four Ways Models Fail

Portfolio Deliverable: A trained model with an honest score, and the five-question code read-through

Start Module

Framing a Modelling Problem

2h · Project brief + leakage audit

Most modelling projects fail before any code is written. Define the prediction target as an actual rule, decide whether the problem needs a model at all, fix the unit of analysis and the moment you score, establish the baseline you must beat, and audit the column list for leakage before you load a single row.

From Business Question to Prediction TargetIs This Even a Machine Learning Problem?The Unit of Analysis and the Prediction WindowThe Baseline You Must BeatThe Leakage Audit, Before You Build

Portfolio Deliverable: A written project brief: target rule, scoring moment, baseline, and the columns you refuse to use

Start Module

Statistics and Experimental Design for Model Builders

2h · Experiment design

Put an interval on your own numbers with the bootstrap, then design the experiment rather than read one — randomisation unit, minimum detectable effect, power, and a stopping rule fixed in advance. What to do when randomising is impossible, and the three mechanisms that make results evaporate.

Uncertainty You Can Actually ComputeDesigning the Experiment, Not Just Reading ItWhen You Cannot RandomisePeeking, Multiplicity, and How Results EvaporateCumulative Review 1: Framing, Building, and Evidence

Portfolio Deliverable: A powered experiment design with a pre-registered analysis plan

Start Module

Feature Engineering With AI

2h · Feature pipeline

Features are where your domain knowledge enters the model, and the one part AI cannot do for you — though it accelerates it more than anything else. Brainstorm candidates with context, encode them properly, keep time-aware features point-in-time correct, and assemble a pipeline that does the same thing twice.

Features Are Where Your Domain Knowledge LivesEncoding, Scaling, and When It Actually MattersTime-Aware Features and the Leakage TrapFeature Selection, Done HonestlyPipelines That Do the Same Thing Twice

Portfolio Deliverable: A reproducible feature pipeline with a point-in-time correctness check

Start Module

Building and Tuning Models

2h · Tuned, diagnosed model

Climb the ladder from baseline to gradient boosting and discover the jump nobody talks about is the first one. Match cross-validation to the structure of your data, tune without contaminating the test set, understand what AutoML hides, and run the diagnostic routine that tells you which failure you are looking at.

The Model Selection LadderCross-Validation That Matches Your DataTuning Without Fooling YourselfAutoML: What It Does and What It HidesDebugging a Model With AI

Portfolio Deliverable: A tuned model with an honest held-out score and a documented diagnosis

Start Module

Evaluation, Metrics, and Error Analysis

2.5h · Threshold + slice analysis

A model does not have a score — it has a decision it supports. Choose the metric from the decision backwards, escape the accuracy trap on imbalanced data, calibrate the probabilities so a cost calculation means something, and read the mistakes rather than the number.

The Metric the Decision Actually NeedsImbalance and the Accuracy TrapCalibration and Where to Put the ThresholdError Analysis: Read the Mistakes, Not the ScoreExplaining a Model — and the Limits of ExplanationCumulative Review 2: Features, Models, and Evaluation

Portfolio Deliverable: A cost-justified threshold, a per-slice performance table, and a per-prediction explanation

Start Module

From Notebook to Something That Runs

2h · Deployed model + monitoring

Most models never reach anyone, and the gap is smaller than people think. Make a notebook that still runs tomorrow, build the scheduled batch job that is the deployment most models actually get, put your model behind a URL a colleague can open, watch for drift, and hand off to engineering properly.

The Notebook That Still Runs TomorrowBatch Scoring: the Deployment Nobody Talks AboutServing Your Model as an App People Can OpenMonitoring, Drift, and How Models Die QuietlyThe Handoff to Engineering

Portfolio Deliverable: A deployed app with a URL, a batch scoring script, and a drift check

Start Module

Responsible Modelling and the Model Card

2h · Fairness audit + model card

You built it, so it is yours. Audit your own model's errors across groups, understand why the fairness definitions cannot all hold at once, decide what belongs in training data, write the model card that makes everything legible to somebody else, and learn to recommend against your own work.

Bias in a Model You Built YourselfFairness Metrics and Why You Cannot Have Them AllPrivacy, PII, and What Belongs in Training DataThe Model Card and the Rules You Now Live UnderWhen to Recommend Against Your Own Model

Portfolio Deliverable: A fairness audit, a completed model card, and a written deployment recommendation

Start Module

Capstone — The End-to-End Modelling Project

1.5h · Capstone project

Solstice Energy Co-op: a residential solar installer you have never seen, a vague brief from a commercial director, nine thousand leads, and traps nobody flags for you. You scope it, build it, evaluate it, audit it, and score yourself against a professional rubric.

Capstone Brief: Solstice Energy Co-opBuilding the Capstone ProjectFinal Review, Self-Score, and What Comes Next

Portfolio Deliverable: A complete modelling project for an unfamiliar business, self-scored against a professional rubric

Start Module
Professional Certificate in Data Science
Verified credential

Your AI Toolkit

Everything in this programme runs on free tiers. No paid plan, no cloud bill, nothing to install.

Claude / ChatGPT / Gemini

Your modelling partner: it writes the Python, brainstorms features, drafts the diagnostics and explains what it did — while you direct it and check every step

Free / $20/mo
Google Colab

The notebook where everything runs. pandas, numpy and scikit-learn arrive pre-installed; nothing to configure

Free
scikit-learn + statsmodels

Training, cross-validation, pipelines, calibration and evaluation — plus the power and sample-size calculations for experimental design

Free, open source
Streamlit Community Cloud

Putting your model behind a URL a colleague can open, in the shipping module

Free tier

Every exercise works on free tiers. Paid AutoML platforms — Vertex AI, SageMaker Autopilot, DataRobot — are covered in Module 5 so you can evaluate them at work and understand what they hide, but none are required and none are priced for personal practice.

About this program

Almost every data science programme is built for someone who wants to become a programmer. Weeks of Python syntax, then algorithms, then — eventually, if the learner is still there — the decisions that actually determine whether a model is any good. This certificate inverts that entirely, because the person it is written for already has the part that is hard to teach. If you can read a chart, reason about a business question, and interpret a regression somebody else fitted, you have the judgement. What you have been missing is the ability to build the thing, and in 2026 that gap is no longer a programming gap. An AI assistant writes the code from the first lesson. Your job — the job this programme spends 47 lessons making automatic — is to direct it, read what it produces, and catch what it got wrong. That is not a lesser version of programming. It is the skill that protects the work, and the evidence says it is in short supply: measured on realistic data-analysis tasks, capable models solve only a minority of problems end to end, and their signature failure is code that runs beautifully while answering the wrong question.

One business runs through every module, and it has traps planted in it. Harborline Freight moves about four thousand shipments a week and misses its promised delivery date on roughly one in nine. Operations does not want to know why last quarter went badly — they have a dashboard for that. They want to know which shipments moving this week will be late, so they can intervene on those and only those. You will define what “late” even means as an actual rule, and watch the entire project change three times as you change the definition. You will write down the dispatcher’s existing rule of thumb and measure it, because a model that cannot beat it should not ship. You will find the column that quietly contains the answer, produce a model that scores 0.98, and learn why that number was an alarm rather than an achievement. You will design the experiment that tests whether intervening actually helps, compute the sample size honestly, and discover it is larger than anyone wanted it to be. You will put the decision threshold where the costs say it belongs rather than at one half. You will find the depot your model is useless for. And then you will put the whole thing behind a URL somebody can open.

What makes this worth four weeks is that it shows the failures rather than describing them. You watch a rolling average computed one row too generously turn an honest 0.72 model into a 0.93 model made entirely out of the future. You watch a careful cost calculation pick the wrong threshold because the probabilities underneath it were never calibrated. You watch a fairness fix that equalises flag rates across groups make the error rate worse for the group it was meant to protect — and learn why the fairness definitions are mathematically incompatible whenever base rates differ, so choosing between them is a decision you have to own rather than a bug you can patch. Then the training wheels come off. Solstice Energy Co-op is a solar installer you have never seen: a vague email from a commercial director, nine thousand leads, and nobody to tell you which two columns are poisoned. You scope it and solve it alone. You finish with a portfolio of artefacts, a model card, and the habit that keeps a practitioner valuable through every model generation — never reporting a number you have not interrogated, and never building something you cannot defend.

Prerequisites

Complete these three short courses before starting the programme. They are Stage 0 of the same road, not a gate in front of it — and Module 0's honest self-assessment tells you in five questions whether you can skip straight past them.

Frequently asked

Do I need to know Python?

You need to have run a piece of Python once. That is the entire bar, and Module 0 Lesson 3 gets you there from nothing installed in about four minutes. You will not be writing Python from scratch at any point in this programme — an AI assistant writes it and you read it, interrogate it, and decide whether to trust it. That is not a beginner's compromise; it is how a great many working data scientists operate now, and the reading skill is the one that actually protects the work. Module 1 Lesson 3 is dedicated to it: a five-question read-through you run on any script an assistant hands you, including the technique of making the code print its own arithmetic so a silently dropped row cannot hide.

What is the difference between this and the Professional Certificate in Data Analysis?

One verb. Data Analysis ends at interpreting existing data and models — framing questions, cleaning, descriptive statistics, reading a regression, reading an A/B test, SQL, dashboards, executive narrative. This certificate begins at constructing a model that scores cases nobody has observed yet. The Data Analysis programme's own Module 5 draws that line explicitly and hands you over. Where the two touch, this programme bridges by name rather than re-teaching: you already know how to frame a question, so we go straight to what changes when the answer has to be a model — the target definition, the prediction window, the baseline, and whether each column was even knowable at the moment you score. If you have not done the Data Analysis certificate you have lost nothing; Module 0's self-assessment tells you honestly where you stand.

How long does it take to complete?

About four weeks at a steady pace — roughly 26 hours split between the lessons and the hands-on work, across 47 lessons. It is fully self-paced and built to be stopped and restarted: cumulative reviews sit at the one-third and two-thirds marks specifically because motivation dips there in any multi-week programme, and each one consolidates what you have built before the next stretch. The capstone rewards learners who take their time over it rather than sprinting for the credential.

Will AI replace data scientists?

The evidence points somewhere more interesting than yes or no. Measured on realistic data-analysis tasks, capable models still solve only a minority of problems end to end, and their signature failure is code that runs perfectly while answering the wrong question. In one randomised trial, experienced developers using AI tools were about 19% slower — while believing they had been roughly 20% faster. Studies of people reviewing AI-generated analyses find professionals routinely miss decision-critical flaws, including ones stated in plain language rather than buried in code. What that adds up to is not replacement but a shift in where the value sits: from producing the analysis to verifying it. This programme is built entirely around that shift, which is why every module teaches the check alongside the technique.

Do I need a paid AI plan or a cloud account?

No. Every exercise across all 47 lessons runs on free tiers: a free Claude, ChatGPT or Gemini account for the assistant, Google Colab for the notebook (free with any Google account, with pandas, numpy and scikit-learn pre-installed), and Streamlit Community Cloud for the deployment module. There is nothing to install and no credit card anywhere. Paid AutoML platforms are covered in Module 5 so you can evaluate them at work and understand what they automate and what they hide, but they are taught as things to assess rather than things to buy.

Is this a machine learning theory course?

No, and the omission is deliberate rather than a gap. You will not derive an estimator, prove a convergence result, or meet measure-theoretic probability. What you will do is everything a working practitioner does around the algorithm: define the target, audit for leakage, choose the validation scheme, pick the metric from the decision, calibrate the probabilities, place the threshold where the costs say, read the errors, and document the whole thing. That is where applied projects actually succeed or fail. The field mastery map behind this programme tags the deep theory explicitly as out of scope with the reason attached — the craft is practised without it, and requiring it would gate out the readers this programme is built for.

What do I actually have at the end?

Artefacts, not a badge. A written project brief with a target defined as a rule and a baseline stated before any code. A leakage audit you ran yourself. A reproducible feature pipeline. A tuned model with an honest held-out score and a confidence interval on it. An experiment design with a computed sample size and a pre-registered stopping rule. A cost-justified decision threshold. A per-slice performance table including the slice where your model is bad. A deployed app with a URL. A drift check. A completed model card. A written deployment recommendation. And a capstone you scoped and solved alone on a business you had never seen.

Is this certificate recognised by employers?

It carries a verifiable credential ID for your professional profile, but the honest answer is that the artefacts do more work than the certificate does. In a hiring conversation, walking someone through the leakage you found in your own data, the baseline you measured before you built anything, and the slice where your model underperforms is a far stronger signal than a line on a CV — because those are precisely the things that separate someone who has shipped a model from someone who has completed a tutorial. It is not an academic qualification and does not replace one. What it replaces is the portfolio gap.

Which AI tools will I use?

A general assistant — Claude, ChatGPT or Gemini — for every module, deliberately tool-agnostic because the discipline transfers and the tools will not be the same in three years. Inside Colab you will also meet Google's built-in Gemini data science agent, which will plan and write an entire analysis notebook from a described goal; it is genuinely capable, and Google's own material notes plainly that it may make mistakes, which is the best possible argument for the reading skill this programme teaches. Module 5 additionally surveys the AutoML landscape, from free open-source options through to enterprise platforms, so you can judge them rather than be sold them.

I am an analyst, not a developer. Is this actually for me?

It is written for you specifically, and the whole design follows from that. The reader this programme assumes can read a chart, reason about a business question, read SQL, and interpret a regression someone else fitted — and has written perhaps twenty lines of Python in their life. Everything follows from that: AI writes the code, the load-bearing skill is reading it critically, every term of art gets defined on first use, and the domain jargon is treated as the bigger wall than the AI jargon because for career-changers it usually is. What the programme does not do is pretend the modelling decisions are easy. They are the hard part, they are where projects die, and they are the part an analyst is unusually well-equipped to learn.

Does this cover deep learning or large language models?

Not as buildable techniques, and Module 5 explains why in some detail. For the tabular business data this programme is about — rows and columns out of operational systems — gradient-boosted trees remain the working default, and reaching for a neural network usually buys nothing while costing a great deal. So deep learning is named, placed accurately on the map, and handed to the Master Certification, where it belongs alongside production machine learning and causal inference at depth. Being clear about where a technique stops being the right answer is part of the craft rather than an omission from it.

What comes after this certificate?

A Master Certification that picks up exactly where this one stops: causal inference beyond difference-in-differences, variance reduction and sequential testing, deep learning and foundation models, production machine learning as an engineering discipline, and leading the work rather than doing it. That is a genuinely different craft and an optional one — you do not need it to be excellent at this job. The more important thing this programme leaves you with is in Module 0 Lesson 4: the method for having an AI teach you a technique nobody wrote a lesson about, and verifying what it tells you in a subject you do not yet know. The capstone's final lesson marks exactly where you stand on the map and what the next steps are.

Ready to build your first model?

Start Learning
First 2 lessons free · $9/mo Pro