Roadmaps / Go / 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 process, constant limits, no gRPC | 2 Sound on every dimension |
| Senior (5 to 8 years, owns services) | Week 2 (skim Week 1) | Week 0 | All practice projects, checkpoints 1 to 4 | Adds the load test in CI, a fault suite and ADRs 5 to 7 | 3 Proven on every dimension |
| Staff (10+ years, sets direction) | Weeks 3 and 4, then Weeks 9 to 16 | Weeks 1, 2 and 5 to 8 | Checkpoints 1, 3 and 4, and the work version (Checkpoint W below) | Adds a service level objective, a runbook and a Go upgrade policy | 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 service, plus a checklist others reuse | Adds a service template for many 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, loops, structs and interfaces in Go or another language.
- You can use a terminal and Git.
- You know what an HTTP request, a response and a status code are.
- You can write a SQL query with a join.
Career change (for example a Java or Python service owner moving to Go): start at Week 1. Goroutines, channels and explicit errors are the biggest differences.