present

present — Presentation Round Coaching

How Presentation Rounds Actually Work (Reference Knowledge)

Format Prevalence: Presentation rounds appear across seniority levels and functions:

• Senior+ engineering: system design presentations, architecture reviews, tech deep dives
• Product management: product sense, business case, strategy presentations
• Design: portfolio reviews, design critiques
• Data science: analysis presentations, methodology reviews
• Executive roles: strategic vision, 90-day plans, board-style presentations
• Consulting: case presentations
• Pre-sales/solutions engineering: technical demos, solution presentations

What Evaluators Actually Assess (from interview design literature and hiring manager perspectives):

1. Communication clarity — Can they explain complex ideas simply? Do they calibrate to the audience?
2. Structured thinking — Does the presentation have a logical arc? Can you follow the reasoning?
3. Audience calibration — Did they pitch at the right level? A technical deep dive for executives fails. An executive summary for engineers fails.
4. Time management — Did they stay within bounds? Going over time is the #1 presentation-round failure mode.
5. Depth vs. breadth judgment — Do they know when to go deep and when to stay high-level?
6. Q&A handling — Can they think on their feet? Do they admit what they don't know? Do they redirect constructively?
7. Confidence and poise — Not arrogance, but comfort with the material and the format. Matt Abrahams (Stanford, via Lenny's Podcast) distinguishes between "performance confidence" (acting confident) and "process confidence" (trusting your preparation). Candidates who try to perform confidence often appear rehearsed. Candidates who trust their process appear natural. The warmup routine should build process confidence — comfort with the structure, flow, and key transitions — not a polished performance.

Narrative Arc Frameworks:

• Situation-Complication-Resolution (SCR) — Most versatile. Present the context, introduce the tension, deliver the resolution. Works for most technical and business presentations.
• Problem-Approach-Results-Learnings (PARL) — Best for technical/analytical presentations. Shows methodology and rigor. Common in data science and engineering deep dives.
• Context-Challenge-Options-Recommendation (CCOR) — Best for business case and strategy presentations. Shows decision-making process. Common in PM and executive rounds.
• Hook-Build-Deliver-Land (HBDL) — Best for executive audiences. Start with the punchline, build the evidence, close with the ask. Executives decide in the first 30 seconds whether to pay attention.
• What Is / What Could Be / New Bliss (Duarte) — Nancy Duarte's framework (CEO of Duarte Inc., 250,000+ presentations crafted, via Lenny's Podcast): Alternate between current reality ("What Is") and future possibility ("What Could Be") to build tension and longing, then end on the transformed future state ("New Bliss"). Found in MLK's "I Have a Dream," Steve Jobs's iPhone launch, and hundreds of great talks. Works at any scale from a 2-minute pitch to a 60-minute keynote. The key principle: the audience is the hero, not you — as Duarte puts it: "Your audience gets to make a choice if they accept or reject your idea. So, the balance of power is with them and not you." Position yourself as the mentor who brings tools and resolve, not the hero proving how great you are.
• Strategic Narrative (Raskin) — Andy Raskin's 5-part framework (strategic narrative consultant, "The Greatest Sales Deck I've Ever Seen" with 2M+ views, via Lenny's Podcast): (1) Name the shift — what's changed in the world (Old Game → New Game), (2) Name the stakes — who wins and who loses, (3) Name the object of the new game — the rallying cry, (4) Show the obstacles — what makes this hard, (5) Show how you overcome obstacles — your "magic gifts." This replaces the "arrogant doctor" anti-pattern (problem → my solution → why mine is better). For presentation rounds: don't do a feature walkthrough of your case study. Structure it as: here's the shift, here's who's winning, here's the goal, here's what's hard, here's how I/we overcame it. As Raskin puts it: "We didn't change the product — it was basically the same business, just how we talked about it."