Customer success sits between support and sales, and weak CS resumes read like one or the other — ticket lists or quota claims. A strong one proves the CS-specific skill: keeping revenue that wanted to leave and growing revenue nobody was asking about.

Structure

1. Header + LinkedIn.
2. Two-line summary: "CSM, {{years}} in {{segment}} {{domain}} — portfolio of {{N accounts / ARR under management}}. {{Headline retention or expansion stat}}."
3. Experience — open each role with the book: "{{N}} accounts · {{ARR}} under management · {{segment}} · renewal cycle {{length}}".
4. Then 3–4 bullets across the four CS proof areas below.
5. Tools row: {{CS platform, CRM, analytics}}.

The four proof areas (cover all four across your roles)

One save story, told properly

Pick your best save and give it a two-line bullet with the full arc: risk signal → diagnosis → intervention → renewed outcome. Interviewers ask for exactly this; putting it on the resume chooses the story they'll ask about.

Common traps

• Claiming NRR without a book size — every percentage needs its denominator.
• Activity metrics (QBRs held, calls made) without consequences — pair or drop them.
• Reading like support: if most bullets are reactive, rewrite toward the revenue outcomes your responsiveness protected.