Interview Drills — Scenario Role-Play

Open-ended live-judgment scenarios from the practical round of CSM interviews. The interviewer plays a customer (or hands you a situation) and watches how you think and respond in the moment. Each drill 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, stay calm, and always tie back to the customer's goal and a clear next step. The app can role-play these as mock interviews (see mock-interview.md).

The two structures that carry most CSM scenarios. For an upset customer or threat: listen fully → acknowledge/empathize → take ownership → solve or set a clear next step → follow up. For onboarding or a fresh account: start from their goal → make a plan → drive to a quick early win → enable the people → confirm value (don't declare victory at "set up"). Reach for whichever fits, narrate which you're using, and resist jumping straight to a solution before you understand the real problem.

D1

difficulty: hard
concept: tough-conversations A key customer just emailed that they're cancelling because of the price increase. They're on the phone now — walk me through how you handle the call.
Framework: Listen fully and let them vent → acknowledge the frustration without getting defensive (validating isn't admitting fault) → take ownership as their point of contact → probe for the real reason (price is often a proxy for "I'm not seeing the value") → reframe around value delivered (lean on QBR results) → offer a concrete path (options, a value recap, escalation if needed) → set a clear next step and follow up. Save the account if you can, but stay calm and respectful even if you can't.
Model answer: "First I'd let them get it all out and say, 'I hear you — a 15% jump with no heads-up is frustrating, and I want to make this right.' Then I'd dig in: 'Help me understand — is it purely the number, or has the value not felt worth it lately?' Usually it's the latter. I'd remind them of the concrete results we drove — 'last quarter the platform saved your team about 200 hours and cut your response time in half' — so the price sits next to the value, not alone. I'd own the next step: 'Let me pull your usage and ROI, talk to my manager about options for a loyal account, and come back to you Thursday with something concrete.' Then I'd actually follow up Thursday. If they still leave, I'd make sure they leave respected — they often come back."
Rubric: Strong answers stay calm, listen before solving, separate the stated reason (price) from the real one (value), re-anchor on demonstrated value, take personal ownership, and commit to a specific follow-up — and accept that not every save works. Weak answers get defensive, immediately offer a discount with no diagnosis, argue about the price, pass the customer to billing, or promise a save they can't keep.

D2

difficulty: medium
concept: onboarding We just closed a new mid-market customer. Walk me through how you'd onboard them.
Framework: Start with a clean handoff from sales (why did they buy, what was promised) → open by confirming their goals and what success looks like for them → co-build a written onboarding plan with steps, timeline, and owners → drive toward one quick early win, not a full feature tour → train and enable the actual people who'll use it → set expectations for support and what's next → confirm real value before calling it done.
Model answer: "I'd start by reading the sales handoff so they never repeat themselves, then kick off by confirming the goal: 'Sales tells me you bought this to cut onboarding time for your own customers — is that still the top outcome?' I'd co-create a 30-day plan with milestones, owners, and dates. Instead of touring every feature, I'd aim for one early win in week one — get their first workflow live and producing a visible result — because that early success hooks the team. I'd train their admins and end users, not just the buyer, since adoption is a people problem. I'd set expectations on support and check-ins. I would not call it done at 'they can log in' — done is 'their team is getting value and using it confidently,' so I'd confirm that against the original goal before we transition to the ongoing cadence."
Rubric: Strong answers anchor on the customer's specific goal (not a generic tour), lay out a structured plan with owners and dates, prioritize a quick early win, train the people (not just the buyer), and define success as value achieved rather than "set up." Weak answers jump to a feature walkthrough, ignore the sales handoff, overwhelm the customer with everything at once, or declare victory at login.

D3

difficulty: hard
concept: health-scores Usage just dropped sharply on one of your top accounts this month. The health score went amber. What do you do?
Framework: Treat it as an early-warning signal, not a crisis to panic over → investigate before reaching out (which teams/features dropped, did a champion leave, any open tickets, did their business change) → form a hypothesis → reach out proactively and curiously, framed around their goals, not "you're not using us enough" → diagnose the real blocker → act (re-train, remove friction, re-engage a new champion, escalate a product issue) → set a follow-up and watch the metric recover.
Model answer: "A usage drop is the radar doing its job — better to catch it now than at renewal. Before calling, I'd look at the data: which features and teams fell off, did our main champion's logins go to zero (often means they left or got reorganized), and are there open support tickets behind it. Say logins from their power-user team flatlined — my hypothesis is a champion departure. I'd reach out warmly and goal-first: 'I noticed your team's activity shifted and I want to make sure you're still getting what you came here for — has anything changed on your side?' Then I'd diagnose: new owner who needs training, a workflow that broke, priorities moved. I'd act accordingly — re-onboard the new champion, fix the friction, or escalate a real product issue with clear context — and I'd set a check-in two weeks out to confirm usage climbs back. The point is to intervene before it becomes a renewal problem."
Rubric: Strong answers read the signal as proactive early warning, investigate the data and the cause before reaching out, frame outreach around the customer's goals (not usage for its own sake), find the real blocker (a departed champion is the classic one), take concrete action, and follow up to confirm recovery. Weak answers ignore it until renewal, fire off a generic "use us more" email, panic, skip the diagnosis, or never close the loop.

D4

difficulty: medium
concept: renewals A renewal is six weeks out and you're not sure where the customer stands. Role-play how you approach it.
Framework: Don't wait for the deadline — start early → assess the account honestly (health, usage, relationship, any open issues) → reinforce value with concrete results from your QBRs → surface and resolve concerns before they become reasons to leave → make the renewal itself frictionless → if there's risk, address it head-on rather than hoping. A renewal should feel like a natural continuation, not a tense negotiation.
Model answer: "Six weeks is enough runway if I move now. First I'd take an honest read: usage is healthy, but our champion's been quiet and there's one unresolved bug. I'd book a value check-in, not a 'please renew' call — recap the results we drove this year against their original goal, so the value is front of mind. I'd directly surface the bug: 'I know that issue's been nagging — here's the fix and the timeline,' so it can't quietly become a reason to churn. I'd re-engage the quiet champion or build a relationship with whoever's now driving it. Then I'd make the paperwork dead simple. If I sensed real risk, I'd name it early and bring in help rather than crossing my fingers. Done right, the renewal is just a formality because the value's already obvious."
Rubric: Strong answers start early, diagnose the account honestly, reinforce value with concrete results, proactively surface and resolve concerns, reduce friction, and treat the renewal as the payoff of year-round work. Weak answers wait until the deadline, treat renewal as a one-off sales push, ignore warning signs, or rely on a last-minute discount instead of demonstrated value.

D5

difficulty: medium
concept: expansion One of your accounts is thriving on the entry plan and clearly outgrowing it. Role-play how you'd raise expanding their contract.
Framework: Earn the right first — expansion is value-led, not pushy → ground it in evidence that they're succeeding and hitting limits → tie the upgrade to their outcome, not your quota → recommend it as a trusted advisor ("given your goal, here's what would help you achieve more") → make it low-pressure and easy to say yes to → connect it to the bigger picture (this is how a healthy account grows, the NRR story). The customer should feel advised, not sold.
Model answer: "I'd only raise it because the data says it genuinely helps them. In our QBR I'd point to it naturally: 'You've hit the seat limit twice this month and your team's clearly relying on the workflows — at this rate the entry plan is capping the results you came here for.' Then I'd frame the upgrade as the path to their goal, not a sale: 'The next tier removes that ceiling and adds the reporting your VP keeps asking for — I think it'd pay for itself in the time it saves.' I'd keep it pressure-free: 'No rush — want me to put together what that would look like for your team?' Because I've earned their trust by helping them succeed, this lands as good advice rather than a pitch. That's exactly the expansion that drives net revenue retention above 100%."
Rubric: Strong answers make expansion value-led and evidence-based, tie it to the customer's own outcomes, position the CSM as a trusted advisor, keep it low-pressure, and show awareness of why expansion matters (NRR). Weak answers are pushy or quota-driven, pitch an upgrade without proof the customer needs it, ignore the relationship, or treat the customer as a transaction.

D6

difficulty: hard
concept: escalations A serious outage is hurting your biggest customer right now, and they're furious. The fix is owned by engineering, not you. Role-play the next hour.
Framework: Stay calm and don't take it personally — your composure is contagious → acknowledge the real impact honestly → take ownership as their single point of contact even though you can't fix it yourself → escalate well: bring in engineering/your manager with clear information (what's broken, the impact, what's been tried, what you need) → keep the customer continuously informed so they never feel abandoned → solve or commit to a clear next step and timeline → follow up after resolution to rebuild trust. A crisis handled well can deepen loyalty.
Model answer: "I'd stay steady — they're upset at the situation, not me, and my calm sets the tone. I'd acknowledge it plainly: 'This is hurting your operations and that's not okay — I'm on it and I'm your point of contact until it's resolved.' I would not hand them to a queue and vanish. Behind the scenes I'd escalate with a tight brief to engineering and my manager — what's down, who's impacted, business cost, what I need and by when — so they can move fast. Then I'd keep the customer updated on a rhythm, even with 'no news yet, still on it,' because silence feels like abandonment. Once it's fixed I'd confirm they're whole, explain what happened and how we'll prevent it, and follow up in a few days. Customers don't expect perfection; they remember how you showed up when it broke — handled right, this can actually deepen the relationship."
Rubric: Strong answers stay calm and own the relationship without owning the fix, escalate at the right time with crisp information, keep the customer continuously informed as their coordinator, close with a clear resolution and a follow-up, and understand that a well-handled crisis builds loyalty. Weak answers get defensive, dump the customer on another team and disappear, escalate vaguely or too late, go silent during the outage, or skip the follow-up that turns a recovery into trust.