Portfolio Ladder — Public Proof-of-Work¶
The portfolio is not a hiring document. It’s a forcing function.
When you know someone can read your implementation, you write it correctly instead of approximately. When you commit to publishing a derivation, you derive it instead of recalling it. When your Codeforces rating is publicly visible, the number doesn’t lie. Public artifacts create accountability loops that private notes never do — and they produce clarity of thought as a side effect, because you cannot fake a working implementation or a coherent explanation.
This is a ladder of 8 rungs, each representing a distinct mode of proof: derivation, implementation, communication, tracking, application, synthesis, competition, and narrative. Two of the eight are hard gates — non-negotiable completion requirements by M9. The rest build the foundation that makes those gates reachable.
The M9 Pitch¶
“An applied ML engineer who rebuilt CS foundations from scratch — complexity theory through competitive solving — over 9 months, shipping 6 public proof-of-work artifacts that demonstrate systematic algorithmic thinking.”
This sentence only becomes true if the artifacts exist and are verifiable. The portfolio is how you make it true.
The 8 Rungs¶
# |
Rung |
Month |
Mode of Proof |
|---|---|---|---|
1 |
M1–M2 |
Derivation |
|
2 |
M2–M3 |
Implementation |
|
3 |
M3–M4 |
Communication |
|
4 |
M4–M6 |
Deliberate Tracking |
|
5 |
M6–M7 |
Application |
|
6 |
M7–M8 |
HARD GATE — Synthesis |
|
7 |
M8–M9 |
HARD GATE — Competition |
|
8 |
M9 |
Narrative |
The Two Hard Gate Rungs¶
Rung 6 — DP Pattern Handbook must be complete by end of Month 8.5. It is the deepest synthesis task in the portfolio. DP is where most self-taught engineers stall permanently, and a handbook written from genuine understanding (not copied) is rare enough to be a meaningful signal. If you skip it, the M9 pitch loses its strongest substantive claim.
Rung 7 — Codeforces Rating ≥ 1200 must be attempted by end of Month 9 (minimum 5 rated contests). A rating cannot be fabricated. It is publicly timestamped, publicly verifiable, and earned in competition conditions under time pressure. It is the only artifact in this portfolio that cannot be written after the fact. Miss the attempts, and the capstone story has no competitive proof.
Why Public, Even Without Job Hunting¶
Three reasons, in increasing order of importance:
Accountability — A private repo is easy to abandon. A public one has even one silent reader. That’s enough.
Clarity test — If you cannot explain something publicly without embarrassment, you don’t understand it yet. The portfolio exposes gaps that private notes hide.
Evidence of journey — In 3 years, you will want proof that you did this. Screenshots delete. Public commits don’t.