Customer Success Manager Questions to Ask Interviewer
For customer success manager candidates who want to know what they are really walking into. Twenty questions that surface book size, retention targets, comp structure, churn history, and how much of the job is support work.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
How would you describe what a CSM here actually does in a normal week?
An easy opener that quickly separates a real strategic CS role from a rebranded support queue. Listen for whether the week is built around proactive account plans or around inbound requests.
- 2
How many accounts would I own, and roughly how much ARR does that book represent?
Book size and ARR per account decide whether this job is doable. Forty accounts at 60k each is a different job from 300 accounts at 4k each, even though both are called customer success manager.
- 3
Which segment would I cover, and is that segment high touch, low touch, or pooled?
Tells you whether you will be running executive business reviews with named accounts or building scaled programs and email plays for a shared queue. Both are valid, but they build very different resumes.
- 4
What would you want me to have accomplished by day 30, day 60, and day 90?
Forces the hiring manager to be concrete about ramp. Vague answers here usually mean the role is undefined, and you will be expected to invent it while carrying a full book from week one.
- 5
Which metrics is the CS team measured on this year: gross retention, net retention, adoption, CSAT, or something else?
The scoreboard tells you what the team really values. If nobody can name the primary metric, your performance review will be based on impressions rather than numbers you can influence.
- 6
Does this role carry a renewal or expansion number, and is it a personal quota or a shared team goal?
Many CS roles have quietly become quota carrying. You need to know before you accept whether you are being hired to retain, to sell, or to do both without sales support.
- 7
How is the compensation split between base and variable, and what specifically triggers the variable payout?
Reveals whether the bonus is tied to something you control, like renewals in your book, or to company wide results you cannot move. Ask what percentage of CSMs hit their variable last year.
- 8
Can you walk me through the handoff from sales to onboarding to CSM, and who owns the customer at each stage?
Broken handoffs are the single most common source of CSM frustration. A clear answer with named owners and a documented process suggests the revenue org is genuinely coordinated.
- 9
Where does the line sit between customer success and support, and who handles inbound tickets?
If CSMs are the de facto tier one support team, your calendar will be consumed by triage and you will never get to renewals or adoption work. Ask for a rough percentage of time spent on tickets.
- 10
What systems would I live in day to day, and how much do you trust the customer data in them?
There is a big difference between a mature Gainsight or Vitally instance and a spreadsheet plus a stale CRM. Poor data means you will spend your first quarter doing manual archaeology on your own accounts.
- 11
How do you define account health today, and does the team actually trust the health score?
Health scoring is where CS teams reveal their maturity. Hearing that the score exists but nobody believes it is useful honesty, and it tells you what your early improvement project could be.
- 12
What was the number one reason customers churned in the last twelve months?
A specific answer, such as a lost champion or a missing integration, shows the team does real loss analysis. A generic answer about budget cuts often means churn is not being diagnosed at all.
- 13
Which accounts in this book are at risk right now, and what has already been tried on them?
Surfaces whether you are inheriting a stable portfolio or a rescue mission. It also lets you judge whether the recovery plan so far has been thoughtful or purely reactive.
- 14
How does customer feedback reach the product team, and can you point to a recent change a CSM drove?
A named example proves CS has real influence. If nobody can name one, expect to keep apologizing to customers for gaps you have no ability to close.
- 15
What happens when a customer needs something the roadmap will not deliver this year?
Tests whether the company supports honest conversations with customers or expects CSMs to keep promising and stalling. The answer predicts how much of your credibility you will have to spend.
- 16
Who does customer success report up to, and how does that shape the team's priorities?
CS under a CRO tends to be revenue driven with strong commercial backing. CS under support or operations tends to be service driven with smaller budgets. Neither is wrong, but it changes the job.
- 17
Is this role a backfill or new headcount, and how long has the average CSM been on the team?
A backfill plus short tenure is the clearest early signal of burnout or unrealistic books. If it is new headcount, ask what changed to justify adding it now.
- 18
What separates your strongest CSM from the middle of the team?
Shows you what behavior actually gets rewarded here, whether that is commercial instinct, product depth, or executive presence. Then you can judge honestly whether that is your strength.
- 19
What does progression look like from this role: senior CSM, team lead, CS ops, or a move into sales?
Ask for recent examples of people who moved. A career path that exists on a slide but has never been walked by anyone is not a career path.
- 20
If I joined and left within a year, what do you think the most likely reason would be?
A closing question that invites candor and usually surfaces the real weakness of the role, whether that is churn pressure, staffing, or product gaps. How openly they answer tells you a lot about the manager.
How to Use These Questions in a CS Interview
Practical guidance for the conversation itself.
Best Practices
Best Practices
Do the arithmetic out loud
When they give you a book size and an ARR figure, work out the average account value and the retention dollars you would be responsible for. Saying 'so that is roughly 3 million in renewals across 45 accounts' shows commercial thinking and gives the interviewer a chance to correct the number.
Anchor two questions in their actual product
Sign up for a trial, read their help center, or skim recent release notes, then ask about a specific onboarding step or feature gap. Generic questions get generic answers. A question about their own activation flow gets you a real conversation about how customers struggle.
Ask the same question to two different interviewers
Ask the hiring manager and a peer CSM how success is measured, or what causes churn. When the answers do not match, you have found something worth probing in the final round. Consistency across the panel is itself a signal about how well run the team is.
Save compensation and quota questions for the right person
Recruiters own base, variable, and quota structure, so ask them early rather than burning hiring manager time. Save book composition, at risk accounts, and product influence for the hiring manager and peers who live with those problems.
Which Questions Fit Which Interviewer
Which Questions Fit Which Interviewer
- Recruiter screen: base and variable split, whether the role carries a quota, segment, book size, whether it is a backfill.
- Hiring manager: 30 60 90 expectations, primary team metric, top churn reason, at risk accounts in the book, what separates their best CSM.
- Peer CSM: what a normal week looks like, how many support tickets land on CS, whether the health score is trusted, the sales to CS handoff in practice.
- Cross functional interviewer such as an AE or product manager: how feedback reaches product, what happens when the roadmap says no, where CS and support divide.
- VP or executive round: where CS reports, how the team plans to hit net retention this year, what progression from this role has looked like for others.
Answers That Should Worry You
Answers That Should Worry You
No one can name the primary metric
If gross retention, net retention, and CSAT all get mentioned without a clear priority, your reviews will be subjective and your priorities will shift with whoever complains loudest that quarter.
The book size keeps changing across interviews
Hearing 40 accounts from the recruiter and 90 from the hiring manager usually means territories are unsettled or attrition has left orphaned accounts that will quietly land on you.
Churn is explained only as budget cuts
Budget is often the reason a customer gives, not the reason they left. Teams that stop at that explanation are not running loss reviews, which means the same churn will keep arriving in your book.
CS is described as owning renewals with no commercial support
Carrying a renewal number is fine. Carrying it with no pricing authority, no deal desk, and no AE partner means you will be negotiating contracts without the tools to win them.
Numbers to Walk Away With
Numbers to Walk Away With
- Accounts per CSM and total ARR under management for this specific book.
- Current gross retention and net revenue retention, ideally as a trend rather than one figure.
- Base salary, variable target, and the percentage of the team that hit variable last year.
- Average CSM tenure on the team and how many people are in the role today.
- Rough share of your week expected to go to support tickets versus proactive account work.