Sample AI interview report

Hi Jamie, thanks for making the time. I'm Alex, and I'll be running this first interview for the Customer Success Manager role. It takes about eight minutes and it's a conversation, so there's no rush. Could you start by telling me a bit about yourself and what you're doing now?

Sure. I've been in customer-facing roles for about five years. I started in support at a B2B software company, moved into customer success there, and for the last three years I've been a CSM at a workflow software company. I look after around sixty mid-market accounts, mostly onboarding and renewals, and I'm looking for a team where success is a bit more strategic.

Got it. Your resume says you reduced churn significantly in your book. What did that look like?

Yeah, churn was a big focus for me. I was really proactive with my accounts, checking in regularly and making sure they were getting value, and churn came down a lot over the year.

When you say it came down a lot, what were the numbers before and after, and over what period?

Fair question. Gross revenue churn on my book was about fourteen percent annualised when I took it over, and about nine percent twelve months later. I should say part of that was a pricing change the company made that year, which moved some smaller customers onto annual contracts. The part I'd claim is onboarding: I rebuilt the first thirty days so every new account had a named admin and a first workflow live by day fourteen.

Helpful. How did you know the onboarding change was working, and not just the pricing change?

I compared accounts that went through the new onboarding with ones onboarded before it, on the same contract type. The new group had noticeably fewer cancellations in the first six months. It wasn't a controlled test, but the gap held for three quarters.

Your resume also mentions building a customer health score. How did it work?

We looked at usage, support tickets and sentiment, and combined them into a red, amber, green score, so we could see which accounts needed attention.

How were those inputs weighted, and what exactly moved an account from amber to red?

Honestly, our ops team maintained the formula. I suggested what went into it and I used it every week, but I couldn't tell you the exact weights. Red was roughly when logins dropped and tickets went up at the same time.

Thanks for being straight about that. Say a customer's main champion leaves and usage drops by half. What do you do?

I'd get the right people involved quickly and make sure the customer sees the value again.

Who are the right people, specifically, and what would you show them? If it's happened to you, walk me through the real one.

It happened last spring. Our champion at a logistics customer left, and weekly active users fell from about forty to eighteen in a month. I found the new operations lead, booked thirty minutes with her and their finance manager, and instead of a feature demo I showed them the three reports their team had stopped running and what those reports had saved them the quarter before. Then I ran two short training sessions for the new users. They renewed, a bit smaller: ten seats instead of twelve.

Looking back, what would you do differently on that account?

I'd have had more than one relationship there before the champion left. Our admin and our sponsor were the same person. Now I aim for three named contacts per account by the first renewal: the admin, a sponsor, and someone in finance, because finance is who asks what the tool costs the moment a champion leaves.

Got it. This role also carries an expansion target. Tell me about an upsell you drove yourself.

In my current role expansion goes to the account executives. I flag opportunities, I think about ten last year, but I haven't run the commercial conversation myself. It's something I want to do more of.

Understood. Tell me about a time you disagreed with a customer or with your own team. How did it end?

A customer wanted a custom integration built for free as a condition of renewing, and our product team said no. I didn't want to just pass on a no, so I asked what they actually needed, which was a nightly export into their finance system. I showed their admin how to do it with our existing API and a scheduled job. It took an afternoon, they renewed, and we turned the steps into a help article.

That's all my questions. Is there anything you'd like the team to know that we didn't cover?

Just that I'd like to own renewals and expansion together. I think those two conversations are closer than most companies treat them.

Thanks, Jamie, I appreciate the detail. The team will review the interview and be in touch about next steps. Take care.