Customer Success Manager CV Example & Writing Guide

The full CV example

One mid-level CSM CV, a mid-market book in field-service software.

Nobody on this page is real. Mateo, Pulsaro and Cadenza Events are invented for the example, along with every account count and euro figure. Replace all of it with your own details and your own book.

Why this CV works

Five things this example does that a portfolio-of-accounts CV does not:

• The book has a size, a value and a shape

  "38 mid-market accounts, 4.2m EUR ARR, average 110k EUR and a range from 35k to 390k" answers the first three questions a CS leader has, in one line. The fourth clause, "the top five accounts are 41% of the book", is the one almost nobody writes, and it tells a reader this person understands concentration risk rather than just their own headcount.

• The retention numbers name their base

  94% gross and 111% net are stated "against the 3.9m EUR that came up for renewal, not against the whole book". Retention figures are trivially inflatable by choosing a friendly denominator, and a CSM who volunteers the base before being asked is telling the reader the rest of the page was calculated the same way.

• The split with sales is written down

  "I qualify and build the case, the AE prices and signs" stops 310k EUR of closed expansion from reading as a quota this person did not carry. The same move appears with support: "support keeps the ticket and I keep the relationship". CS sits between two functions, and vagueness about the boundary is read as overclaiming.

• A save is a process, not a rescue story

  "6 of 9 accounts that entered the at-risk process, 780k EUR retained" carries the denominator again, and names the method: a written recovery plan with a named executive sponsor on each side. Three accounts still left. Saying so makes the six believable.

• It shows the health score being wrong and fixed

  The old score "rated two of the three accounts that churned as green a month before they left". Admitting the miss is what makes the rebuild into four inputs sound like judgement rather than tool administration, and it is a far better interview topic than a list of Gainsight features.

Professional summary examples

Entry level

At entry level the book may not be yours alone. Say pooled, give the count anyway, and name what you want next.

Mid level

Count, value, segment, both retention figures, expansion. Five facts in three sentences is the density a CS leader is scanning for.

Senior

Senior is where the book gets smaller and the numbers get bigger. Name what you are trusted with, and close with an offer rather than a job description.

Experience bullet examples

Thirteen bullets, weak form and strong form. Every account count, euro figure and retention rate below belongs to the fictional example - substitute your own book and your own renewal record, because these are the first numbers an interviewer will ask you to walk through.

Weak

Managed a portfolio of customer accounts.

Stronger

Held 38 mid-market accounts, 4.2m EUR ARR, averaging 110k with a range from 35k to 390k.

Why

The single highest-value rewrite on a CSM CV. Count, value, segment and spread turn an unjudgeable sentence into a job description.

Weak

Responsible for renewals.

Stronger

Closed 22 of 24 renewals in 2025 for 94% gross revenue retention, measured against the 3.9m EUR up for renewal.

Why

Give the base. A retention percentage with no denominator is the easiest figure on a CV to inflate, and good readers discount it accordingly.

Weak

Grew revenue within existing accounts.

Stronger

Sourced 640k EUR of expansion pipeline and closed 310k with the AE team, contributing to 111% net retention.

Why

Sourced and closed are different claims. Separate them, and say who priced the deal.

Weak

Reduced churn.

Stronger

Saved 6 of 9 at-risk accounts, retaining 780k EUR of ARR, using a written recovery plan with a named executive sponsor on each side.

Why

Three accounts still churned. The 6 of 9 is credible precisely because it is not 9 of 9.

Weak

Onboarded new customers.

Stronger

Cut time to first value on mid-market accounts from 41 days to 26 by moving technician data import ahead of admin training.

Why

Define first value for your product, then show the change. Onboarding speed is the earliest retention lever you own.

Weak

Monitored account health.

Stronger

Rebuilt the health score from one usage metric into four inputs after the old version rated two of three churned accounts green a month before they left.

Why

The failure is what justifies the rebuild. Without it this is a sentence about configuring a tool.

Weak

Handled escalations.

Stronger

Ran 31 escalations last year at a median 4 days to resolution, with support owning the ticket and me owning the relationship.

Why

