Module 5: Portfolio & Specialization Assessment
Primary texts: Staff Engineer (Will Larson) · The Pragmatic Programmer (Thomas & Hunt) -- revisit, not re-read.
Selective support: essays from staffeng.com, lethain.com, kalzumeus.com, randsinrepose.com, and martinfowler.com used as working examples of engineering voice.
This guide is the primary teacher. This is the capstone of the capstone: it is where the whole degree is packaged, a direction is chosen, and the work is defended.
Scope of This Module
This module is not a résumé workshop. It is the integrative step that turns ten semesters of work into (a) a case study other engineers can read in fifteen minutes and respect, (b) a portfolio that holds up when someone goes digging, (c) a picked next direction with a plan, and (d) a defense you can deliver out loud without a slide deck.
What it covers in depth:
- structure of a strong capstone case study and what to cut from it
- portfolio-as-artifact: GitHub organization, per-project one-pagers, evidence of craft
- written engineering voice: bio, blog, editing for clarity
- a concrete rubric for choosing a specialization and a 12-month learning plan
- the final Feynman challenge and a mock interview-style defense
- an honest inventory of what you did not learn yet, and how to close it
What it deliberately does not try to finish here:
- interview grind logistics (LeetCode pacing, company-specific loops)
- recruiter-facing resume formatting
- salary negotiation mechanics
- long-term career strategy beyond the 12-month horizon
Before You Start
Answer these closed-book before starting the main path:
- In two sentences, what is your capstone and why does it matter?
- Which three commits, PRs, ADRs, or incident writeups most honestly demonstrate your engineering judgment?
- If a senior engineer spent only five minutes on your GitHub, what would they conclude about you?
- Which track (backend, distributed, platform, infra, data, security) have you pulled toward most consistently across Semesters 4-9?
- Name one topic you can no longer bluff through -- and one you still can.
Diagnostic Interpretation
4-5 honest answers
- Proceed directly. Your main job this module is packaging, not discovery.
2-3 honest answers
- Proceed, but expect Cluster 4 (Specialization Decision) to take longer than planned.
0-1 honest answers
- Spend a day rereading your own journal entries from Semesters 6-9 and your S10 M01-M04 artifacts before starting the concept path.
What This Module Is For
The capstone proved you could build a system. This module proves you can represent yourself as an engineer:
- tell the story of a real project cleanly, with tradeoffs visible
- publish evidence of craft that stands up to scrutiny
- write about your own work in a voice that is neither humble-bragging nor inflated
- choose a direction honestly instead of drifting
- sit across from a sharp senior engineer and defend what you shipped
This is where the portfolio, specialization decision, and final defense become graduation artifacts.
Concept Map
How To Use This Module
Work in order. Clusters 4 and 5 depend on 1-3 being done honestly.
Cluster 1: The Capstone Case Study
| Order | Concept | Type | Focus |
|---|---|---|---|
| 1 | Structure of a Strong Capstone Write-Up | PRIMARY | Problem, approach, outcome, tradeoffs -- with section lengths |
| 2 | What To Show, What To Cut | PRIMARY | Tailoring depth to audience without lying by omission |
| 3 | Diagrams and Screenshots That Carry Weight | PRIMARY | Visuals that replace paragraphs instead of decorating them |
Cluster mastery check: Can you write a 5-page case study that a senior engineer finishes without skimming?
Cluster 2: Engineering Portfolio
| Order | Concept | Type | Focus |
|---|---|---|---|
| 4 | Portfolio-as-Artifact: GitHub Organization | PRIMARY | Readme-driven profile, pinned repos, signal density |
| 5 | Per-Project One-Pagers | PRIMARY | Consistent, scannable, honest project summaries |
| 6 | Evidence of Craft: Tests, CI, Docs, Commits | PRIMARY | What a reviewer sees when they look past the README |
Cluster mastery check: Can a stranger land on your GitHub and in five minutes correctly describe what you are good at?
Cluster 3: Written Engineering Voice
| Order | Concept | Type | Focus |
|---|---|---|---|
| 7 | The Technical Bio and About-Me | PRIMARY | A short bio that reads like an engineer, not a brochure |
| 8 | Blog-as-Thinking: One Post Per Quarter | SUPPORTING | Publishing cadence as a learning tool, not a brand |
| 9 | Editing for Clarity: Before and After | PRIMARY | Cutting 40% of a paragraph without losing content |
Cluster mastery check: Can you produce a one-page bio and a 900-word technical post you would let a senior engineer read?
Cluster 4: Specialization Decision
| Order | Concept | Type | Focus |
|---|---|---|---|
| 10 | Mapping Curriculum Strengths Across Tracks | PRIMARY | Honest strength audit across the degree arc |
| 11 | Specialization Options | PRIMARY | Backend, distributed, platform, infra, data, security -- what each actually is |
| 12 | Choosing the Next 12-Month Focus | PRIMARY | Rubric (strength × interest × market) and a plan that survives contact |
Cluster mastery check: Can you defend your chosen specialization in 90 seconds against someone who prefers a different one?
Cluster 5: Defending the Degree
| Order | Concept | Type | Focus |
|---|---|---|---|
| 13 | The Final Feynman Challenge: 5 Topics | PRIMARY | Deep plain-language explanation of five chosen topics |
| 14 | Interview-Style Defense | PRIMARY | System design, behavioral, and retrospective under pressure |
| 15 | What You Didn't Learn (Yet) | SUPPORTING | The honest gap list and how to close it after graduation |
Cluster mastery check: Can you deliver the 10-minute defense from memory, take three curveball questions, and still name three real gaps?
Then work these practice pages:
| Order | Practice path | Focus |
|---|---|---|
| 1 | Case Study Writing Lab | Write the full capstone case study |
| 2 | Portfolio Packaging Workshop | Organize the GitHub org / portfolio site |
| 3 | Specialization Decision Clinic | Complete the rubric and the 12-month plan |
| 4 | Defense Katas | Mock panel, Feynman, curveballs, retrospective |
Use Module Quiz after the concept and practice path. Use Reference and Selective Reading and Learning Resources only for targeted reinforcement.
Learning Objectives
By the end of this module you should be able to:
- Write a 5-page capstone case study with problem, approach, outcome, and tradeoffs visible.
- Organize a GitHub profile and set of pinned repos that communicate a coherent engineering identity.
- Produce per-project one-pagers that are consistent, scannable, and honest about scope.
- Write a short technical bio and one 900-word post that demonstrate engineering voice.
- Edit a paragraph of your own prose down by 40% without losing information.
- Map your degree-wide strengths to six common specialization tracks and justify a pick.
- Produce a 12-month learning plan with concrete artifacts, reviewers, and checkpoints.
- Deliver a 10-minute capstone defense from memory to a mock panel.
- Explain five chosen degree topics in plain language at Feynman depth.
- Name three to five real gaps in your own preparation and how you will close them.
Outputs
- one 5-page capstone case study (problem, approach, outcome, tradeoffs), with diagrams and no placeholder prose
- one organized GitHub profile, README, and set of 3-5 pinned repos
- one per-project one-pager template instantiated for every shipped capstone subsystem
- one technical bio (≤ 200 words) and one 900-1,200 word technical post
- one edited-paragraph pair (before / after) in your portfolio repo as a writing artifact
- one specialization rubric (strength × interest × market) with a filled example and the final pick
- one 12-month learning plan with quarterly objectives, 6-12 artifacts, and review cadence
- one 10-minute recorded defense with transcript
- one Feynman packet covering five topics spanning Semesters 2, 4/5, 6, 7/8, 9
- one "what I didn't learn (yet)" gap list with 3-5 entries and a closing plan
Completion Standard
You have completed Module 5 when all of these are true:
- a stranger reading the case study can state your problem, approach, outcome, and one tradeoff in their own words
- your GitHub profile, pinned repos, and READMEs form a single coherent identity
- your bio and post sound like the same engineer
- your specialization pick is defended in writing and out loud, not merely declared
- your Feynman packet survives peer review on five different topic areas
- your gap list is written in the voice of someone who finishes things, not someone hiding
If the portfolio "looks done" but you cannot defend any single piece verbally, the module is not complete.
Reading Policy
- Concept pages are the main path.
- External essays are examples of voice and structure, not a second syllabus.
See also (integrative)on each concept points to 1-2 prior modules and 1 external URL -- open only when stuck.- No new required books. Use Staff Engineer and The Pragmatic Programmer as reference only.
Suggested Weekly Flow (Week 95-96)
| Day | Work |
|---|---|
| 1 | Cluster 1 concepts + case study skeleton |
| 2 | Cluster 2 concepts + GitHub organization pass |
| 3 | Cluster 3 concepts + bio draft + post outline |
| 4 | Cluster 4 concepts + rubric fill + 12-month plan |
| 5 | Cluster 5 concepts + Feynman prep |
| 6 | Practice 1-2 + edit pass on case study and post |
| 7 | Practice 3-4, quiz, recorded defense, gap list |
Cross-Semester Context
This module is a mirror held up to the full degree. Specifically:
- Cluster 1 and 3 build on S8 M05 Technical Leadership & Strategy -- written-first culture, communication under pressure.
- Cluster 2's "evidence of craft" lens builds on S7 M05 ADRs & Reviews -- the artifacts that prove engineering judgment are the same ones reviewers read.
- Cluster 4 looks back across Semesters 2 (algorithms and data structures), 4/5 (systems and databases), 6 (distributed systems), 7/8 (architecture and leadership), and 9 (production operations) to pick a direction.
- Cluster 5's Feynman challenge explicitly samples from that same span.
If the reflection in this module is honest, graduation is already defensible.
Reference
If you need exact links to external essays and verified sources, use Reference and Selective Reading.
Rich Learning Pages
Worked Examples | Guided Labs | Case Studies | Mistake Clinic | Reading Guide | Capstone Thread
Model Artifact Calibration
For final assessment packaging, compare your evidence bundle to the capstone defense packet model artifact.