How is a customer success manager interview different from a support interview?

Support resolves the problem in front of them; a customer success manager owns the account's outcome over months. So this kit weighs adoption planning, reading renewal risk and commercial conversations, while a support kit weighs troubleshooting, clear replies and pace. Some candidates move well between the two, and the questions show which skills they already have.

How much weight should net revenue retention carry in a CSM interview?

Some, as context. Retention depends on the product, the segment, pricing and the accounts the candidate inherited, and it is hard to verify. Ask what drove the number, and let the account walk-throughs and the renewal role-play carry the rating.

Should a customer success manager interview include a role-play?

Yes. A renewal conversation with an unhappy customer is the moment the job is hardest, and a 15-minute role-play shows more than any question about it. Give the interviewer a written brief so every candidate meets the same customer, and rate against the anchors, not polish.

Can someone from support or account management move into customer success?

Often, yes. Support people bring product depth and calm with upset customers; account managers bring commercial confidence. Use the same questions for every candidate and look for the competency that is new to them, then decide whether onboarding can close the gap.

Free interview kit

Customer Success Manager interview kit: questions and rubric

For hiring teams interviewing a customer success manager who owns a book of business-to-business accounts after the sale, roughly two to seven years in. It covers a short screen, five competencies with behavioral questions, a renewal role-play and an account-triage work sample, anchored ratings, the questions never to ask, and a rule for deciding.

5 competencies · 10 questions · anchored 1-to-5 scale · Updated 10 October 2026 · Written by the Itya team

Share this kitLinkedIn X WhatsApp Email

How to use this kit

Agree the competencies with the hiring manager before the job is posted.
Give each interviewer one or two competencies, so nothing is asked twice.
Ask every candidate the same core questions; follow up freely.
Rate each competency against the anchors straight after the interview, alone.
Debrief on quotes, not adjectives, then decide with the rule at the end.

First-round screen

Fifteen to twenty minutes, by phone, video or a disclosed AI screen. The aim is to confirm the basics before the panel spends its time.

What draws you to customer success, and to working with this kind of customer after the sale?
Tell me about the accounts you manage today: how many, their typical size, what you are measured on, and how your week splits between onboarding, renewals and everything else.
The job description says whether this role owns the renewal and expansion number or supports an account manager who does. Which of those have you done before, and how did it work?
The job description sets out the location, working pattern, customer time zones and start date. Do those work for you, what is your notice period, and what compensation range are you expecting?

Competency 1

Onboarding and adoption

Customers who reach a real result early tend to renew; customers who never adopt the product leave quietly. A customer success manager turns a signed contract into a working habit.

Tell me about an onboarding you ran for a customer that was slow to get started. What did you do to get them to their first real result?
Follow up with
- How did you define that first result, and who on the customer side agreed to it?
- What did the customer have to do, and how did you get them to do it?
- What would you change in the onboarding plan now?
Strong answer
Agreed a specific outcome with the customer up front, not just 'go live'. Built a plan with owners and dates on both sides, found the real blocker (no internal owner, data not ready, a competing priority) and acted on it, for example by bringing the sponsor back in.
Weak answer
Lists the training sessions delivered and the checklist completed, but cannot say what the customer achieved. Waited for the customer to come back, or blames the customer for being slow.
Ninety days after go-live, the product shows that 15 of the 200 seats the customer bought are active. What do you do?
Follow up with
- What would you look at before contacting anyone?
- Who would you contact first, and what would you say?
- Who inside your own company needs to know?
Strong answer
Checks which teams and features are in use before reaching out. Asks whether the rollout stalled, the use case changed or the product does not fit. Talks to the sponsor about their goal rather than seat counts, agrees a plan to get specific teams to value, and flags the renewal risk internally.
Weak answer
Sends a mass email with training links or books another product demo. Treats it as a usage problem only, tells nobody that the renewal is now at risk, or blames the customer.

Rating	What it looks like
5 · Strong	Agrees a measurable first outcome with the customer, plans the work on both sides, spots stalled adoption early, and goes after the cause instead of sending more training.
3 · Mixed	Runs a sound onboarding plan with dates and owners, but measures success by activity such as logins, and reacts to low adoption late.
1 · Weak	Equates onboarding with training sessions delivered. Cannot say what outcome the customer bought or whether they reached it.

Competency 2

Account health and renewal risk

Churn is usually visible months before the renewal date to someone who is looking. A customer success manager who reads the signals honestly gives the company time to act and keeps the forecast real.

