Data science & AI,
taught from scratch.
The complete path from your first line of Python to production AI — become a data analyst, data scientist, or AI engineer.
Pick the job. We’ll sequence the courses.
The right courses in the right order, taught from scratch. Three headline tracks here; 9 in all.
Data Analyst
Answer real business questions with data — SQL, pandas, charts that tell the story, and the analytics sense to turn numbers into decisions.
Data Scientist
From SQL to statistical rigor to communicating results that change decisions.
AI Engineer
Build AI products from first principles — neural nets, transformers, LLMs, RAG and agents, all the way to shipping them in production.
20 courses, 662 lessons. All of it free.
In learning order, grouped the way the field actually fits together. Each card opens its first lesson straight away.
The lessons readers open first.
Prep & reference, when it counts.
Interview rounds, a quick definition, the syntax you forgot — the fast lane next to the courses.
Interview Q&A
Real questions across SQL, ML, Python, statistics & AI — each with a worked answer and the trap to avoid. Filter by the role you're chasing.
Glossary
245 data & AI terms in plain English — from overfitting to RAG — each linked to a lesson.
Look it upCheat sheets
6 dense one-pagers for Python, SQL, Pandas, NumPy, Git & scikit-learn — the syntax you actually reach for.
Grab oneActivation checkpointing makes GPU memory a scheduling decision
Large-model training is constrained by more than weights. Activation checkpointing changes which forward tensors survive, trading recomputation for a smaller peak-memory footprint.
RAG poisoning is an evidence-integrity problem
A retrieval system can reason perfectly from corrupted evidence. Defending RAG means governing what enters the corpus, preserving provenance, isolating tenants, and treating retrieved text as untrusted data.
Six system-design boundaries that prevent category mistakes
Stateless vs stateful, Lambda vs ECS, database vs cache, queue vs stream, retrieval vs reranking, and monitoring vs tracing—explained as operational contracts.
Token theft in AI agents is an architecture failure
Prompt injection gets the attention, but credentials turn a confused model into an authenticated attacker. The fix is to keep tokens out of model context and authorize every action at runtime.
From scratch, with the math
Every idea is built up from first principles — derivations traced step by step, then turned into working code you can follow line by line.
Every output is real
Code samples ship with their actual verified output — run before publishing, never guessed. What you see is what the code does.
One clear idea at a time
Short lessons in a deliberate order — each one hands off to the next, so the whole field clicks together instead of piling up.
Read more about datarekha · questions? get in touch