Status: queued — starts the Monday after SWE 102’s finish line is met · Length: 11 weeks
How every week works: the four lanes, the rotation and the rules are in SWE 101. Notebook sections are numbered 103.1–103.11.


Why this course

By now the flagship is real and its AI feature is measured. What’s left is what senior-leaning interviews probe: designing a system out loud in 45 minutes, and the database, web and distributed-systems knowledge underneath it. The notes for all of it are written; the reps are not. So the Build lane becomes a design lane: one system design every other week, on the board, out loud, timed.

What moved out on purpose: link layer, subnetting, routing, congestion control, QUIC, NAT, database page layout, LSM trees, durability internals, Paxos and Raft. All good knowledge, rarely asked of a junior TypeScript or AI engineer. They’re in the CS spine below — later, not never.

Course finish line

  • Four system designs done out loud and timed: URL shortener, notification system, payment system, chat
  • Two full system-design mocks (45 minutes, with someone else asking if possible) and two timed coding mocks
  • “What happens when I type google.com”, one page from memory
  • One slow query from a real project fixed with EXPLAIN ANALYZE, before and after recorded
  • The project story at three lengths: 2 minutes, 5 minutes, 20 minutes of depth
  • Six behavioural stories in STAR form, from real projects
  • DSA: mixed review, five a week, plus one timed mock a week

Week 1’s first job is the audit of this course’s lessons.

DSA in this course

No new patterns. Every week: five problems drawn at random from NeetCode 150 problems not yet logged, plus one timed 45-minute mock. This is what interviews actually are — the pattern isn’t announced. Draw at least one graph problem every week; that’s the gap interviews exposed.

The eleven weeks

Week 1 — How to approach a design

Week 2 — Caching and load balancing

Week 3 — Messaging and communication

Week 4 — Architecture choices

Week 5 — Databases I: querying well

Week 6 — Databases II: changing data safely

Week 7 — The web, end to end

Week 8 — The request path and the event loop

Week 9 — Identity

Week 10 — Distributed systems, the essentials

Week 11 — Mock loops

  • Two full system-design mocks: ride-sharing, then video platform.
  • Two timed coding mocks.
  • The project story at 2, 5 and 20 minutes → the nextvibe story bank is the model.
  • Six STAR stories from real projects. Remote roles probe async communication hard.
  • The interview banks: 13 domains. Cover the answer, say it out loud, then compare.
  • By Sunday: every finish-line box ticked, or dated.

After the series — the CS spine

Not a course yet. When the series is done, or once employed, this becomes its own course through the usual make-a-course step:

↑ Back to Learning — How I Learn