Customer Success Manager, Enterprise
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content. We have: - About the role: description of Enterprise Customer Success Manager role, responsibilities list. Could combine responsibilities and about role? But we need separate sections if content exists. We have responsibilities bullet list: many bullet points after "As an Enterprise Customer Success Manager (CSM) you will be a key partner...". Those are responsibilities. We have qualifications: "4-8 years of professional work experience, preferably 3 in a Customer Success role." etc. Also "Prior experience working in a Fortune 500 corporation..." etc. Also "Fluency with AI-driven tools and agentic automation". Also "Proficiency with Microsoft Word..." etc. Also "Prior use of Salesforce..." etc. Also "Ability to travel up to 15%". Also "Position will be based in US headquarters; open to remote US based on experience (must be flexible to cover US client time zones)". Also "We are not able to offer sponsorship for this position." That's maybe a note but could be omitted as boilerplate? It's not EEO but it's a restriction. Might be considered minor metadata; we could fold into a short p or drop. Probably we can include as a note in Requirements? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. This is not job ID but a restriction; still could be minor metadata. We could include in a
under Requirements or Qualifications. We have Pay: "The estimated base salary range for new hires into this role is $85,000-$115,000 annually + bonus depending on factors such as job-related knowledge, relevant experience, and location." That's specific pay info, so we should include Pay section. We have Benefits: "We also offer a competitive benefits package, details of which can be found here." That's vague; not specific details. The instruction: never create Benefits sections unless the posting actually states them. It states there is a competitive benefits package but no details. Is that enough? It says "details of which can be found here." That's not specific content. Likely we should not include Benefits because it's not substantive detail. So skip Benefits. Schedule: Not mentioned. No schedule info. So skip. We also have "Physical Demands" but that's boilerplate; we should remove. We also have "Multiple positions may be filled from this announcement." That's boilerplate; remove. We also have "This job posting is intended to comply with all applicable laws..." boilerplate; remove. Thus sections: About the role (maybe include brief overview), Responsibilities, Requirements (or Qualifications?), Skills, Pay. We need to decide which headings to use. The posting includes experience requirements, qualifications, skills. Could combine Requirements and Qualifications? But we have both headings possible. We need to include sections only when posting has real specific content. It does have experience requirements, qualifications, skills. Could split into Requirements (experience) and Skills (technical). Qualifications maybe overlapping. Let's map: - Experience: "4-8 years of professional work experience, preferably 3 in a Customer Success role." plus "Prior experience working in a Fortune 500 corporation, hospitality, meetings & events technology, or similar enterprise SaaS platforms; experience helping customers to promote adoption of new technologies is preferred." plus "Experience working in or with cross-functional account teams (e.g., Sales, Account Management, Services, Product, Marketing) in a matrixed environment." That's experience/requirements. - Skills: "Fluency with AI-driven tools and agentic automation", "Proficiency with Microsoft Word, Excel, PowerPoint, and Outlook; strong skills in building executive-ready presentations and reporting.", "Prior use of Salesforce or similar CRM, and familiarity with customer success platforms and collaboration tools (e.g., Teams, Zoom, Slack)". Also maybe "Ability to travel up to 15%" is not a skill but a requirement. - Qualifications: maybe same as experience; but we can treat Requirements as experience and Skills as technical skills. Could also have Qualifications heading for education? Not present. Thus we can have sections: About the role (brief description of role and company culture), Responsibilities, Requirements, Skills, Pay. We must not repeat job title as heading. Already not. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, all experience requirements, all skills. We need to format lists with
- . For prose, use
. We need to avoid filler like "commensurate with experience". Not present. Now craft HTML. First, About the role: combine culture and impact description plus role overview. The posting starts with "Our Culture and Impact Cvent is a leading meetings, events, and hospitality technology provider..." That's company overview. Then "AI at Cvent: Leading the Future ..." then "As an Enterprise Customer Success Manager (CSM) you will be a key partner..." That's role overview. So we can put that in About the role section as prose (maybe multiple paragraphs). We'll keep all that content. We must not include boilerplate like "If you’re excited to be part of a team that’s leading the way in AI-powered collaboration, we’d love to meet you." That's part of the AI section; it's substantive? It's more of a call to action but still part of posting. It's not boilerplate; we should keep it. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI section is not boilerplate; it's part of the posting describing culture. So keep. Thus About the role will include: - Our Culture and Impact paragraph(s) - AI at Cvent paragraph(s) - As an Enterprise Customer Success Manager (CSM) you will be a key partner... (the role overview sentence) We'll keep them as
elements. Now Responsibilities: list of bullet points after that sentence. Let's extract them exactly: "Manage a portfolio of enterprise accounts, (10-25), acting as a designated point of contact for customers up to C level for day-to-day engagement and adoption. Create and maintain success plans with clients that define business objectives, success metrics, milestones, and ownership, helping them advance adoption, strategic meeting management, and program maturity. Conduct Customer Success Reviews (CSR/ABR) to assess progress against success plans, highlight impact, and identify opportunities to optimize programs and expand the relationship. Collaborate closely with cross-functional teams to deliver a unified customer experience, support renewals, and identify opportunities such as new use cases, additional departments, or regions showing interest in Cvent. Monitor and analyze user adoption and system usage; build data-driven recommendations and lead joint action plans with customer stakeholders to increase usage, expand use cases, and drive value realization. Use data and AI-driven insights to identify trends, risks, and optimization opportunities across accounts, and translate those insights into clear, actionable recommendations. Identify when customers would benefit from additional or refreshed training and recommend appropriate training paths or re-onboarding working with internal teams to execute. Document and track feature requests and feedback and keep customers informed on roadmap items and newly released capabilities. Contribute to internal process documentation, playbooks, and best practices that elevate the Enterprise Customer Success team’s effectiveness and consistency globally. Serve as the voice of the customer internally, advocating for customer needs, sharing insights and trends with cross-functional partners, and influencing product and program strategy. Additional responsibilities as assigned." We need to keep each as
- . Note the first bullet includes "(10-25)" maybe parentheses; keep. Now Requirements: experience bullets: "4-8 years of professional work experience, preferably 3 in a Customer Success role. Prior experience working in a Fortune 500 corporation, hospitality, meetings & events technology, or similar enterprise SaaS platforms; experience helping customers to promote adoption of new technologies is preferred. Experience working in or with cross-functional account teams (e.g., Sales, Account Management, Services, Product, Marketing) in a matrixed environment. Ability to travel up to 15%. Position will be based in US headquarters; open to remote US based on experience (must be flexible to cover US client time zones). We are not able to offer sponsorship for this position." We could keep these as
- . The last two maybe considered minor metadata but they are specific; we keep.
Now Skills: list:
"Fluency with AI-driven tools and agentic automation
Proficiency with Microsoft Word, Excel, PowerPoint, and Outlook; strong skills in building executive-ready presentations and reporting.
Prior use of Salesforce or similar CRM, and familiarity with customer success platforms and collaboration tools (e.g., Teams, Zoom, Slack)"
We could also include maybe "Ability to travel up to 15%" but that's already in Requirements.
Now Pay: "The estimated base salary range for new hires into this role is $85,000-$115,000 annually + bonus depending on factors such as job-related knowledge, relevant experience, and location."
We'll put as
. Now ensure we don't include Benefits section. Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Pay
...
Make sure no extra whitespace? It's fine. Now craft the About the role paragraphs. Need to preserve all substantive information from culture and impact, AI at Cvent, and role overview. Let's copy text: "Our Culture and Impact Cvent is a leading meetings, events, and hospitality technology provider with more than 6,000+ employees and ~34,000 customers worldwide, including 60% of the Fortune 500. Founded in 1999, Cvent delivers a comprehensive event marketing and management platform for marketers and event professionals and offers software solutions to hotels, special event venues and destinations to help them grow their group/MICE and corporate travel business. Our technology brings millions of people together at events around the world. In short, we’re transforming the meetings and events industry through innovative technology that powers the human connection. Cvent's strength lies in its people, fostering a culture where everyone is encouraged to think like entrepreneurs, taking risks and making decisions confidently. We value diverse perspectives and celebrate differences, working together with colleagues and clients to build strong connections." Then AI section: "AI at Cvent: Leading the Future Are you ready to shape the future of work at the intersection of human expertise and AI innovation? At Cvent, we’re committed to continuous learning and adaptation—AI isn’t just a tool for us, it’s part of our DNA. We’re looking for candidates who are eager to evolve alongside technology. If you love to experiment boldly, share your discoveries, and help define best practices for AI-augmented work, you’ll thrive here. Our team values professionals who thoughtfully integrate AI into their daily work, delivering exceptional results while relying on the human judgment and creativity that drive real innovation. Throughout our interview process, you’ll have the chance to demonstrate how you use AI to learn, iterate, and amplify your impact. If you’re excited