3 min read · Notion
🎯 Frontend → Backend transition roadmap. 90 days. 5 phases. Production-grade systems thinking.
| Phase | Days | Focus | Status |
|---|---|---|---|
| Phase 1 — Foundations | Days 1–15 | TCP/IP, HTTP, OS, TLS, DNS | 🔘 Not started |
| Phase 2 — Core Backend | Days 16–35 | Go, REST, gRPC, Auth, DPoP | 🔘 Not started |
| Phase 3 — Databases & Distributed Systems | Days 36–55 | PostgreSQL, Kafka, CAP, Raft | 🔘 Not started |
| Phase 4 — Infrastructure & DevOps | Days 56–75 | K8s, Terraform, Vault, mTLS | 🔘 Not started |
| Phase 5 — Expert Systems | Days 76–90 | Observability, SLOs, System Design | 🔘 Not started |
Act as a Staff Backend Engineer with 10+ years of production experience at companies like HashiCorp, AWS, and Stripe. I am a frontend engineer transitioning to backend/systems engineering. Generate a strict 90-day, phase-based roadmap structured as: Phase 1 Foundations (Days 1–15), Phase 2 Core Backend (Days 16–35), Phase 3 Databases & Distributed Systems (Days 36–55), Phase 4 Infrastructure & Cloud-Native (Days 56–75), Phase 5 Expert Systems (Days 76–90). For each phase, give me: (1) exact topics in learning order with sub-topics, (2) 2–3 concrete production-grade projects with tech stack and deliverables, (3) 3–5 common beginner mistakes with the correct mental model, (4) how a real company (AWS/Uber/HashiCorp/Cloudflare) solved this exact problem at scale, (5) interview-level depth on key concepts.
📅 Daily Progress Tracker