A customer success manager job description should be one of the clearest role pages in a SaaS company. Customer success sits close to retention, adoption, customer value, onboarding, expansion, product feedback, and commercial renewal. Yet many CSM job descriptions still rely on generic language about building relationships and ensuring customer satisfaction.
Those words are not wrong, but they are not enough. Customer success roles differ heavily by company stage, customer segment, product complexity, and revenue model. A CSM supporting high-volume SMB customers is doing different work from a CSM owning strategic enterprise accounts. A CSM responsible for renewals needs a different profile from a CSM focused mainly on adoption and enablement.
A strong customer success manager job description makes these differences clear. It helps candidates understand the customer base, the work, the commercial expectations, and the support model. It also helps hiring teams avoid attracting applicants who like the title but do not fit the role’s realities.
“Customer success roles can look similar from the outside, but the reality depends on book size, renewal ownership, product complexity, and customer maturity. The job description has to make those differences visible.”
Will Steward, Founder & CEO, The SaaS Jobs
For broader role-page guidance, read our article on how to write a job description that attracts better candidates. This guide focuses on SaaS customer success roles.
Start with the customer context
A CSM candidate needs to know who the customers are. Are they SMB, mid-market, enterprise, strategic accounts, public sector, healthcare, financial services, ecommerce, software companies, or another segment? Are users technical, operational, commercial, executive, or a blend?
The customer segment changes the role. SMB success may require scalable engagement, automation, and efficient prioritisation. Enterprise success may require stakeholder mapping, executive communication, commercial judgement, and complex implementation awareness.
Explain the customer base early in the job description. If your company serves multiple segments, say which segment the role will focus on. If the customer profile is changing, explain what is changing and why the hire matters now.
Clarify the book of business
One of the most useful details in a CSM job description is the book of business. Candidates want to understand account volume, account size, revenue responsibility, and whether the role is high-touch, low-touch, digital-led, or hybrid.
You do not need to publish every commercial number, but you should provide a practical sense of the workload. A CSM managing thirty strategic accounts is very different from a CSM supporting hundreds of smaller accounts through scalable programmes.
If book size is still being defined, say so. Ambiguity is normal in scaling SaaS companies, but candidates need to know whether the role is designed around deep account management, scalable success operations, or a mix of both.
Define renewal and expansion ownership
Customer success roles vary significantly in commercial ownership. Some CSMs own renewals. Some influence renewals but work with account managers. Some own expansion. Some identify expansion opportunities but hand them to sales. Some are measured mostly on adoption and customer health.
The job description should explain this clearly. If the role includes commercial responsibility, include it in the summary and responsibilities. If it does not, avoid implying that the CSM owns revenue outcomes they cannot directly control.
This clarity matters because candidates assess whether the role aligns with their strengths. Some CSMs enjoy commercial ownership. Others prefer adoption, enablement, product feedback, and customer value work. Neither profile is inherently better, but the job description should attract the right one.
Explain the product and implementation context
Customer success work depends heavily on product complexity. A simple self-serve product creates different success needs from a deeply integrated workflow platform. A product with heavy onboarding, data migration, compliance, or configuration requires a CSM who can manage complexity and coordinate with implementation or support teams.
Include product context in the description. What does successful adoption involve? Do customers need training, process change, technical setup, integrations, data quality, stakeholder alignment, or executive sponsorship?
This helps candidates understand the work and gives the hiring team a stronger filter for relevant experience. It also helps avoid attracting candidates who expect relationship management but not implementation complexity.
Write responsibilities around customer outcomes
Many CSM job descriptions say the person will build relationships, manage accounts, and ensure satisfaction. Stronger descriptions explain the customer outcomes the role supports.
Responsibilities might include leading onboarding or adoption plans, building relationships with users and executive stakeholders, monitoring customer health, identifying renewal risk, running business reviews, coordinating with support and product, spotting expansion opportunities, and turning repeated customer feedback into useful internal insight.
This kind of responsibility list is more useful because it describes how the CSM creates value. It also helps candidates understand the balance between reactive customer management and proactive success planning.
Include the metrics that matter
Customer success candidates will look for the metrics attached to the role. These may include retention, gross revenue retention, net revenue retention, renewal rate, product adoption, onboarding completion, customer health, expansion influence, support escalation reduction, or customer satisfaction.
Be careful with accountability. If the CSM influences retention but account managers own renewals, explain the split. If adoption is the main focus, say which adoption signals matter. If customer health scoring is still developing, describe how the team currently identifies risk.
Clear metrics support better hiring and better performance management. They also connect to talent acquisition strategy because the role requirements should match the outcomes the company cares about.
Separate essential skills from useful experience
Essential skills may include customer communication, account planning, problem solving, prioritisation, commercial awareness, stakeholder management, and the ability to explain product value clearly. For more complex products, technical curiosity or implementation experience may be important.
Useful experience might include SaaS customer success, working with a similar customer segment, renewal ownership, change management, product analytics, CRM or CS platform familiarity, or experience partnering with sales and product teams.
Avoid requiring every tool and every background detail unless it is genuinely necessary. A candidate who has managed complex customers well may learn a new CS platform quickly. A candidate with the right tool experience but weak customer judgement may not succeed.
Explain the team and support model
CSM candidates need to know who supports them. Is there an implementation team, dedicated support, account management, sales engineering, customer operations, or product support? If the CSM is expected to handle everything from onboarding to support escalations to renewal conversations, say so.
Support model affects workload and fit. A high-autonomy role can be attractive, but only if candidates understand the reality. If the function is still being built, be explicit about the opportunity to shape process.
Show what success looks like
A strong customer success manager job description should include practical first-six-month outcomes. The CSM may have improved onboarding consistency, built account plans for key customers, reduced renewal risk through earlier intervention, improved customer health visibility, or created stronger feedback loops with product.
These outcomes help candidates visualise the role. They also make interviews more practical because the hiring team can ask candidates how they would approach those situations and what they would prioritise first.
Build the interview process around real scenarios
Customer success interviews should test the work the person will actually do. If the role requires renewal ownership, ask about commercial risk and negotiation. If it requires adoption improvement, ask how the candidate identifies usage problems. If the role is enterprise-heavy, test stakeholder mapping and executive communication.
This alignment matters because many CSM candidates can speak broadly about customer relationships. The hiring team needs to understand whether they can operate in your specific SaaS environment.
Connect the job description to candidate relevance
Customer success roles often attract broad applicant pools because many people like the sound of relationship-led work. That can create screening volume if the role is not clearly scoped and distributed to the right audience.
A specific job description helps, but distribution still matters. If you are hiring customer success roles for a SaaS company, specialist distribution can help you reach candidates already interested in SaaS companies, recurring revenue models, adoption work, and customer value. Our article on where to advertise SaaS jobs explains the channel strategy behind that.
Final checklist
Before publishing a customer success manager job description, check that it answers these questions: which customer segment will the CSM support, what is the approximate book of business, does the role own renewals or expansion, how complex is adoption, which metrics matter, what support exists, and what does success look like after six to twelve months?
A clear CSM job description helps attract candidates who understand the post-sale reality of SaaS. If your team is hiring recurring SaaS roles, The SaaS Jobs can help you promote those roles to a more relevant SaaS candidate audience. Review employer packages at The SaaS Jobs pricing page.
