Questions to Ask a Customer Success Manager
For hiring managers and founders interviewing a customer success manager (CSM) candidate. The questions follow the order of a good interview: their background and the numbers they answered for, onboarding, spotting risk and handling renewals, the hard moments with customers, working with sales, product and support, and their habits and fit for your job.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Background
What does customer success mean to you, and how is it different from support?
Why ask it
Start here, because the title covers very different jobs from one company to the next. A candidate who describes waiting for problems to arrive has been doing support under another name. The stronger answer is about getting customers to the result they paid for, and reaching out before they have to ask.
Why customer success, and not sales or support?
Why ask it
Some candidates want the relationship without a quota, some came up from support and liked the customers more than the tickets, and some see this seat as a step toward account executive. All three can work. What you need to know is which one you have, and whether your role gives them what they came for.
How many accounts did you carry in your last role, and roughly what was that book worth in recurring revenue?
Why ask it
A few dozen large customers and several hundred small ones build opposite habits: long meetings with a handful of buyers on one side, email programs and group webinars on the other. A rough range is enough, since exact figures may not be theirs to share. Hold the answer against the book you plan to hand over, and ask what they would have to do differently at your size.
Which numbers were you personally measured on, and how did you finish against them last year?
Why ask it
People who were held to a retention or expansion figure can usually say it from memory, with the target beside it. If what you get is a team number, ask what their own book did inside it. Never having carried a number is no mark against them, but plan for an adjustment if your role has one.
Did you own the renewal yourself, or did it pass to sales or a renewals team?
Why ask it
Companies split this in different ways, so a candidate may have done far more commercial work than the title suggests, or far less. Ask who sent the quote and who took the call when the customer pushed back on price. Then say plainly how it works in your company, so neither of you is guessing.
Tell me about an account that grew while you managed it. What did they buy, and what part of that was your doing?
Why ask it
The second half is where the story gets honest. Some growth simply happens because the customer hired more people, and a good candidate will say so. Give credit for a specific move: a second team they introduced the product to, or a problem they heard in a review and matched to something their company already sold.
Who were your customers: what size of company, and who was your day-to-day contact there?
Why ask it
Looking after the owner of a ten-person firm is a different skill from working with an operations director who has procurement, security and a boss to satisfy. Ask who the most senior person they dealt with regularly was. If your buyers sit higher or lower than that, name the gap and see how they respond.
Take me through a normal week with that book. Where did the hours actually go?
Why ask it
You are listening for how much of the week they planned and how much simply arrived. A week made only of replies and urgent calls means the book was running them. Ask which task they would have dropped if they could, since it is often one your job also includes.
Onboarding
Walk me through how you onboard a new customer, from the handoff to the day you would call them live.
Why ask it
Have them tell it through one real account so you get steps and not a diagram. Pay attention to what 'live' means to them. A checklist with every box ticked is a weaker finish line than the customer doing, without help, the thing they bought the product to do.
What do you want to know about a new customer before your first call with them?
Why ask it
A strong list covers why they bought, what they were promised, who signed, who will use it and any deadline on their side. Ask where that information came from in their last job. Customers notice quickly when they are asked the same questions they answered during the sale, and it costs trust in the first week.
How do you pin down what a new customer wants from the product, in terms you can both check later?
Why ask it
The reason in the contract and the reason in the buyer's head are often different, and the renewal is usually judged on the second. Good candidates describe asking for the goal as a result with a date, writing it down, and bringing it back at every review. Ask for an example where the first answer turned out not to be the real one.
How long did onboarding usually take in your last role, and what made the slow ones slow?
Why ask it
The length depends on the product, so the figure matters less than whether they know it and can say what stretched it. Listen for causes they could act on, such as a data export that never arrived or no named owner at the customer, and for what they changed afterward. If your own onboarding runs much shorter or longer, say so and ask what they would do differently.
An onboarding has stalled because the customer's own team has stopped doing their part. What do you do?
Why ask it
This happens in almost every book, so there should be a practiced answer. Useful ones include cutting the next step down to something that takes ten minutes, asking the sponsor what changed in their priorities, or resetting the date openly. 'I kept following up' is the reply to worry about, since it describes waiting.
How do you get people to use a product their boss chose for them?
Why ask it
The people logging in every day did not sign anything and may resent the change. The better approaches start from their existing work: training on the customer's own data, one early win for one team, a named person on the inside who likes it. More invitations to more webinars is the weak version.
Explain a product you have supported to me as if I were a new user on my first day.
Why ask it
This one is a work sample, so give them two minutes and play the part. Notice whether they begin with what you are trying to get done or with a tour of the menus, and whether they check you are following. Jargon from their old company that they never stop to explain is worth a note.
Risk and renewals
How do you tell an account is at risk before the customer says so?
Why ask it
Fewer logins, meetings that keep getting moved and a new boss on the customer's side are the usual answers. Ask which sign they trust most and which one has fooled them. The stronger candidates add something they noticed for themselves in a real book, and can say what they did the week they saw it.
Tell me about an account you saved. What was wrong, and what did you do first?
Why ask it
'First' is the word that matters. A candidate who opened by finding out what had actually gone wrong will usually have a save that lasted. One who opened with a discount may have only moved the problem to the next renewal, so ask how that account is doing now if they know.
Tell me about a customer who left anyway. Looking back, when could you have known?
Why ask it
Nearly everyone who has carried a book has lost an account, and the useful part is the moment they point to: a meeting, an email that went unanswered, a change they shrugged off. If every loss was down to the product, the price or the sales team, you have learned how they will explain losses to you.
Your main contact at a customer leaves the company. What do you do that week?
Why ask it
The best answer begins before the week in question, with a second and third relationship already in place. After that, the moves that count are reaching the sponsor quickly and briefing the replacement on why the company bought in the first place. Waiting for the new person to get in touch is how accounts drift away.
A customer's usage looks healthy, but nobody there replies to you anymore. How do you read that?
Why ask it
There is no single right reading, which is the point. It could be a team that needs nothing, or a decision being made somewhere the candidate cannot see. Look for curiosity: trying a different person, sending something worth opening in place of another check-in, confirming who will decide the renewal.
Tell me about a time the health score said an account was fine and you did not believe it. What happened?
Why ask it
The story should include a reason they could defend to a manager and something they did about it. Ask whether they turned out to be right, and whether they can name a time they were not. If their last company kept no score, ask what they went by instead.
How far ahead of a renewal date do you start working on it, and what is the first thing you do?
Why ask it
A good reply has a number of months in it and a first step about the customer's results, not the paperwork. Timing varies with contract size, so ask how it changed for their largest accounts. Starting when the system sends a reminder means every objection will come as a surprise.
A customer says they will renew only at a lower price. Talk me through the conversation.
Why ask it
Listen for a question before any concession: what changed, what they are comparing you with, who is asking. Then listen for a trade, such as a longer term or fewer seats, in place of a straight cut. Tell the candidate how much authority over price the role has with you, and ask how much they had before.
How do you bring up an upgrade or extra seats without sounding like you are selling?
Why ask it
The comfortable answers tie the suggestion to something the customer already said they wanted, or to a limit they keep hitting, and pick a moment just after a result. Some people in this work dislike talking about money at all. If your role carries an expansion target, this is where you find that out.
How do you run a business review so the customer feels the hour was worth it?
Why ask it
Weak reviews are a tour of usage charts followed by the roadmap. Stronger ones open with the goals the customer set, show progress in the customer's own terms and end with a decision or two. Ask who from the customer's side used to attend, since senior people keep coming only when the meeting is useful to them.
Hard moments
Tell me about the angriest customer you have dealt with. What did you say in the first five minutes?
Why ask it
People who have handled a call like this tend to remember their opening words. The good versions let the customer finish and say the problem back to them before explaining anything. If the candidate still sounds irritated with that customer while telling the story, weigh it.
How do you tell a customer no?
Why ask it
Ask for the last time, whether it was a feature request, custom work or a refund. A clear no comes with the reason and with something the customer can do instead. Be wary of 'I'll take it back to the team' used as a way to end the call, because the customer hears a maybe and comes back for it.
A customer finds out in week two that the product does not do something they were told it would. What now?
Why ask it
With the customer, a good reply has the truth early and whatever can honestly be offered in its place. Inside the company, it has a direct word with the salesperson and a note to whoever can stop it from recurring. Blaming the rep in front of the customer is the version to watch for.
The product is down and your biggest account is on the phone. What do you tell them, and what do you leave out?
Why ask it
What gets left out says the most: experienced people do not guess at a fix time or speculate about the cause. They say what is known and when the next update will come, then keep that appointment even if there is nothing new. Ask what they did for the customer after it was over.
How do you deliver bad news the customer is not expecting, such as a price increase or a feature being retired?
Why ask it
The careful way is a call before an email, as early as they were allowed, with a plan for what the customer can do next. Ask whether they have ever softened a message so far that the customer missed it. It is an easy mistake for people who are good at being liked.
Tell me about a mistake you made with a customer. How did they find out?
Why ask it
How the customer found out separates candidates who owned up from those who were caught. A small, real error with a plain account of the repair is worth more than a strength dressed up as a flaw. If no mistake comes to mind after a pause, ask about a deadline they missed.
A customer treats you as their help desk and messages you about every small problem. How do you change that?
Why ask it
The skill is moving the requests without making the customer feel passed along. Good answers fix the cause, perhaps by training the users who ask most or by introducing the support team by name. If you have no separate support team, say so, because then some of this simply is the job.
When have you gone over your contact's head, and how did you keep the relationship afterward?
Why ask it
Sometimes a sponsor has to hear something the daily contact would sooner keep quiet. The careful version involves telling the contact beforehand, or bringing them into the conversation. A candidate who has never needed to do it may have managed accounts that were only one person deep.
Other teams
Tell me about a disagreement with a salesperson over an account. How was it settled?
Why ask it
The usual causes are who gets to raise an upsell, a customer who was a poor fit from the start, or a rep contacting the account without warning. Look for a direct conversation before any escalation, and for a story told without a grudge. You are hiring someone who will sit next to your sales team every day.
How do you pass customer feedback to the product team so that something happens?
Why ask it
Forwarding every request is the weak method. Better ones describe the problem behind the request, how many accounts share it and what is riding on it. Ask for one piece of feedback that shipped and one that did not, and what they told the customer in the second case.
A customer asks when a feature on the roadmap will ship. What do you say?
Why ask it
The trouble with a date they do not control is that the customer will plan around it. The safer answer gives what is known, stated carefully, and a workaround for the meantime. Tell them your own rule on roadmap commitments and see if it sits easily with them.
Where did your job end and support's begin, and what did you do with a ticket that had sat too long?
Why ask it
The line is drawn differently everywhere, so first get their version of it. Then listen to how they chased: asking the right person by name and keeping the customer informed is good. Quietly doing support's work themselves, or running the support team down to the customer, each causes its own trouble later.
How do you spot a customer who should never have been sold to, and what do you do about it?
Why ask it
This tests candor more than technique. A thoughtful answer covers being honest with the customer about what the product will and will not do, and taking the pattern back to sales with examples. Occasionally the right outcome is helping them leave on good terms, and a candidate who can say that has seen it.
When have you turned a happy customer into a reference, a review or a case study?
Why ask it
Ask how they made the request and when. Right after a result the customer can name is the natural moment, and the request works best when it is small and specific. Someone who has never asked may well have had satisfied customers that nobody outside the account ever heard from.
Habits and fit
If I handed you a book tomorrow with more accounts than you could call in a month, how would you sort it?
Why ask it
Revenue, renewal date, risk and room to grow are the sensible inputs, and a good candidate will ask you for them. 'Whoever is loudest' is the honest description of a bad system. Ask what the smallest accounts would get.
Which tools have you used to keep track of accounts, and what did your notes look like after a call?
Why ask it
The software matters less than the habit. Ask what a colleague would find if they took over one of the candidate's accounts tomorrow: the contacts, what was promised, the next step and its date. Tell them what your team uses and ask what they would need in order to pick it up.
How do you use product usage data when you talk to customers?
Why ask it
The useful habit is specific, such as checking the numbers before each call and bringing one observation the customer has not seen. Not every company gives its CSMs usage data. If theirs did not, ask how they knew what their customers were doing, and what they would look at first if they had it.
What do you find hardest about this work?
Why ask it
Common honest answers are the constant switching between accounts, answering for a number while having no control over the product, and absorbing other people's frustration. None of them rules anyone out. Set the answer beside your own job, and be straight if the hard part they name is a large part of it.
What have you found out about our product, and where do you think our customers get stuck?
Why ask it
Learning someone else's business quickly is a large part of this job, and yours is the business they had notice of. Credit a candidate who tried the product, read your help pages or public reviews, and arrives with a guess they can defend. Then ask what they would want to learn in week one.
Have you worked somewhere with no playbook? What did you build?
Why ask it
For a founder hiring a first CSM this may be the deciding question. Look for a thing they made that others then used: an onboarding checklist, a renewal calendar, a set of emails for quiet accounts. If they have only worked inside a mature team, ask what they would miss most on day one with you.
How would you spend your first 30 days with a book you inherited from someone else?
Why ask it
Judge the order of things. Reading the account history, finding the nearest renewals and holding introduction calls that do not make the customer start from zero are a sound beginning. A plan to change how every account is run in the first month should give you pause.
Here is a real situation from one of our accounts. What would you want to know before doing anything?
Why ask it
Prepare one in advance with the names taken out, such as a customer whose logins fell after a reorganization. You are scoring the questions they ask, not the plan. Candidates who jump straight to a solution will do the same with your customers.
What are you looking for in your next job that the last one did not give you?
Why ask it
For a CSM the answer might be a smaller book, a say in the renewal, a product with fewer gaps or a path to leading a team. Set it against what you can truly offer, and say so now if you cannot. If the reply is only about a former manager, ask what the work itself was missing.
What do you need to know about our customers and our churn before you could say yes to this job?
Why ask it
Their questions are a sample of how they will run a first call with a customer. Serious candidates ask about book size, who owns the renewal, why customers leave and how pay is tied to results. Answer honestly, including the figures you are not proud of.
How to interview a customer success manager
Practical guidance for the conversation itself
Before the interview
Decide which job you are hiring for
Customer success is not one job. Write down the size of the book, whether the accounts are named or pooled, who owns the renewal, whether the role carries an expansion target and how much support work comes with it. Most of the notes on this page ask you to compare an answer with your own setup, and you cannot do that until it is on paper. It also gives you something truthful to tell the candidate.
Spread the groups across the rounds
Background suits a first call: book size, the numbers and who owned renewals tell you quickly whether the experience fits. Onboarding and Risk and renewals belong in the main interview, where there is time for whole stories. Keep Hard moments and the work samples for a later round, and give Other teams to an interviewer from sales or product if you have one.
Bring one real account
Pick a situation from your own customers, remove the names and write it in four or five sentences: who the customer is, what they bought, what has changed. A real case shows how the candidate thinks about your kind of customer, which no general question can. Use the same one with every candidate so the answers can be compared.
Agree on what a good answer is
If several people are interviewing, settle beforehand which questions each will ask and what a strong and a worrying reply would sound like. Otherwise one interviewer scores warmth, another scores commercial instinct, and the debrief becomes an argument about what the job is.
In the interview
Ask for one account, not a method
'How do you handle churn risk?' gets a framework anyone can recite. 'Tell me about the last account you were worried about' gets a customer, a date and a result. Whenever an answer stays general, ask which account they are thinking of and stay with that one.
Get the numbers with their context
A retention figure means little without the size of the book, the kind of customer and who owned the renewal. Ask for all of it together. You are not checking arithmetic. You are finding out whether the candidate knows their own results well enough to have been steering by them.
Play the customer once
Pick one of the Hard moments questions and act it out for three minutes: you are the customer who has just learned about the price increase, or the one whose rollout has stalled. Tell candidates in the invitation that a short role-play is coming. You want to see how they do the job, not how they cope with being surprised.
Leave ten minutes for their questions
The last question on the page invites them, and it needs room. Someone who asks nothing about your customers or why they leave is showing you how a first call with a new account might go, so do not let the hour run out before you get there.
Reading the answers
Listen for 'I' and 'we'
Customer success is team work, so 'we' is natural. When a story matters, ask what the candidate did themselves: who made the call, who wrote the plan, who noticed the problem. Strong people can separate their part from the team's without claiming all of it.
Notice how they speak about customers
A candidate can describe a difficult customer and still explain what that customer needed. One who sneers at customers in an interview, where everyone is on best behavior, is unlikely to be kinder about them in your team chat. The same goes for how they describe former salespeople and support colleagues.
Value a loss told plainly
The account they lost and the mistake they made are often the most useful answers in the hour. Someone who can say what they missed, and what they do differently now, has turned a bad quarter into a skill. A record with no losses in it usually means a short one or a selective memory.
Look for fit with your book, not the best resume
A person who thrived with twenty large accounts may be unhappy with three hundred small ones, and the reverse is equally true. After the interview, set what they have done beside the job description you wrote beforehand. The gaps are what you would have to train, so decide whether you can.
Mistakes to avoid
Hiring for warmth alone
Nearly everyone who applies for this work is pleasant to talk to, so likeability will not separate candidates. The questions about saying no, delivering bad news and negotiating a renewal are there to show whether the candidate can be liked and still be direct.
Asking only hypotheticals
A page of 'what would you do if' produces sensible answers from everyone, including people who have never done the thing. Keep the scenarios to two or three and spend the remaining time on what actually happened in their last book.
Hiring a salesperson or a support agent by accident
A candidate who lights up only when talking about expansion may be an account executive in waiting. One who talks only about solving tickets may want a support role. Either can be a fine hire if that is the job you have. The mistake is finding out after the offer.
Hiding the hard part of your own job
If the book is large, the product has gaps or churn is high, say so in the interview. A candidate who accepts knowing that has chosen the job as it is, and one who finds out in month two has not. How they react to the news is itself an answer.