Scalable AI

Bridging Theory, Understanding, and Practice

Fall 2026 | UC Berkeley

Large-Scale AI as an End-to-End Engineering Discipline

Announcements: Course information will be updated regularly. Check back for enrollment details, assignment deadlines, and lecture materials.

Course Overview

Central inquiry: How do we build, train, and deploy large-scale AI systems by treating them as full-stack engineered artifacts, where hardware constraints, software stacks, and optimization dynamics jointly determine model behavior and performance?

This course examines the principles required to build, train, and deploy large-scale AI models. We treat large-scale AI as an end-to-end engineering discipline, where a model is a computational graph that must be trained, specialized, evaluated, deployed, monitored, and iterated on, under hard constraints from hardware, data, and serving economics.

The course follows the lifecycle end to end:

Architecture β†’ Pre-training β†’ Post-training β†’ Efficient inference β†’ Applications β†’ Research greenfields

Resources

Syllabus (PDF)
Course policies, project expectations, assignment workflow, and course structure.
Tip: If your browser opens the PDF instead of downloading it, click β€œDownload” in the PDF viewer.

Course Team

Logistics

Class Logistics

Course Number
EE 290 / 194
Instructors
Teaching and Support Staff
Nathan Henry; Hanchen Li; Mayank Mishra; Venkat Srinivasan (NVIDIA infrastructure and technology)
Full staff cards + photos in Course Team.
Lecture Time
Mondays & Wednesdays, 12:30 PM – 1:59 PM
Location
The Gateway Building B1022
Office Hours
  • Instructor office hours: Mondays & Wednesdays 2 - 3 PM, Gateway 1110B
  • GSI office hours: Mondays 9:30 - 10:30 AM, Gateway B1009
  • Venkat's office hours: by request
Assignment Checkoffs
Checkoff slots by sign-up
Resources
Gradescope entry code: posted on Ed

Communication

Ed only. Please post all course questions on Ed (course discussion board). We do not use Slack or other channels for course Q&A. If you have not been automatically added, the join code will be shared in lecture.

Once we finalize the enrollment, we will purge all non-students from the course forum to encourage free discussion among students.

Compute

Teams are 8 groups of 4. Each group receives 1 H100 node (8Γ—H100) for the semester (8 total nodes on GCP). Each group is assigned a single static external IP address for SSH access.

Course questionnaire (Week 1): a short onboarding questionnaire released in the first lecture; enrollment/compute allocations will be finalized by the end of the second week.

Practical Tools

Students will gain hands-on experience with industry-standard tools and frameworks throughout the course:

Consolidated Schedule

Everything in one place: lecture plan, dated timeline, deadlines/milestones, and recommended readings. Dates below are for Fall 2026. Lecture plan subject to change.

Date Lecture / Events Recommended Readings / Resources Notes
Part 1: Architecture. Defining the Computational Graph and Scaling Strategies
Aug 26
L1. Course Overview and the Modern AI Stack
Key topics
  • Course goals, structure, and expectations
  • The full-stack view: hardware ↔ software ↔ optimization
  • Lifecycle map: architecture β†’ training β†’ post-training β†’ inference β†’ applications
Aug 31
L2. All About Performance (Part 1)
Key topics
  • Matrix multiplication as the basis of deep learning
  • The Roofline model and memory bandwidth bottlenecks
  • Component-level cost analysis (compute vs. memory vs. communication)
  • The economics of tokens: training vs. serving tradeoffs
Also:
  • A1 released (Performance Engineering Assignment) Release
Sep 2
L3. All About Performance (Part 2)
β€”
Sep 7
Labor Day No class
β€”
Sep 9
L4. Architectures to Break Bottlenecks: MoE, Sparse & Long-Context Architectures
Sep 14
L5. Parallelism Strategies
Key topics
  • Parallelism mechanics (e.g., multi-dimensional parallelism)
  • Interconnect topology and communication costs
  • Automated orchestration and practical scaling patterns
