Roadmaps / Python / Who this is for
Read first
Who this is for
Hours by path. A Senior who skims Week 1 and skips Week 0 does about 120 hours. A Staff reader doing Weeks 3, 4 and 9 to 16 needs 10 weeks, 80 hours: 27 weeks at 3 hours a week. The work version is a separate effort of about 30 hours of work time. A Principal does Phase 4 (32 hours) plus the work version, about 62 hours.
| You are | Start at | Skip | Your assignments | Your milestone scope | Aim for |
|---|---|---|---|---|---|
| Fresher (under a year of work; one language, Git, HTTP) | Week 0, then Week 1 | Nothing. Do all the weeks, and plan 20 | Practice projects 1 and 2 in each phase, and checkpoints 1 to 4 | Core scope: one service, one worker pool, no free-threaded build | 2 Sound on every dimension |
| Senior (5 to 8 years, ships services) | Week 2 (skim Week 1) | Week 0 | All practice projects, checkpoints 1 to 4 | Adds the free-threaded comparison, a typed public API and ADRs 5 to 7 | 3 Proven on every dimension |
| Staff (10+ years, sets direction) | Weeks 3, 4 and 9 to 16 | Weeks 1, 2 and 5 to 8 | Checkpoints 2, 3 and 4, and the work version (Checkpoint W) | Adds a typing and packaging policy, an upgrade plan and a cost model | 3 on all, 4 on two |
| Principal (15+ years, sets strategy) | The milestone section, Phase 4, then Interview topics | The weekly tables of Phases 1 to 3 | The work version on a real codebase, plus a checklist others reuse | Adds a decision on a Python standard for several teams, with a measured outcome | 4 on at least two |
Prerequisites for a fresher. If one is missing, do Week 0 first.
- You can write functions, classes and loops in Python.
- You can use a terminal and Git.
- You know what a list, a dict and a set are.
- You know what an HTTP request and a SQL
SELECTare.
Career change (for example a Java or JavaScript engineer moving to Python): start at Week 1. Typing and packaging are the biggest differences, and both are easier if you already use a build tool.