Every customer success manager interview case study I've been handed looks the same: here's an account, here's some usage data, present a plan to save the renewal. The trouble is that all the information needed to answer is sitting in the prompt, and on the actual job it almost never is. This piece is for recruiters and CS hiring managers who need to run a case study and score it without guessing. You'll get two cases you can copy this week, the data packet for each, the script for the person playing the customer, and a scorecard written for these exact cases.
My bias, up front. Skillvee is a 60-minute "day at work" simulation that replaces the recruiter phone screen and the first interview round. The candidate solves a real challenge, talks to AI teammates to get the information they need, and defends their decisions on a call, while the screen is recorded. It measures how someone works: communication, collaboration, agency, AI leverage, problem solving, quality of output and time management. Customer success is one of the role families we build for, so I've got opinions about what these cases should look like, and you should weigh them knowing that.
What most customer success interview case studies test, and what they miss
The usual prompts are a churn-risk plan, a 30-60-90 day onboarding plan, or a QBR deck for an account that could expand. They're reasonable choices. They're also closed. The candidate gets the full picture and produces a document, which measures structured writing, and now that a model drafts a decent success plan in under a minute, it measures that less than it used to.
What I've seen separate strong CSMs is that they notice when the dashboard's incomplete, and they go find the missing piece before anyone asks them to. A sponsor who left last month, or an IT approval nobody chased. I call the fix a buried-signal case: give the candidate data that looks healthy or merely slow, put the deciding fact inside a person, and score whether they go and get it. It's the missing-information test, applied to CS.
Case 1: the renewal that looks fine (live, 45 minutes)
Candidate brief (send 24 hours ahead): "You've just inherited Northwind Logistics from a CSM who left. Renewal is in 75 days. You have a 30-minute call with your main contact, Dana, their Director of Operations. Afterward, spend 10 minutes telling us your read on the account and your plan between now and the renewal."
Data packet (fictional, give it with the brief):
| Field | Value |
|---|---|
| ARR | $48,000 |
| Renewal date | 75 days out |
| Seats licensed / active | 60 / 51 |
| Weekly active users, last 6 months | 49, 51, 50, 50, 51, 51 |
| Support tickets, last quarter | 4, all resolved, none urgent |
| NPS (Dana, 5 months ago) | 9 |
| Last QBR | 6 weeks ago, with Dana |
| Executive sponsor | Raj, VP Operations |
Everything on that sheet reads as healthy. That's the point.
Interviewer card (never shared): you play Dana. Be friendly and positive. Hold back three facts and give each one only when the candidate asks something that reasonably leads to it:
- Raj, the sponsor who signed the deal, left the company six weeks ago. (Comes out on any question about the sponsor, leadership, or who's involved in the renewal.)
- The new VP, Priya, has asked every team to list its software with costs by the end of the quarter. (Comes out on questions about budget, priorities, or changes since Raj left.)
- Dana's team loves the product, but Dana doesn't know whether Priya has ever logged in. (Comes out when the candidate asks who else needs to see value.)
If the candidate spends the call on feature adoption and never asks about people, Dana doesn't mention any of it. It'll feel unkind the first time. Hold the line anyway, for every candidate, or the case stops being comparable.
Case 2: the onboarding that stalled (take-home, 60 minutes plus a 20-minute defense)
Candidate brief: "Bluebird Health signed 5 weeks ago. Onboarding was planned for 6 weeks and is behind. Write a one-page recovery plan and a short email to Jordan, the customer's project lead. Before you start, you have 15 minutes to send up to three questions to Sam, the AE who closed the deal. Sam replies within 30 minutes, and your 60-minute writing clock starts when the answers arrive."
Data packet:
| Milestone | Planned week | Status |
|---|---|---|
| Kickoff call | 1 | Done |
| Admin account set up | 1 | Done |
| SSO configured | 2 | Not started |
| First team trained (8 users) | 3 | Done on temporary logins, 3 of 8 attended |
| Data import | 4 | Waiting on customer |
| Second team trained (25 users) | 5 | Not scheduled |
Sam's answers (the recruiter replies as Sam): if asked why SSO hasn't started, the customer's IT team has never been introduced to anyone at your company, and their security review queue is six weeks long. If asked who the champion is, it's Jordan, a clinic manager who was promised the rollout would be "light on IT." Anything else gets a short, honest answer that doesn't hand over the plan.
Anyone can see SSO hasn't started. Strong candidates spend a question on why, because the data import and the second team both wait on real logins. Weaker ones ask about training content and write a plan for more training.
The CSM case study scorecard
Score each dimension 1 to 4, with a quote or a line from the candidate's work next to every number.
| Dimension | 1 | 4 |
|---|---|---|
| Discovery | Asked about features and usage only; hidden facts never surfaced | Surfaced the deciding fact through questions about people, budget, or blockers, then followed up on it |
| Risk read | "Account is healthy" or a generic risk list | Names the specific risk (sponsor gone, SSO blocking the import and the second team) and says why it matters for the renewal date |
| Plan | Activities with no dates or owners | Three or four steps, dated, each tied to the risk, including who at the customer needs to be reached |
| Customer communication | Email or call is generic, could go to any account | Uses the customer's own words, asks for one specific thing, easy to say yes to |
| Internal coordination | Works alone | Pulls in the AE, support, or an exec sponsor on your side where it helps, and says what they need from them |
On Case 2, score customer communication on the email to Jordan. On Case 1, score it on the call with Dana.
For most CSM hires I'd weight discovery and risk read double. A candidate who finds the problem with a rough plan is easier to coach than one with a lovely plan for the wrong problem. Decide the weights before the first candidate, not in the debrief.
Adjusting the case for seniority
| Level | Change to Case 1 | What a 4 looks like on top |
|---|---|---|
| CSM (1-3 years) | Keep as written | Surfaces Raj's departure and plans around it |
| Senior CSM | Dana mentions a team lead, Chris, who's lukewarm on the product | Asks to meet Chris and plans a separate conversation with each person |
| Strategic / enterprise CSM | Make it a $400,000 account, and add a fourth hidden fact: procurement has already asked a competitor for a quote (comes out on asking how Priya's review will be run) | Plans the exec conversation with Priya and what evidence to bring to it |
Live or take-home, and what about AI?
Run Case 1 live, since the hidden facts don't work anywhere but a conversation. Run Case 2 as a take-home when you need to see the candidate's writing, and keep the defense call. That's where you find out whether they understood their own plan or just wrote it.
I'd let candidates use AI on the take-home and tell them so. The case is built so the answer isn't in the packet. A model will turn the milestone table into a tidy recovery plan, and it'll flag SSO, since that row says "Not started." What it can't know is that nobody has ever met the customer's IT team or that their review queue is six weeks long, and a plan that says "configure SSO in week 6" falls apart on that. The candidate still has to spend a question in the right place. That's the behavior you're paying for, and it's the same bet I'd make for sales role plays: fix what the other person knows, then watch who goes and finds it.
If the case is your second step, the recruiter phone screen template has a CSM screening question that pairs with it.
Where this gets hard
Whoever plays Dana has to hold the script. Interviewers like candidates and start helping them, usually around the third interview of the day. Write the three hidden facts and the questions that surface them on a card.
The data packet needs a sanity check too. I've broken my own cases this way. If the usage table shows a drop, candidates will chase the usage and never ask about people, and you've built a different case by accident. Keep the numbers boring on purpose.
And a case adds time. Forty-five minutes of a CS manager plus the scoring is real cost, so it belongs after a screen, not in front of every applicant. If you need something cheap for the first cut, a customer success manager assessment from a test library is fine there. Just don't read its score as what the case shows.
How this maps to what we run
Inside Skillvee, customer success candidates go through the same shape: an account review or escalation where the information they need sits with AI teammates, which can include a customer they have to talk to, followed by a written deliverable and a call where they defend it. The report scores onboarding and enablement, escalation handling, value realization, relationship management and communication. You don't need us to run the two cases above, though. A recruiter, a CS manager and the cards in this piece are enough. If you'd rather see the cost of running it across a req list, the pricing page has the plans.