🎉 The Product Data Scientist track is free. Start Free →
⚡ Free · Step by Step · At Your Own Pace

Become a Product Data Scientist

A step-by-step path from working analyst to product data scientist: SQL, statistics, experiments, product sense and interview prep. Plan on about 12 months at 6.5 hours a week, or go at your own pace.

See the Roadmap

✓ No account needed. Your progress saves in this browser.

Skills You'll Learn
52 Weeks · At Your Own Pace

Your Roadmap

Nine phases, in order. Pass a short quiz to unlock the next one.

The Course

One Course, One Path

Built for working analysts moving into product data science. It's free. A few weeks assign books, which you can often borrow from a library.

How It Works

Same Rhythm Every Week

About 6.5 hours a week, split into the same four blocks. You never have to decide what to do next.

20m

Recall

Write down what you remember from earlier weeks before opening your notes.

1h50

Learn

Guess first, work through the material, then explain it in your own words.

3h

Practice

Solve problems on your own, then test yourself.

1h20

Ship

Save your work to GitHub and write a short summary of what you learned.

The Learning System

Backed by Learning Science

Built around study methods with strong research behind them in cognitive psychology.

1

Test yourself

You recall ideas from memory instead of rereading. In studies, this beat rereading on later tests.

2

Review over time

Topics come back after a week, a month and three months, so you keep what you learn.

3

Mix old with new

Old topics return alongside new ones, just like a real interview.

4

Pass before moving on

A short quiz unlocks each phase, so gaps get fixed early.

See the research

These studies tested the methods with other subjects and learners. No study has tested this exact course.

Want to go deeper? Try Andrew Huberman's episode Optimal Protocols for Studying & Learning. Data Craft isn't affiliated with him or the show.

How to Study

Your Study Routine

The same five steps every time. The lessons remind you.

1

Before

Start at your planned time, with your phone out of reach.

2

During

Try each problem before looking anything up. Pause briefly between problems.

3

Right after

Explain the idea out loud, then take 10 quiet minutes before your phone.

4

Next session

Write what you remember from last time before starting anything new.

5

Tonight

Protect your sleep. It helps new memories last.

Portfolio

Four Portfolio Projects

Each one answers a real business question and ends in a recommendation, not just charts.

1 · Product health report

"How healthy is this business, and where should the team focus?"

2 · Experiment analysis

"Should we launch this change?"

3 · Metrics framework

"How should success be measured, and what if it drops 10%?"

4 · Capstone decision

One real question, from framing to recommendation.

What you'll deliver and how it's scored
  • Project 1 (Weeks 9–10): SQL repo, funnel and cohort charts, 1-page memo.
  • Project 2 (Weeks 29–30): design doc, sanity checks, analysis notebook, launch recommendation.
  • Project 3 (Weeks 35–36): HEART table, metric tree, diagnosis memo.
  • Project 4 (Weeks 39–42): AI-use and verification log, memo and 5-minute video.

Rubric (score each 1–4; pass = 3+ on all)

  1. Question: clear, linked to a decision, scoped
  2. Correctness: checks shown, edge cases handled
  3. Recommendation: specific, with risks and confidence stated
  4. Communication: answer first, readable in 2 minutes
Practice with AI

Make AI Test You, Not Answer for You

Copy a prompt into any AI chat and get quizzed.

See the prompts

Concept quiz

Quiz me on [topic] with 5 questions that get harder, at product data scientist interview level. Ask one at a time. Don't reveal answers until I reply. After all 5, tell me my weakest area and give me 1 Anki card for it.

Product case interviewer

Act as a product data scientist interviewer at a top tech company. Give me one product case on [metric drop / feature success / launch trade-off]. Ask follow-ups like a real interviewer. Don't help me. At the end, score me 1–4 on: problem structure, metric choice, statistical rigor, recommendation. Be strict.

Experiment design drill

Give me a one-line feature idea. I'll write a full A/B test design. Then critique it on hypothesis, metrics, randomization unit, sample size, duration, and risks. Point out anything an interviewer would catch.

Questions or feedback?

We'd love to hear from you.

hello@learndatacraft.com