Skip to main content

Path Levels

The full roadmap is 96 weeks. That is too much to hold in your head on day one.

Use these three levels to decide what to do next.

Readiness still governs coursework use. Level 2 and Level 3 describe the intended long-range scope, but many of those semesters may be Scaffolded or Blueprint; check Curriculum Readiness before treating them as learner-ready coursework.

Level 1: Starter Path​

Purpose: build the foundation and prove that the learning system works.

Use this if: you are beginning the curriculum or rebuilding weak fundamentals.

Scope:

  1. Pre-Semester Launchpad
  2. Semester 0 Orientation
  3. Semester 1 Mathematical & CS Foundations

Expected evidence:

  • one stable study workspace
  • Git-based workflow
  • notes and retrieval practice
  • mathematical proof notebook
  • small code drills and tests
  • checkpoint and exam attempts

Outcome: credible foundations. Not job-ready yet.

Level 2: Engineer Core​

Purpose: become strong enough in algorithms, design, systems, networking, databases, and distributed-systems thinking to build nontrivial software with judgment.

Use this if: you finished Level 1, or you are filling the same prerequisites from outside sources.

Check Curriculum Readiness before starting any Level 2 semester. If a semester is not Learner-ready, Reviewed, or Battle-tested, use it as planning context unless the readiness page gives a narrower learner path.

Scope:

  • Semester 2: Algorithms & Data Structures
  • Semester 3: Software Design & Patterns
  • Semester 4: Systems Programming
  • Semester 5: Operating Systems & Networking
  • Semester 6: Databases & Distributed Systems

Expected evidence:

  • tested algorithms repository
  • refactoring and design notes
  • C/systems projects with debugging evidence
  • networked service or small deployment
  • database and transaction notes
  • at least one design artifact per semester

Outcome: engineering core. This is the middle that makes later architecture work real.

Level 3: Production And Architecture​

Purpose: turn engineering core skill into design, delivery, operations, and portfolio evidence.

Use this if: you already have the systems, database, and distributed-systems background that the advanced material assumes.

Check Curriculum Readiness before starting any Level 3 semester. Advanced scope here does not mean every page is ready as coursework.

Scope:

  • Semester 7: Software Architecture & Domain Design
  • Semester 8: System Design & Technical Leadership
  • Semester 9: Cloud Infrastructure & DevOps
  • Semester 10: Capstone Integration

Expected evidence:

  • architecture review packet
  • ADRs
  • API contract and compatibility policy
  • cloud deployment
  • CI/CD pipeline
  • runbooks, SLOs, logs, metrics, and operational notes
  • security review
  • capstone portfolio case study

Outcome: production-shaped portfolio evidence.

Most learners should ignore Level 2 and Level 3 until Level 1 is complete.

The right question is not "Can I finish 96 weeks?"

The right question is "Can I complete the next module and produce evidence?"