Mock Q packs (hotspots)

~9 min read

🎯 Interview frequent

Why it matters

Reading the spine and answering out loud are different skills. Founder interviews are short, interruptible, and allergic to a memorized script. This page is the drill: a YC-style pack and an early-VC pack, with the shape of a good answer and a pointer to the page that holds the substance. Run it with a cofounder or a friend who is willing to cut you off.

Core concepts

  • How to run it. Ten minutes for Pack A. One person asks, and they must interrupt at least three times. Record it. The only debrief that matters: which sentence broke (jargon, no user, a number you couldn’t define, an answer longer than the question deserved). Fix that sentence and run it again. Don’t add slides.
  • Pack B is thirty minutes. Two minutes of narrative, then questions. The interviewer should ask for a definition and a customer by name or context. Debrief the same way, plus: did the ask land on a milestone?
  • Answer shape, every time. Plain sentence. Past-tense fact. Ugly qualifier, said by you. Stop. The content lives in the earlier topics. If you “win” the mock by being charming and vague, the mock failed.
  • Don’t memorize paragraphs. Memorize the facts (the user, the numbers, the cut, the price, the split) and the order. Partners notice a recited answer, and an interruption destroys it.
  • Trade places. The person who only asks never hears their own hedges. Both founders should be able to answer. A YC interview can aim the next question at either of you.

Mental model

flowchart TD
  T[Timer on] --> I[they interrupt]
  I --> A[you answer the new question]
  A --> S[stop]
  S --> B["after: which sentence broke"]

Silence while you recall a true number is better than a smooth sentence you have to retract.

Interview questions

Pack A is the YC-style ten minutes. Pack B is the seed-style follow-up. Answer keys are the shape, not a script.

  1. Pack A — What do you do? Answer: Two sentences a non-expert can picture, plus one person in a scene. No category nouns. Full treatment: Product sense and Traps.

  2. Pack A — Who is the user? Tell me about the last one. Answer: Role and context, the last time the problem happened, the workaround, the cost, and what you changed. If you only have friends, say so. Full treatment: Problem clarity.

  3. Pack A — How do you make money, and what’s the number? Answer: Who pays, how much, how often. Then the real traction sentence: absolute level, dates, and the quality label (paid, pilot, LOI). Full treatment: Pricing and Traction.

  4. Pack A — Why you, and why now? Answer: One edge that is a fact, and one change that unlocked the product this year. “We care” and “AI is hot” don’t count. Full treatment: Why this / why now / why you.

  5. Pack A — What are you raising, if anything, and what do you do with it? Who else is on the team? Answer: Amount, milestone, commitment constraint (including school). Equity only if they poke a weird split. Full treatment: Fundraising and Team.

  6. Pack B — Walk the wedge, then the bigger market. What’s unproven? Answer: Bottom-up count for the first buyers, one adjacent step, and an explicit label on the step you have not sold. Full treatment: Market size & wedge.

  7. Pack B — Who do you lose to today, and why doesn’t the incumbent copy you? Answer: Status quo plus a named alternative. One user-visible axis. A structural reason or an honest head start, not a moat you don’t have. Full treatment: Competition.

  8. Pack B — Define the metric. Show a cohort. What did you spend to get them? Answer: Definition, absolutes, cohort, and “founder time” if you didn’t pay for the channel. Recompute the growth rate with the interviewer. Full treatment: Traction and Go-to-market.

  9. Pack B — Two-minute story, then: what has to be true in eighteen months for this round to have been right? Answer: Narrative order, then a milestone a stranger could check. Not a valuation. Full treatment: Fundraising.

Watch

Further reading


Back to top

Copyright © 2026. Distributed under the MIT License.

This site uses Just the Docs, a documentation theme for Jekyll.