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

Capstone Presentation: The Demo Day

A demo that only shows the working product proves you can build something. A demo that also shows the spec, the harness, the gates, and a real incident proves you engineer with discipline — and only one of those gets remembered after the room empties.

Hiring signal: Structuring a demo around the full engineering discipline behind a product — not just the feature working — is the single most direct way to make an audience believe the discipline this course teaches is real, not claimed.

What you will learn

Structure a demo day presentation around a user journey/story rather than a feature list
Show the spec, harness, quality gates, and observability behind the product, not just the working feature
Present a real incident and its resolution as part of the demo, not omit it to look flawless
Close a demo with a recap, explicit confirmation of what was shown, and a concrete next step

Introduction

Capstone Presentation: The Demo Day

Two learners present the same kind of capstone product on demo day. The first walks through the feature: "here's the refund flow, you type a request, the agent processes it, and it works." Ninety seconds, a working feature, polite applause. The second walks through a user journey — a customer disputing a charge — and as she narrates it, she pulls up the spec that defines what a correct refund decision looks like, the harness config that limits what the agent can do unsupervised, the CI check that blocked a bad merge last week, and a real incident from her observability dashboard where the agent almost issued a refund it shouldn't have, and how she fixed the underlying gap rather than just the one case. The room remembers the second demo, not because the feature was more impressive, but because it proved an entire discipline was real, not because it worked once in front of an audience.

Structuring the demo as a story, not a feature list

A demo built around a feature list ("first this button, then this screen, then this output") reads as a tour, not a story — the audience has nothing to follow beyond "does the thing work." A demo built around a real user journey (a customer with a specific problem, moving through the system to a resolution) gives the audience something to track, and naturally creates the moments where showing the spec, the harness, or an incident actually makes sense in context, rather than feeling like a bolted-on technical appendix. Presenting to a technical audience specifically means matching depth to what they'll actually probe — evaluators care about integration and security details, decision-makers care about risk and scope, so knowing who's in the room shapes how deep to go on each part of the story.

Showing the discipline is what separates a demo from a proof
Anyone can demo a feature that works once, live, in a controlled setting — that's the easy part. Showing the spec that defines correctness, the harness that constrains bad behavior, and a real incident that was actually caught and fixed is what turns a demo into evidence that the discipline behind the product is real, not just the feature itself.

Learner A's demo shows only the working refund feature end to end. Learner B's demo follows a customer's dispute journey and, along the way, shows the spec defining a correct decision, the harness limiting agent actions, and a real incident that was caught and fixed. Why does Learner B's demo leave a stronger impression, per this lesson?

The functional feature working is table stakes — both demos presumably show that. What distinguishes Learner B's demo is that it demonstrates the engineering discipline behind the feature (the spec, the harness, a real incident handled well) as verifiable evidence, rather than asking the audience to simply trust that the discipline exists because the feature ran successfully once.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers Including a real incident, not hiding it to look flawless, Rehearsing enough that a live demo is actually safe to run, Closing with a recap, confirmation, and a concrete next step, 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.