AI Foundations
People who already use these tools daily and want to build with them — analysts, product people, and engineers early in their careers.
Length
6 weeks, part-time
Commitment
~5 hours per week
Cohort
12 live sessions, 20 seats
You do not need anything to start this one
None. You will write some Python, and the track teaches the Python it needs.
Every other technical track expects professional engineering experience. This one does not, and it is the way in.
What you cover
6 modules
Each one is worked through live, then built on between sessions.
- 01What the model actually is — tokens, context, sampling, and why that explains the failures
- 02Prompting as specification — structure, examples, and the problems prompting cannot fix
- 03Retrieval, plainly — why a model needs your documents and how it gets them
- 04Making it do something — tools, APIs, and the shape of a working application
- 05Being wrong — hallucination, confidence, and telling good output from merely plausible output
- 06Judging it — a small test set, and proving a change helped rather than feeling that it did
You build it, then you defend it.
There is no exam and no pass for attendance. Some people do not pass first time.
The project
A small working application of your own, answering questions over documents you actually care about, with a test set you built and evidence that one change measurably improved it.
Read first
Some of this is free
The knowledge library covers a good deal of the same ground. Start there, and pay us only once you have decided the reviewed version is worth it.
Evaluation Harnesses For LLM Systems
The piece almost every team skips. How to build a golden set, design a rubric, use LLM-as-judge without being fooled by it, and turn "is this better?" from an argument into a measurement.
Inference Cost As An Architectural Constraint
Model-backed features carry a variable cost that rises with success. Context budgeting, caching, routing and cascades, batching, and the unit economics you need before the architecture hardens around you.
RAG Architecture That Survives Production
Retrieval quality sets the ceiling on answer quality, and chunking decides retrieval quality. Hybrid search, reranking, grounding and citation, re-indexing, and how to tell which half of the system broke.
Testing Non-Deterministic Systems
Assertion-based testing assumes one correct output. Model-backed systems do not have one. What replaces equality checks, where deterministic tests still belong, and what the test pyramid becomes.
Other tracks
The rest of the technical family
AI-Native Delivery
5 weeks, part-time
Teams adopting AI-assisted engineering who want the throughput gain to survive contact with review and production.
AI Engineering
8 weeks, part-time
Engineers building LLM applications, retrieval systems and agents who need them to hold up in production.
Agentic Systems Engineering
7 weeks, part-time
Engineers building systems that act on their own, and the leads accountable for what those systems do unsupervised.
Physical AI
7 weeks, part-time
Engineers moving from software-only AI to systems that act in the world, where being confidently wrong has consequences you cannot undo.
Web3 & Smart Contract Security
10 weeks, part-time
Engineers moving into contract development, and teams preparing a protocol for audit and mainnet.
Mobile Delivery
5 weeks, part-time
Mobile teams whose release cadence is set by store review rather than by their own decisions.
Take AI Foundations.
6 weeks, 12 live sessions, 20 seats, priced by region from $450. Places in the first cohorts are arranged directly.