Portfolio Walkthrough

• Pick the projects that best support the interview's focus
• Structure a walkthrough that owns its limitations
• Practice defending method choices without being defensive

• It is the only stage where you control the material — use that.
• Owned limitations build more trust than a polished claim.
• Walkthroughs are rehearsable to near perfection.

You choose the dishes, you plate them, and you are judged on the tasting — not on every ingredient in the pantry.

• Select one decision-centric project and one depth project.
• Rehearse the arc: question, evidence, method, limitation, decision.
• Preprepare answers to the five most likely probes about method and data.
• Timebox to the slot and cut any slide that does not serve the story.

• A growth role gets a churn-model walkthrough with precision-at-top-slice defended.
• A BI role leads with a dashboard project showing metric definitions and trade-offs.
• A senior role walks a decision that changed and admits the assumption that broke.

• Open with the recommendation; the project earns it by the last slide.
• Name the limitations and their impact before being asked.
• Keep code links in the appendix; the talk is about judgment, not LOC.

• Walking through code instead of decisions.
• Defending choices with 'it felt right' when reviewers want 'because XY'.
• Reading equals the deck; you should know it well enough to talk over one chart.

• If reviewers keep probing the same weak spot, fix it in the narrative before the interview.
• If your timebox overruns, cut the middle slide, never the recommendation.