Tell me about an account you lost, or nearly lost. When did you first see the risk, and what did you do?
Follow up with
- Looking back, what was the earliest signal?
- What did you tell your manager, and when?
- What changed in how you watch accounts afterwards?
Strong answer
Names concrete signals: the sponsor left, usage fell in one team, tickets rose, the customer stopped coming to reviews, a budget review was announced. Raised the risk internally with a plan, not just a red flag, and owns what they missed.
Weak answer
Says the customer 'just churned' over price or budget with no warning they can name, or kept the account green on the dashboard until the renewal call.
Work sample (10 minutes): here is a one-page table of five invented accounts with contract value, renewal date, usage trend, open support tickets and the date of the last sponsor meeting. Rank them by renewal risk and tell me what you would do this week for the top two.
Follow up with
- Which signal in this table would you trust least, and why?
- What is missing that you would want to know?
Strong answer
Weighs several signals together rather than one score, notices the contradictions the table plants (high usage but a silent sponsor, an early renewal with no recent contact), names specific actions with owners, and says what data they distrust or lack.
Weak answer
Ranks by contract value or by usage alone, proposes the same action for every account, or misses the account that renews soonest.

Rating	What it looks like
5 · Strong	Reads several signals together, raises risk early with evidence and a plan, keeps the forecast honest, and changes how they monitor accounts after a loss.
3 · Mixed	Watches usage and support signals and raises risk internally, but late, or without a recovery plan.
1 · Weak	Learns of risk at the renewal call. Relies on a health score or gut feel and cannot name the signals behind it.

Competency 3

Renewal and expansion conversations

Most customer success managers carry or influence a renewal and expansion number. The skill is making each commercial conversation follow the value the customer has seen, without pushing.

Role-play (15 minutes): I am the operations director at a customer renewing in 30 days. The rollout went badly, support was slow twice, and finance has asked me to halve the contract or cancel. Run this call. (The interviewer works from a written brief: one team was never onboarded, and a smaller renewal with a recovery plan would keep the account.)
Follow up with
- What did you learn that changes your plan?
- What would you offer, and what would you need approval for?
- What would your follow-up email say?
Strong answer
Lets the customer finish, acknowledges the specific failures without excuses or blaming the support team, asks what success would have looked like, and finds the team that was never onboarded. Proposes a recovery plan with dates, discusses a right-sized renewal honestly, promises no discount or feature it cannot commit to, and agrees a next step.
Weak answer
Defends the company, apologizes in general terms and moves straight to renewal terms, offers a discount in the first minutes, promises a roadmap feature, or ends without a next step.
Tell me about an expansion you led. How did you know the customer was ready, and how did you raise it?
Follow up with
- Who on the customer side took it to their budget holder?
- Tell me about an account where you decided not to push for more.
Strong answer
Ties the expansion to an outcome the customer reached or a need they raised, frames it in the customer's goals, brings in sales at the right point if that is the model, and can name an account where they held back because the customer was not yet getting value.
Weak answer
Pitched upgrades to every account to hit a quarterly target, describes 'creating urgency' with invented deadlines, or cannot connect the expansion to anything the customer achieved.

Rating	What it looks like
5 · Strong	Ties every commercial conversation to outcomes the customer has seen, stays calm and honest in a hostile renewal, right-sizes a contract when that keeps the customer, and expands only where there is value.
3 · Mixed	Handles routine renewals and raises expansion when the customer asks, but loses footing in a tense renewal or reaches for a discount too early.
1 · Weak	Avoids commercial topics, or pushes them regardless of the value the customer has seen. Concedes a discount at the first sign of pressure.

Competency 4

Cross-functional advocacy

Customer success managers hear what customers need before anyone else. Turning that into product, support and onboarding changes, without promising what the company has not agreed, is part of the job.

Tell me about a time you got the product or engineering team to change something because of what you heard from customers.
Follow up with
- What evidence did you bring, and how did you gather it?
- What did the product team push back on?
- What did you tell customers while they waited?
Strong answer
Brought evidence from several accounts (how many, the revenue at stake, concrete examples), described the problem rather than dictating a solution, accepted the product team's prioritization, and kept customers informed without promising a date.
Weak answer
Escalated one loud customer's request as urgent, promised the customer the feature, or describes the product team as ignoring customer success.
What would you do if, at the kickoff call, you learned that a sales colleague had promised the customer an integration that does not exist?
Follow up with
- What do you say on the call itself?
- Who do you talk to afterwards, and what do you ask for?
Strong answer
Neither confirms the promise nor contradicts the colleague in front of the customer. Gets the facts quickly, resets expectations honestly with a workaround or alternative, and raises the pattern with the sales lead so the handoff improves.
Weak answer
Confirms the promise to keep the call smooth, tells the customer that sales misled them, or says nothing internally.