Sep 16
L5. Parallelism Strategies (continued)
L6. FlashAttention + Sonic MoE
Sep 21
L7. NeMo AutoModel
Part 2: Pre-Training of Language Models. The Engineering of β€œBase Models”
Sep 23
L8. Introduction to Pre-Training
Key topics
  • Tokenization fundamentals
  • The causal language modeling (CLM) task
  • Pre-training fundamentals and scaling considerations
  • How to evaluate pre-trained models
Also:
  • Hypothesis statement v1 due Milestone
β€”
Sep 28
L9. Pre-Training (Part 2): Data for Pre-Training
Key topics
  • Data curation: deduplication, quality filtering, and mixture design
  • Curating corpora at scale with NeMo Curator
Also:
  • A1 due Deadline
  • A2 released (Pre-Training Assignment) Release
β€”
Sep 30
L10. Modern Architectures + Modern Optimizers
Key topics
  • SGD-family methods and adaptive optimizers (Adam/AdamW)
  • Learning rate schedules, warmup, and stability
  • Gradient clipping, normalization, and numerics
  • Batch size, effective step size, and scaling behavior
β€”
Oct 5
L11. MARS Lecture
β€”
Oct 7
L12. Case Study: The Pre-Training of Nano-V3
Also:
  • Project proposal v2 due Milestone
β€”
Part 3: Post-Training of Language Models. Specializing Models Through SFT and RL
Oct 12
L13. Intro To the LLM Post-Training Lifecycle and Evaluation
Key topics
  • Differences between pre-training and post-training data
  • Chat templating and training fundamentals
  • Post-training benchmarks and evaluation practices
β€”
Oct 14
L14. The Data Powering Post-Training: SFT Data Engineering and RL Environments + Details in Specific Domains
Key topics
  • Synthetic data generation pipelines
  • Rejection sampling and quality scoring
  • Skills mixtures and data balancing
  • RL environment construction and reward design basics
β€”
Oct 19
L15. Building SFT Datasets: Generation, Tooling, and NeMo Data Designer
β€”
Oct 21
L16. Using the NeMo RL Stack for RL Post-Training + NeMo Gym
Also:
  • A2 due Deadline
  • A3 released (Post-Training Assignment) Release
β€”
Oct 26
L17. Case Study: Post-Training of Nemotron-NanoV3
β€”
Part 4: Efficient Inference. Deployment Preparation and High-Performance Frameworks
Oct 28
L18. Fundamentals and Overview of High-Performance Inference Frameworks
Key topics

A systems overview of modern inference engines, batching/scheduling, memory management, and throughput/latency tradeoffs.

β€”
Nov 2
L19. Efficient Inference (Part 2): Inference Engines
β€”
Nov 4
L20. High-Performance Inference in Practice: Dynamo, TRT-LLM, vLLM, and SGLang
Key topics

Serving engines and control runtimes for LLM applications: throughput optimization, KV cache management, and efficient scheduling.

Also:
  • A3 due (Post-Training Assignment) Deadline
  • A4 released (Inference and Serving Assignment) Release
β€”
Nov 9
L21. Grok LPX
Also:
  • Midterm check-in report due Milestone
β€”
Nov 11
Veterans Day No class
β€”
Part 5: LLM Applications and Use Cases. Building Real-World AI Systems
Nov 16
L22. Fundamentals of Context Engineering
Key topics

Designing prompts, retrieval, memory, and tool usage under latency/cost constraints and reliability targets.

β€”
Nov 18
L23. Harness Design
Key topics

Methods for engineering software harnesses for modern LLMs.

β€”
Nov 23
L24. Safety and Security (Part 1): Deployment Guardrails
β€”
Nov 25
Non-Instructional Day No class
β€”
Nov 30
L25. Safety and Security (Part 2): Open-Weight Safety
β€”
Part 6: Research Greenfields. Emerging Research Directions
Dec 2
L26. Greenfields in Performance & Accelerators
Also:
  • A4 due (Inference and Serving Assignment) Deadline