Volume, speed, and the boundary. Escalation bullets without a boundary make a reader wonder whether you were the CSM or the support queue.

Weak

Conducted quarterly business reviews.

Stronger

Ran executive reviews on the 14 accounts above 100k EUR, each opened with the customer's own adoption numbers rather than our roadmap.

Why

Say which accounts get the review and what is in it. Every CSM has run a QBR; not every CSM has decided what belongs in one.

Weak

Worked closely with the sales team.

Stronger

Split the account plan with the AE in writing: I own adoption, risk and the renewal case, the AE owns pricing and the signature.

Why

A written split is a real artefact and it prevents the interview question about who actually closed the deal.

Weak

Gathered customer feedback for the product team.

Stronger

Turned recurring complaints into a monthly summary for product; three of the requests shipped as fixes within two quarters.

Why

The shipped count is the evidence that the feedback was usable rather than forwarded.

Weak

Supported a large number of SMB customers.

Stronger

Covered roughly 140 SMB accounts at 1.1m EUR ARR in a pooled model, with outreach triggered by usage drops rather than a calendar.

Why

Pooled coverage is a real model and worth naming. Claiming 140 named relationships instead would not survive a follow-up question.

Weak

Improved retention in a difficult segment.

Stronger

Held SMB gross retention at 86% through a seasonal cycle by moving renewal conversations to the month after each customer's event season.

Why

A flat number plus the mechanism. In a churn-heavy segment, holding a line is an achievement and should be framed as one.

Weak

Created onboarding documentation.

Stronger

Wrote the mid-market onboarding playbook now used by all six CSMs, which flattened the variance in first-90-day adoption between them.

Why

Adoption by the rest of the team is what separates a document you wrote from a document that mattered.

Skills that belong on this CV

Education and certifications

Customer success takes people from support, sales, account management and the customer's own industry, and no degree route dominates. Keep education to one line after experience. Domain knowledge of the customer's world is worth more space than the degree: if you sold field-service software after five years dispatching technicians, say so, because that is the part of the CV a hiring manager cannot train into someone else.

Certifications

• Vendor certification in your CS platform (Gainsight, Totango, HubSpot) - Worth one line when the advert names the platform, since it removes a ramp-up objection.
• Product or industry certification for the customer's domain - The more useful one. Knowing the customer's workflow beats knowing another dashboard.

No certification is required for a CSM role. Keep them to one line each and never above the book.

How an ATS reads this CV

Appliora's ATS Checker runs 14 checks against an uploaded file and shows the text its parser extracted. Four of them matter most for a customer success CV.

• Bullet quality

  This is the heaviest content check, and CS CVs fail it in one specific way: bullets full of relationship language and empty of figures. "Built strong relationships with key stakeholders" carries no action verb and no number. Put the account count, the ARR, the renewal rate and the save count into the bullets themselves, not only into the summary at the top.

• Accented characters

  Spanish, Portuguese and Central European names and cities carry accents that some export paths turn into question marks or drop entirely, so Guzman, Malaga and Sao Paulo come out mangled in the extracted text. The checker shows you the parsed characters, which is the only way to see it before an employer does. Check your own name first, since that is the field a recruiter searches on.

• Recognised sections

  CS candidates invent headings: "Book of Business", "Portfolio", "Customer Outcomes". A parser looking for Experience, Education and Skills may file everything under the previous heading it recognised. Keep the standard section names and put the book inside the first line of each role, the way the example does.

• Concrete skills

  Skills blocks here fill with soft phrases - relationship building, stakeholder management, empathy - which read as orphan fragments rather than recognisable skills. Twelve concrete items, mixing named platforms with named practices like renewal forecasting and health scoring, score better than thirty abstractions.

Templates that suit this role

• ATS Clean

  Single column, plain headings, plenty of room for a first line of book detail under each job title. The default when you are applying through a SaaS company's portal.

• Commercial

  Built for revenue-facing roles: the layout gives retention and expansion figures visual weight without turning the CV into a dashboard.

• Two Column Pro

  Useful once the tool list and the language list are long enough to crowd the experience column, provided you keep the account and renewal numbers in the main column.

Related roles

• Account Executive
• Sales Manager
• Marketing Manager