Rating	What it looks like
5 · Strong	Brings evidence gathered across accounts, frames problems rather than solutions, resets expectations honestly, and fixes the handoff that caused the problem.
3 · Mixed	Brings customer feedback to other teams and works well with them, but with anecdotes more than evidence, or avoids resetting expectations.
1 · Weak	Passes requests along without evidence, or promises customers things the company has not committed to.

Competency 5

Managing a book of accounts

A customer success manager may carry twenty accounts or two hundred. Deciding where each hour goes, and keeping promises across all of them, separates managing a book from reacting to the loudest customer.

Walk me through how you plan a typical week across your accounts. How do you decide which ones get your time?
Follow up with
- Which accounts do you see least, and how do you stop them slipping?
- What do you run one-to-many instead of account by account?
- What do you record, and where, so a colleague could pick up an account?
Strong answer
Segments accounts by value, risk and lifecycle stage, protects time for renewals and at-risk accounts, serves the long tail one-to-many (webinars, office hours, email programs), and keeps notes a colleague could act on.
Weak answer
Responds to whoever emails first, treats every account the same, or keeps the state of each account in their head.
You inherit 60 accounts from a colleague who left, with thin notes, and 8 of them renew this quarter. What do you do in your first two weeks?
Follow up with
- What would your first message to a renewing customer say?
- What would you ask your manager for?
Strong answer
Triages by renewal date and risk, contacts the renewing accounts first, reads the history that exists (CRM, tickets, invoices), opens each conversation with a reason to talk rather than a generic check-in, and says early what they cannot cover.
Weak answer
Sends the same introduction email to all 60 and waits for replies, or plans a full business review with every account before looking at renewal dates.

Rating	What it looks like
5 · Strong	Segments the book by value, risk and stage, covers the long tail one-to-many, keeps records a colleague could pick up, and asks for help before an account slips.
3 · Mixed	Prioritizes renewals and large accounts sensibly, but the long tail gets little attention and notes are thin.
1 · Weak	Works reactively, account by account, with no view of the whole book. Promises slip without the customer being told.

Never ask

Don't ask a candidate's age, or their graduation year to work it out. Why: age says nothing about customer success skill, and age-based decisions are unlawful in many places.
Don't ask about marital status, children, pregnancy or plans to start a family. Why: none of it is job-related. Describe the hours and customer time zones and ask every candidate whether they can work them.
Don't ask about religion, caste, community or the origin of a surname, directly or by proxy ('What does your father do?'). Why: in India these questions signal caste and religion, which have no bearing on the job.
Don't ask 'Where are you from originally?', 'What is your native place?' or about citizenship. Why: it invites judgments about region and national origin. Ask only whether the candidate is authorized to work where the job is based.
Don't ask about health conditions, disabilities or past medical leave. Why: the only relevant question is whether the candidate can perform the essential functions of the job, with or without reasonable accommodation.
Don't ask for salary history where the law restricts it, as many US states and cities do. Why: it carries past pay gaps into the new offer. Ask for the expected compensation range instead.
Don't ask for a current or former employer's customer names, contract values, churn figures or health data. Why: it asks the candidate to breach confidentiality. Ask them to describe accounts without names or identifying numbers, and use invented accounts in the exercises.

Making the decision

The must-haves are onboarding and adoption, account health and renewal risk, and renewal and expansion conversations. Any 1 on a must-have is a no, and so is any competency rated 1 by two interviewers. A hire needs an average of 3.5 or higher. Treat claimed retention figures as context to probe, not as a score. Each interviewer rates alone before the debrief; the hiring manager decides after it and records the role-play evidence behind each rating.

Questions people ask

How is a customer success manager interview different from a support interview?: Support resolves the problem in front of them; a customer success manager owns the account's outcome over months. So this kit weighs adoption planning, reading renewal risk and commercial conversations, while a support kit weighs troubleshooting, clear replies and pace. Some candidates move well between the two, and the questions show which skills they already have.
How much weight should net revenue retention carry in a CSM interview?: Some, as context. Retention depends on the product, the segment, pricing and the accounts the candidate inherited, and it is hard to verify. Ask what drove the number, and let the account walk-throughs and the renewal role-play carry the rating.
Should a customer success manager interview include a role-play?: Yes. A renewal conversation with an unhappy customer is the moment the job is hardest, and a 15-minute role-play shows more than any question about it. Give the interviewer a written brief so every candidate meets the same customer, and rate against the anchors, not polish.
Can someone from support or account management move into customer success?: Often, yes. Support people bring product depth and calm with upset customers; account managers bring commercial confidence. Use the same questions for every candidate and look for the competency that is new to them, then decide whether onboarding can close the gap.

A kit is step one.

Itya holds every interviewer to the same rubric, records the interview, and drafts the scorecard with the quotes behind each rating. The AI drafts; your team decides. Free plan, unlimited teammates.

Run this kit in Itya All interview kits