Interviews and Capstone
Answer the Python questions interviewers really ask, with a runnable proof for each, then build and ship a complete document question-answering tool.
The first half of this phase is interview preparation done properly. Each topic takes a family of questions (core language, "what does this print?", object model and internals, coding rounds, production Python) and gives the precise answer, the reason behind it, and a program you can run to see it happen. An interviewer rarely wants a definition. They want to hear that you know why.
The second half is a capstone: a document question-answering tool called docqa. You plan it, build the core library (loading, chunking, a toy embedder, NumPy search, a model interface with a fake and a real client), add a command line with config, logging, streaming and retries, then test, package and ship it. Every piece uses ideas from earlier phases, so this is also the best way to find what you still need to revisit.
The phase ends with an honest map of where to go next: what an AI engineer, a forward deployed engineer and an AI scientist do day to day, which skills from this course each role leans on, and what to learn after it.
Practise this phase
Hands-on exercises: write the code, run it, and press Check to have it tested automatically.