β€”
Dec 7
L27. Greenfields in Pre-Training and Post-Training
Also:
  • Draft project report due (submit on Gradescope) Milestone
β€” Peer review cycle
Dec 9
L28. Greenfields in Inference
Also:
  • Final project presentations (short talks) Milestone
β€”
Dec 10
Peer review due Milestone
Submit on Gradescope
β€”
Dec 11
Poster session Milestone
No formal lecture
β€”
Dec 16
Final deliverables due Milestone
Code + final report
β€”
Dec 18
Impact update Milestone
Proof of impact document
β€”

Grading & Policies

Grading Breakdown

This course has no exams. Evaluation is based on assignments, a semester-long research project, an explainer video, and participation.

Component Weight
Research project 50%
Assignments 35%
Explainer video 10%
Attendance & participation 5%
Important: Failing any one component fails the class. You must complete every component satisfactorily.

Commitment & Letter Grading

This course requires sustained weekly engagement (group work, compute usage, and in-person checkoffs). It must be taken for the maximum number of units. Letter grade only (no Satisfactory/Non-Satisfactory).

Assignments

There are four group-based assignments, each spanning roughly 3–4 weeks. Assignments include conceptual questions and hands-on experiments (implementation, profiling, scaling, analysis) with an in-person oral checkoff/presentation per assignment.

All assignment release/due dates are listed in the Consolidated Schedule.

  • A1: Performance Engineering Assignment
  • A2: Pre-Training Assignment
  • A3: Post-Training Assignment
  • A4: Inference and Serving Assignment

Late Policy

You have 3 total slack days across the semester for assignments. At most one slack day may be applied to any single assignment (extends deadline by 24 hours). No other late work is accepted without an approved exception.

Enhancements

Your assignments will also be graded on enhancements -- contribute meaningfully by adding questions, or reframing the programmatic part to be more challenging. Each group only needs to enhance one assignment. Out of the 35% of your grade that is reserved for assigments, 10% will be graded based on enhancements, and the other 25% will be graded based on the core assignment.

Research Project

The research project is group-based and open-ended, with an emphasis on producing something useful to the community. Expect 1–2 project check-ins with course staff over the course of the semester.

All project milestones and dates are listed in the Consolidated Schedule.

  • Technical quality (40%): hypothesis clarity, depth, correctness, rigor, and artifact quality (code + report + other deliverables).
  • Impact (10%): evidence of external usefulness (e.g., PR merged into open source, reproducible benchmark, public report, arXiv preprint).
  • Peer review: each group provides a structured review of another group’s report.

Explainer Video

Each student records a short explainer video on a topic from the course: record yourself at a whiteboard giving a clear, simple explanation of a concept from lecture, where you go further than we had time to.

These are made for your classmates, so make them as helpful as you can. Full credit requires going into more depth on the topic than lecture does, not restating it. Each video is due a month after its topic is introduced in lecture. No video editing is required.

Attendance & Participation

Attendance is required. Participation includes contributing to in-class discussions and project check-ins, posting/answering on Ed, and providing constructive comments on lecture notes and slides.

Academic Integrity

Collaboration is encouraged within your group. Do not copy code or reports from other groups. If you use external code or AI assistants, cite the source clearly and ensure you understand the work you submit.

Infrastructure Notes

This course uses shared GPU infrastructure. For access/quota/networking issues, post on Ed and include timestamps, job IDs, logs, and a short repro description. Multi-node experiments require coordinating with another team to share nodes for a bounded window of time.

Submission platform (Gradescope): all written and code submissions are via Gradescope (entry code posted on Ed), unless explicitly stated otherwise. Oral presentations/checkoffs require sign-up and in-person attendance.