Interview Drills — CS Knowledge

Open-ended interview questions. Each has a Framework (the structure a strong answer follows), a Model answer (a concise example), and a Rubric (what an interviewer listens for). These are the "knowledge-round" questions that test whether you actually speak the language of Customer Success. Answer crisply: define the term in one sentence, then add why it matters to the business. The app can role-play these as mock interviews (see mock-interview.md).

The universal CS-knowledge structure: Define the term in one plain sentence → say why it matters to a subscription business → connect it to what a CSM does about it → name the metric it touches. Short, confident, and specific beats long and vague.

D1

difficulty: easy
concept: churn-renewals-expansion What is churn, and why does it matter so much in a subscription business?
Framework: Define churn in one sentence → explain why it's the central threat in SaaS (recurring revenue leaks every period) → add the key insight that churn is usually preventable and signaled in advance → tie it to the CSM's job.
Model answer: "Churn is when a customer leaves — they cancel or don't renew. It matters because in a subscription model that lost revenue leaks out every month and has to be replaced just to stay flat, and replacing a customer costs far more than keeping one. The important part is that churn is usually preventable and rarely a surprise: warning signs like declining usage or a departed champion show up first, so a proactive CSM's whole job is to spot those early and intervene before the customer decides to leave."
Rubric: Strong answers define churn cleanly, frame it as a revenue/retention problem (not just "a customer is sad"), and show the proactive insight that churn is preventable and signaled early. Weak answers give a vague definition, miss why it's economically central to SaaS, or treat it as a surprise event with no early warning.

D2

difficulty: easy
concept: csm-vs-other-roles What's the difference between a CSM, customer support, and account management?
Framework: Contrast posture (proactive vs. reactive) and focus (relationship/value vs. issue vs. commercials) → give a crisp one-line distinction for each → note the lines blur in practice and that you'd read the JD.
Model answer: "Support is reactive and transactional — a customer hits a problem, opens a ticket, support fixes that specific issue; success is the issue resolved quickly. A CSM is proactive and strategic — I own the ongoing relationship and the customer's overall success, reaching out before problems to drive value, renewals, and growth. Account management traditionally leans commercial — renewals, upsells, the contract side. The analogy I use: support is the ER you visit when something hurts; the CSM is the family doctor who knows your history and keeps you healthy. In practice these merge — many CSMs own success and renewals — so I'd always read the specific job description."
Rubric: Strong answers nail the proactive-vs-reactive distinction, give a clean one-liner for each role, and acknowledge that roles overlap by company. Weak answers conflate CSM with support ("a CSM answers tickets"), miss the strategic/relationship ownership, or present the boundaries as rigid and universal.

D3

difficulty: easy
concept: customer-lifecycle What is "time to value," and why do CSMs obsess over it?
Framework: Define TTV in one sentence → explain the risk it addresses (customers churn most before they've felt value) → connect it to onboarding and the early win → say what a CSM does to shorten it.
Model answer: "Time to value is how long it takes a new customer to get their first real benefit from the product — and shorter is always better. CSMs obsess over it because customers are most likely to quit early, before they've actually experienced the value they bought; someone who signs up, struggles to get going, and never hits a win tends to quietly churn at renewal. So a big part of onboarding is engineering a quick early win that proves the value fast, because a customer who reaches value quickly is far more likely to stay for years."
Rubric: Strong answers define TTV crisply, link it directly to early churn risk and onboarding, and frame the CSM's role as actively accelerating it toward a concrete early win. Weak answers define it vaguely ("when the product is useful"), miss the connection to churn and retention, or treat it as something that just happens rather than something the CSM drives.

D4

difficulty: medium
concept: relationships-adoption What is a QBR, and why does it matter?
Framework: Define QBR (what it is and roughly how often) → state its core purpose: make value visible → list what a good one accomplishes (review results, align on next-quarter goals, surface risks early) → connect it to renewals and to positioning the CSM as a strategic partner.
Model answer: "A QBR — Quarterly Business Review — is a periodic meeting, often every few months, where I step back with the customer to look at the big picture: are you hitting your goals, here's the value you've gotten, and here's what we recommend next. It matters most because it makes value visible. Customers are busy and forget how much a product has helped, so at renewal a customer who can't see the value will balk at the cost. A good QBR reminds them of concrete results — 'this saved your team 200 hours last quarter' — aligns on goals for next quarter, and surfaces risks early so nothing blows up at renewal. It also repositions me as a strategic partner rather than a help desk."
Rubric: Strong answers correctly expand QBR, explain it as a value-visibility and alignment ritual, give a concrete results example, and tie it to renewals and strategic positioning. Weak answers describe it as just "a status meeting" or "a check-in," miss the make-value-visible purpose, or fail to connect it to renewal risk.

D5

difficulty: medium
concept: metrics What is a customer health score, and how would you use one?
Framework: Define the health score and what it's built from (usage + signals, often red/amber/green) → explain its purpose as an early-warning radar → describe how you'd act on it, not just read it → note the limitation that data plus the human relationship is what works.
Model answer: "A customer health score is a combined indicator — often red/amber/green — built from signals like product usage, support tickets, engagement, and survey results. Its purpose is early warning: a customer whose usage is quietly declining is often heading for the exit, and the score flags that before renewal. The skill isn't computing it — tools do that — it's reading it and acting. If an account drops to amber, I'd look at why, reach out to understand what changed, and put together a plan to get them back on track. I treat it as a radar I combine with the actual relationship; the number tells me where to look, the conversation tells me what's really going on."
Rubric: Strong answers define the score and its inputs, frame it as early-warning to prevent churn, and emphasize acting on it (investigate, reach out, intervene) rather than just monitoring. Weak answers describe it as a vague satisfaction number, omit that usage is a central signal, or stop at "I'd watch it" with no intervention.

D6

difficulty: hard
concept: metrics Which metrics does a CSM influence, and which one matters most?
Framework: List the metrics a CSM moves (churn/retention rate, GRR, health scores, NPS/CSAT) → then name NRR as the single most important and define it → explain why NRR is special (includes expansion, can exceed 100%) → tie it back to the two halves of the CSM job: retention and expansion.
Model answer: "A CSM influences churn rate and its flip side retention, Gross Revenue Retention, health scores, and sentiment metrics like NPS and CSAT. But the one I'd name first is Net Revenue Retention — NRR. NRR measures how the total recurring revenue from your existing customers changes over a year, including expansion from upsells and cross-sells and minus churn and downgrades. It's special because it can exceed 100%: if expansion from happy customers outweighs churn, the company grows even without adding a single new customer — the holy grail of a healthy SaaS business. I lead with NRR because it captures both halves of my job, keeping customers and growing them, in one number, which is exactly why executives watch it most."
Rubric: Strong answers list several real CSM metrics and explicitly name NRR as the headline, define it correctly (existing customers, includes expansion, can exceed 100%), and connect it to retention + expansion. Weak answers name only churn or NPS, fail to name NRR, confuse NRR with GRR, or can't explain why exceeding 100% matters.