How to Become a Software Engineer
The generalist trunk that backend, frontend, full-stack, and platform careers fork from. Deep foundations in code, systems, and shipping product.
1. Programming Fundamentals
coreA Primary Language, Deeply
Pick one — Python, TypeScript, Go, Java, C# — and get past syntax. Understand its memory model, concurrency model, and error handling.
Data Structures & Algorithms
Arrays, hashmaps, trees, graphs, dynamic programming — not just for interviews. Knowing when a hashmap collapses O(n²) to O(n) is table stakes.
2. Version Control & Collaboration
coreGit Fluency
Beyond commit/push — rebase, cherry-pick, bisect, reflog. When production is broken and you need to find the commit that did it, this is what you reach for.
3. Computer Science Foundations
coreOperating Systems
Processes, threads, memory management, filesystems, syscalls. Explains every weird production behaviour you'll ever encounter.
4. Systems Design
coreDesign Fundamentals
Latency, throughput, availability, consistency. The five words every senior interview loop hinges on.
Caching Strategies
Cache invalidation is one of the two hard things. Learn Redis, cache aside, write-through, TTLs, and stampede prevention.
5. Testing
coreUnit Tests
Fast, deterministic, isolated. AAA (arrange-act-assert), test doubles, table-driven tests.
6. Databases
coreSQL
Every backend engineer writes SQL. Master joins, aggregations, window functions, and reading EXPLAIN plans.
7. Web Fundamentals
coreHTTP
Methods, status codes, headers, caching, cookies, CORS. The layer everything web-shaped runs on.
8. CI/CD & DevOps Basics
coreDocker & Containers
Every modern deploy is containerized. Learn images, layers, multi-stage builds, and image size hygiene.
GitHub Actions / CI Pipelines
Build, test, deploy on every push. Pipeline-as-code is the norm.
- docs free →
9. Security Fundamentals
recommendedOWASP Top 10
The vulnerabilities that ship in production every day. Read the list, understand each one, know how to prevent it in your stack.
10. Observability & Debugging
recommendedLogs, Metrics, Traces
The three pillars. Structured logs, RED/USE metrics, distributed tracing with OpenTelemetry.
Debugging in Production
Reproducing bugs from logs alone, reading heap dumps, using profilers. The skill that separates senior from mid.
- docs free →
11. Cloud Fundamentals
recommended12. Career & Craft
optionalWriting Technical Design Docs
Every non-trivial change deserves a doc: problem, options, chosen approach, rollout plan.
- blog free →
Want a personalised version?
This roadmap is the same one our platform uses internally, but the logged-in version lets you tick off topics as you complete them, track a personalised First 90 Days plan, and see your AI-durability score against this role. All free.
Open the interactive roadmap →