Signal archive

Signal

Issue 4 · July 28, 2026 · 4 min read

Statistics Is Having a Quiet Comeback in Machine Learning

AI hiring is surging while half of genAI projects get abandoned. The gap is measurement: calibration, uncertainty, and metrics that hold up outside a demo.

"I keep saying that the sexy job in the next 10 years will be statisticians. And I'm not kidding." - Hal Varian (Chief Economist, Google)

Everyone wants to train bigger models. Almost nobody wants to prove those models actually work.

This week we're talking about the quiet comeback of statistics skills in machine learning, and yes, this can get you a very comfortable job.

Here's the idea: companies are drowning in AI demos and starving for people who can measure whether anything improved. According to the U.S. Bureau of Labor Statistics, employment for statisticians is projected to grow about 9% from 2024 to 2034, nearly three times the average growth rate across all occupations. Meanwhile, Indeed's Hiring Lab found that U.S. job postings mentioning AI surged more than 130% by the end of 2025, even as overall hiring stayed weak.

That hiring wave is colliding with a brutal reality check. Gartner reports that by the end of 2025, at least half of generative AI projects were abandoned after proof of concept, often because of unclear business value, weak risk controls, or poor data quality. McKinsey's 2025 State of AI survey found that while 88% of organizations use AI in at least one function, only about 6% qualify as high performers. RAND's research points to a common root cause: teams optimize the wrong metrics, then discover too late that the model solved the wrong problem.

To see what bad statistics cost at scale, remember Google Flu Trends. It became a poster child for big data, then famously overshot CDC flu estimates by more than double in one season and stayed high for 100 of 108 weeks. Researchers later showed the system had overfit noisy search terms and fallen into classic sampling traps. More data did not save it. Better statistical reasoning might have.

In machine learning terms, statistics is how you separate signal from noise: experiment design, uncertainty, bias, and evaluation that holds up outside a demo.

Now I'm going to explain what this means for you:

The Skill Employers EXPECT

Learn statistical foundations for ML. Most courses jump straight to model architectures. Companies hire people who can:

  • State a hypothesis clearly
  • Choose the right evaluation metric
  • Estimate uncertainty with confidence intervals
  • Spot sampling bias and leakage
  • Decide when a result is real vs lucky

The Skill That Separates You

Learn model calibration.

A preschooler can report accuracy. Strong ML engineers can tell you whether a "70% confidence" prediction is actually right about 70% of the time. You should know how to:

  • Build reliability diagrams
  • Compute Expected Calibration Error (ECE) and Brier score
  • Apply Platt scaling and isotonic regression
  • Produce prediction intervals, not just point estimates
  • Choose decision thresholds based on real false-positive and false-negative costs

The Project To Learn These Skills This Week

Build a calibrated customer churn predictor.

Dataset: Telco Customer Churn (or any public binary classification dataset with class imbalance)

Requirements:

  • Use a stratified train / validation / test split and document how you checked for leakage.
  • Train two models: logistic regression as the baseline, and gradient boosting as the challenger.
  • On the held-out test set, report accuracy, precision, recall, ROC-AUC, and Brier score for both models.
  • Plot a reliability diagram for each model before calibration.
  • Calibrate the challenger with Platt scaling and isotonic regression, then recompute ECE before and after.
  • Bootstrap at least 1,000 resamples to produce 95% confidence intervals for AUC and ECE.
  • Assume a false negative costs 5x a false positive, then pick the decision threshold that minimizes expected cost.
  • Write a short ship / no-ship memo: which model wins, which calibration method you recommend, what threshold to use, and what residual risk remains.

This project teaches one of the most important lessons in machine learning:

A model that cannot be measured honestly cannot be trusted in production.

If you want to sharpen your machine learning skills even more, I also selected a challenge problem for you this week.

If you learned something from this newsletter, make sure to forward it to a friend.

F1 Score

Easy · ~15 min

Concept: model evaluation

Ready to practice?

Turn weekly insights into hands-on ML skills on GRADuateML.