GuideIntermediate

AI System Design Interview Guide

Almost every AI engineer hiring process includes a round that does not exist in traditional software interviews: you are asked to design, in front of another person and in English, a system that uses a language model. An assistant over a company's documents, an agent that takes actions, a chat for a million users. You are not graded on transformer math. You are graded on how you think: whether you ask before you draw, whether you turn the answers into numbers, whether you know what the model decides and what the code decides, and above all whether you can **choose and say out loud what you give up** with each decision. This guide trains that round with eight original cases, ordered by how often they show up in real interviews. Each case takes place at a fictional company and follows the same seven-step script: clarify, set the boundary, sketch, name the trade-offs, evaluate and cost it, break it, and wrap up. The numbers (requests per second, tokens, cost per request, latency) come from short Python scripts that run without an API key. Each case ends with a complete interview written in English and annotated with a rubric, and every lesson gives you the exact phrases to lead that step in English. After the cases, two modules for the rounds people forget to prepare: the **forward deployed** interview, where you break down an ambiguous business problem and talk to a simulated client, and defending **a project you built** as if it were a take-home.

lessons
66
modules
11
available in
English · Spanish
access
Free
Outcomes

What you'll be able to do

  • Lead an AI system design round from start to finish with a structure the interviewer can follow
  • Clarify requirements before drawing and turn the answers into scale, cost and latency figures
  • Decide whether a system answers or acts, and keep authorization and amounts outside the model
  • Name every trade-off in the form "I choose, I give up, I would revisit it if", under pressure too
  • Propose how each part of the system is evaluated and defend a cost per request with a calculation
  • Say how a design fails (slow, with an error, or wrong but convincing) and what the fallback does
  • Critique someone else's design and rank its problems by the damage they cause
  • Lead a forward deployed interview: decompose, ask, explain without jargon and deliver bad news
  • Defend a project of your own as a take-home, with its evals page and what did not work
  • Hold the whole conversation in English with prepared phrases for every step
Before you start

What you need to bring

It's for you if...

  • Developers and AI engineers who have already built something with a model through an API and are preparing for AI engineer, applied AI or forward deployed interviews
  • People who know how to build a RAG system or an agent but get stuck explaining why they designed it that way
  • People who have the technical side but need to hold the conversation in English

Requirements and materials

  • Having built something with a language model through an API (a RAG system, an agent or a function with tools)
  • Knowing the common pieces by name: embeddings, retriever, tool calls, evals
  • Basic Python to run the number scripts (Python 3.12 or later, standard library only)
  • Technical reading in English; the guide gives you the phrases to speak
  • No API key: no script calls a model
Content

The syllabus, module by module

Open any of them to see its lessons.

Bootcamps

Learn with live classes and reviews of your work.

In a group or 1:1, depending on your schedule.

Common questions

What people usually ask

Start whenever you like

Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!