Background
This candidate was an account manager with an operations background. They were interviewing for a technical, mid-market customer success role at a SaaS company.
They had real customer experience. The role asked them to present it differently: as technical, scalable and tied to business value. Most of the stories in this series show a quick turnaround. This one doesn't, which is why it's worth reading.
The challenge
The first two sessions scored 2.3 and 2.2 out of 5. After the early sessions, the coach's hiring-style verdict was "maybe." It flagged four separate moments where the candidate didn't answer the question they were asked.
Two habits stood out.
The first was describing a process instead of telling a story. Asked for an example, they explained how they generally handle that kind of situation. A process shows how you think in theory. One specific customer, and what happened, shows what you actually did.
The second was undercutting the role itself. In an interview for a technical customer success position, they said they didn't deliver technical solutions. That one sentence weakened much of what came before and after it.
The coach flagged smaller patterns too. There was no clear pitch for why this company. Hard questions sometimes led to a different success story that didn't fit. Filler phrases crept into their answers. And when they did describe a fix, it often relied on manual spreadsheets, where a mid-market book of business calls for something that scales.
What they did
Every session was a full mock interview, covering a recruiter screen, their background, and executive presence.
For a while, nothing moved. Four sessions in a row landed on the same score. They kept practicing, and a few days in the plateau finally broke. Over the next several days, their scores rose a little each time.
The results
The second-to-last day was their busiest, with six sessions, and the most uneven. One of them fell all the way back to their lowest score from the first day. The next session reached their best so far.
On the final day, they ran one more full mock. It tied their best score, and the coach's verdict on that session was "advance." Their average coach score went from 2.25 in their first two sessions to 3.55 in their last two.
That verdict is the coach's read on one practice session. It is not a prediction of what a hiring team will decide. They didn't tell us how the real interview went, so we won't guess.
What other customer success managers can take from this
Don't disclaim the core skill. If the role has "technical" in the title, don't say you aren't technical. Describe the most technical work you've done and how you would grow from there. The customer success manager interview guide covers the technical questions these roles tend to ask.
Tell one story, not a process. "Usually I would..." is a description. "Last year, one account..." is evidence. Pick a single customer and tell what happened. The STAR method guide shows the structure.
Show a solution that scales. A spreadsheet can fix one account's problem. For a mid-market book, talk about automation, playbooks or tooling that works across accounts.
Expect a slow climb. When you are moving in from a nearby role, the new framing can take many sessions to come naturally. This candidate hit the same score four times in a row before it moved, and kept going.
If you are moving into customer success, you can practice the interview out loud on Revarta and track which habits are still costing you.
