Serving, hardware sizing, streaming, client scoping, safe database access, Docker, and the capstone system design. The week that turns thirty days of code into something you can be hired on.

Seven build days, two live sessions, one ship day, one graduation. Monday, October 19 to Tuesday, October 27.

What this week is actually for

Everything so far has been a script on your machine. Week 4 turns it into a service, then asks the questions a client or an interviewer will ask about that service.

Day 25 is the odd one out and the most valuable. It has almost no code. It asks you to write a one-page discovery proposal for a real enterprise use case, because the Forward Deployed Engineer role pays what it pays for scoping ability, not for typing speed.

Day Date Focus Type
22 Mon, Oct 19 ‣ Build
23 Tue, Oct 20 ‣ Build
24 Wed, Oct 21 ‣ Build plus Live Session 7
25 Thu, Oct 22 ‣ Build
26 Fri, Oct 23 ‣ Build
27 Sat, Oct 24 ‣ Ship Day
28 Sun, Oct 25 ‣ Build plus Live Session 8
29 Mon, Oct 26 ‣ Build
30 Tue, Oct 27 ‣ Graduation

Live sessions this week

Session 7, Wednesday October 21, 7:30 PM IST, 90 minutes. Streaming with Server-Sent Events, and watching Time-to-First-Token drop on screen.

Session 8, Sunday October 25, 7:30 PM IST, 90 minutes. The capstone system design for 10,000 users, run as a live workshop with Excalidraw.

Session 8 falls on a Sunday rather than a Friday because Day 28 lands there when you count thirty consecutive days from September 28. Weekend attendance is usually better for working engineers, so it stays where it is.

Week 4 has no Read Day

Weeks 1 through 3 each end with a Sunday paper. Week 4 does not, because the fourth paper, PagedAttention, is load-bearing for the Day 28 capstone and gets covered inside that session instead.

If you want the standalone write-up, read it on Saturday alongside your Docker ship day. Interview question 78 comes straight out of it.

What you have at the end of the week

A containerized FastAPI service with streaming, a hardware sizing calculator, a safe Text-to-SQL assistant, an enterprise discovery proposal, and a full architecture blueprint for 10,000 users.

That is Portfolio Build 4 of four. On Day 29 the four builds get assembled into one master repository, and on Day 30 you publish it.