Interview Drills — Mock Discovery & Role-Play

Open-ended interview questions and live role-plays. Each has a Framework (the structure a strong answer follows), a Model answer (a concise example), and a Rubric (what an interviewer listens for). Practice thinking aloud and, in role-plays, talking less than you ask — your job is to surface and quantify a real problem before pitching. The app can role-play these as mock interviews, playing the buyer (see mock-interview.md).

The universal discovery structure: Open-ended questions → listen and dig (current process → what's painful → cost of inaction → what good looks like) → qualify with BANT (Budget, Authority, Need, Timing) → connect their specific need to an outcome → handle objections by finding the real concern → confidently ask for the next step. Use it on almost any "sell me this" or "run a discovery call" prompt.

D1

difficulty: easy
concept: discovery-and-qualification "Sell me this pen." Walk me through how you'd handle it.
Framework: Resist pitching → ask open-ended questions to find a real need (how/when do they write, what's painful about their current pen) → listen → quantify the pain → connect the pen to their outcome → ask for the close. Name out loud that discovery comes before pitch.
Model answer: "First I wouldn't pitch — I'd ask: 'When do you write by hand, and what matters in those moments?' Say they sign contracts in front of clients. Now I know the need: looking polished and never having a pen skip mid-signature. Then I sell to that: 'This pen writes cleanly every time and looks the part when a client is watching you sign — want to start carrying it?' The point of the exercise is that I qualified the need before I pitched a single feature."
Rubric: Strong answers explicitly ask questions before pitching, uncover a specific use and pain, then tie the product to that outcome and ask for the sale. Weak answers immediately rattle off features ("it writes smoothly, it's blue") with no question, no need, and no close.

D2

difficulty: easy
concept: discovery-and-qualification What does a good discovery call look like to you, and roughly how much should you talk?
Framework: State the goal of discovery (understand before pitching) → talk far less than you listen → use open-ended questions → say what you're listening for (current process, pain, cost, desired outcome) → explain why listening builds trust and uncovers the real pain that drives a purchase.
Model answer: "The goal is to understand their world before I pitch anything, so the rep should be listening far more than talking — maybe 30% me, 70% them. I'd open with broad questions: 'Walk me through your current process for X. What's frustrating about it? What happens if it isn't fixed?' Listening does two things: it tells me exactly which problem to connect the product to, and people trust someone who's curious about their problem instead of pushing a pitch."
Rubric: Strong answers put the listen/talk ratio firmly on the customer's side, give concrete open-ended questions, and explain why (trust + uncovering real pain). Weak answers treat discovery as a quick formality before a feature pitch or describe the rep doing most of the talking.

D3

difficulty: medium
concept: discovery-and-qualification Role-play: you're selling a project-management SaaS to an ops manager at a 200-person company. Run the first five minutes of discovery.
Framework: Open with a broad question → follow the chain (current process → what's painful → cost/impact → what success looks like) → weave in BANT naturally (who else is involved, is there budget, how urgent) without interrogating → summarize the pain back to confirm you heard it.
Model answer: "'Thanks for the time — before I show anything, walk me through how your team plans and tracks work today.' (listen) 'Where does that break down?' She says status updates eat hours and things slip. 'When something slips, what's the impact — missed deadlines, unhappy clients?' (quantify) 'If this were solved, what would good look like?' Then naturally: 'Who else would weigh in on a tool like this?' (Authority) and 'Is fixing this a this-quarter priority?' (Timing). I'd close the segment by reflecting it back: 'So status updates cost ~5 hours a week and slipped deadlines are hurting client trust — did I get that right?'"
Rubric: Strong answers stay in open-ended questions, follow the pain chain, fold BANT in conversationally, and confirm by summarizing. Weak answers jump to demoing the product, fire a checklist of BANT questions like an interrogation, or never quantify or confirm the pain.

D4

difficulty: medium
concept: discovery-and-qualification A prospect says, "This sounds interesting, but it's too expensive." How do you respond?
Framework: Don't get defensive or discount reflexively → acknowledge/empathize → diagnose the real concern ("too expensive" usually = value not yet clear) → reconnect to the pain you quantified and reframe value vs. price (ROI) → confirm you've resolved it → move toward the next step.
Model answer: "'That's a fair concern — let me make sure the value is clear.' Then I diagnose: usually 'too expensive' means the ROI isn't obvious yet. 'Earlier you said manual reporting costs your team about 10 hours a week — at your loaded cost that's roughly $X a month. Our tool removes most of that, so it pays for itself in under two months.' Then I confirm: 'Does the value line up against the cost now?' I'd only talk price terms once value is agreed — I defend the value before I ever discount."
Rubric: Strong answers reframe price as a value/ROI question, tie back to a quantified pain, acknowledge without arguing, and confirm resolution before closing. Weak answers immediately offer a discount, get defensive, or argue the price instead of uncovering the real concern.

D5

difficulty: medium
concept: discovery-and-qualification How do you qualify a deal with BANT during a discovery call without it feeling like an interrogation?
Framework: Define BANT (Budget, Authority, Need, Timing) → explain you learn it through natural discovery questions, not a checklist → give a conversational question for each → state the payoff: qualifying out fast keeps the pipeline full of winnable deals.
Model answer: "BANT is Budget, Authority, Need, Timing — but I never read it as a checklist. I uncover Need first (it's the one that drives a sale) by digging into pain. Authority comes from 'Who else would be involved in a decision like this?' Budget from 'Have you set aside resources to fix this, or are we still scoping?' Timing from 'Is this a this-quarter priority or more of a someday?' If there's no real need, no budget, and no urgency, I qualify out early — that's not a loss, it saves both of us time and keeps my pipeline full of deals I can actually win."
Rubric: Strong answers translate each BANT letter into a natural question, lead with Need, and frame qualifying out as a win. Weak answers recite BANT as a literal script, treat every lead as worth chasing, or never mention qualifying out.

D6

difficulty: hard
concept: demos-objections-closing Role-play the full arc: take a discovered need, handle a real objection, and close — for a security tool sold to an IT director who already uses a competitor.
Framework: Briefly restate the quantified need from discovery → tailor the value to it (outcome, not feature tour) → surface and handle the "we already use X" objection (listen → empathize → find the real gap → respond with evidence → confirm) → create honest urgency → confidently ask for the business and make yes easy.
Model answer: "'You told me you're spending ~8 hours a week chasing alerts your current tool can't prioritize, and a missed one is a real breach risk.' Tailored value: 'Ours auto-prioritizes, so your team focuses on the few that matter.' Objection — 'We already use X': 'Makes sense, switching is a real cost. What's the one thing X doesn't do that you wish it did?' He says noisy alerts. 'That's exactly the gap we close — here's a team like yours that cut alert volume 60%.' Confirm: 'Does that address the concern?' Then honest urgency + close: 'Every week unsolved is 8 hours and open risk — could we run a two-week pilot on your noisiest segment starting Monday? I'll handle setup.'"
Rubric: Strong answers tie the demo to a quantified need, treat the objection as a chance to find the real gap (not a wall), respond with evidence, use honest urgency, and confidently ask for a concrete next step. Weak answers do a generic feature tour, get defensive about the competitor, fake urgency, discount to win, or never actually ask for the business.