Phase 11: Capstone: The AI-Native Product Engineer · 60 min · Claude Code · Python

Project: Full Platform & Career Portfolio

Four disconnected documents in a folder is a paper trail. One coherent narrative connecting the platform, the case study, the mock interview, and the roadmap is the artifact you actually bring to a job search.

Hiring signal: A candidate who arrives with one integrated package — a verifiable platform, a case study proving the engineering discipline behind it, and a roadmap targeting the right company archetype — is exactly the AI-native product engineer this course was built to produce.

What you will learn

Assemble the four capstone deliverables (platform, case study, mock interview, career roadmap) as one coherent package rather than disconnected documents
Cross-reference each deliverable so a reader can navigate from any one of them to the others
Build a career roadmap that targets a specific company archetype (from c12-10-1) with concrete, timed next actions
Verify the complete capstone package is production-honest: every claim in it maps to a real, checkable artifact

Introduction

Project: Full Platform & Career Portfolio

A learner finishes the course with four solid pieces sitting in four separate places: a production platform with good documentation, a portfolio case study written for c12-10-2, a mock interview presentation practiced for c12-10-3 and c12-10-4, and a career roadmap listing target companies. Each piece is individually strong. Submitted as four disconnected files, a hiring manager opens the case study, has to go hunting for the actual repository it references, can't easily tell if the mock interview answers correspond to the real system or a hypothetical one, and gives up halfway through reassembling the pieces themselves. The engineering was real. The presentation of it wasn't, and that gap is exactly what this final project closes.

The four deliverables, and why each one is required

This project isn't new work — it's the assembly of everything the last eleven phases and two prior capstone lessons already produced, into the actual thing you'll hand to a hiring manager: the production platform with full documentation (the multi-agent system from Orbit 3, with the architecture document from c12-11-1 and the remediated gaps from c12-11-2), a portfolio case study covering the complete spec-to-platform arc (per c12-10-2's three-artifact structure: the system, the context architecture, and a real incident postmortem), a mock interview presentation demonstrating the system-design and live-coding discipline from c12-10-3 and c12-10-4 applied to this specific product, and a career roadmap targeting a specific company archetype using c12-10-1's framework. None of these are optional extras — a platform with no case study is unverifiable to a reader who won't dig through source code themselves, and a case study with no platform behind it is just prose.

The package is one artifact with four parts, not four artifacts
Every deliverable in this project should point at the others: the case study should link to the actual platform repository and reference the specific incident it discusses, the mock interview should answer questions about the real system the case study describes, and the roadmap should target company archetypes the platform itself demonstrates readiness for. A reader should be able to start at any one piece and navigate to the rest without hunting.

A learner submits their capstone as four separate files: a platform repo link, a case study PDF, a mock interview transcript, and a roadmap document — none of which reference each other. A hiring manager opens the case study, can't find the repo it's describing, and gives up reassembling the pieces. What does this lesson say went wrong?

Individually strong artifacts still fail if a reader can't connect them — the entire point of assembling these four pieces into 'one artifact with four parts' is that each piece should reference the others, letting a reader navigate the full picture starting from whichever piece they happened to open first, rather than requiring them to reconstruct the connections themselves.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers The career roadmap: targeting, not just listing, What "full documentation" means for the platform piece, Closing the loop back to where this course started, Build It — plus a hands-on lab, quiz, and project artifact.

Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.