M0-L3.3Handbook Reading Paths
In one sentence: Readers choose how deep to go in each module (Know, Use, Build or Design) based on their background, skip what they already master, and treat Module 0 and the Module 7 practicum as required for everyone.
What it is
Section titled “What it is”The handbook is written so that someone with no software background can read it start to finish. Most readers don’t need to. A reading path is a plan for which modules to read, at what depth, given what you already know.
Four depth levels
Section titled “Four depth levels”| Level | You can… | Example (Module 4, authentication) |
|---|---|---|
| Know | Explain the concept and recognize it in a conversation | Explain the difference between authentication and authorization |
| Use | Work with existing tools and configurations correctly | Set up an API key and a read-only role for an agent |
| Build | Implement it yourself in a working system | Implement an OAuth flow and per-user permissions for a tool |
| Design | Choose between approaches and justify the trade-off for a customer | Design the permission model for a multi-tenant deployment and defend it to a security reviewer |
Why an FDE needs this
Section titled “Why an FDE needs this”FDE preparation is broad, and time is limited. Without a path, beginners drown in Module 1 detail and experienced engineers skip Module 5, which is exactly the module they most need.
Key concepts
Section titled “Key concepts”Suggested starting paths
Section titled “Suggested starting paths”| Background | Usually needs most | Usually can go lighter on |
|---|---|---|
| Domain expert from finance, healthcare or marketing | Modules 1–3 at Use, Module 5 at Build | Module 4 at Know to Use |
| CS student or junior engineer | Modules 2, 3 and 5 | Parts of Module 1 after a self-check |
| Backend or full-stack engineer | Modules 2, 3 and 5 | Most of Module 1 |
| AI engineer | Modules 4 and 5; persistence and multi-agent parts of Module 3 | Much of Module 2 |
| Consultant or solutions engineer | Modules 1–3 (coding and systems literacy) | Parts of Module 5, though the practicum is still required |
| Senior full-stack and AI engineer | Module 5 and the four archetypes in Module 6 | Modules 1–2; go straight to the practicum |
These are defaults, not prerequisites. Check yourself against each module’s lesson outcomes and skip what you can already demonstrate.
Required for everyone
Section titled “Required for everyone”Module 0, because the rest of the handbook uses its vocabulary, and the Module 7 practicum, because running one full engagement is the only way to show the whole loop.
How each page is built
Section titled “How each page is built”Every knowledge-point page has the same structure: a one-sentence definition, what it is, why an FDE needs it, key concepts, common misconceptions, typical interview questions with model answers, Learn more resources and related pages. Read the one-sentence definition and misconceptions first if you are reviewing; read the whole page if the topic is new.
Common misconceptions
Section titled “Common misconceptions”- “Experienced engineers can skip straight to the interview module.” Module 5 and the practicum test skills that engineering experience alone does not build.
- “Know level is enough for everything outside my specialty.” FDEs work across the whole system. Aim for at least Use on anything you will touch in a customer environment.
Typical interview questions
Section titled “Typical interview questions”How have you prepared for the parts of this role outside your background?
Describe a deliberate plan rather than general reading: which areas you identified as gaps, what depth you aimed for, and one artifact that proves it (a deployed project, an eval set, a discovery write-up).
Learn more
Section titled “Learn more”- No external resource needed. The Background Pathways table in the syllabus gives the full per-module recommendations.