Customer Success Director
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content.
We need to parse the posting.
Key parts:
- Intro paragraph: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day."
- Job Title: Customer Success Director (should not be heading)
- Location: North America Central Region
- Summary: paragraph about owning and elevating, etc.
- Minimum Requirements: list of bullet points (starting with "Own a portfolio..." etc.)
- Desirable Skills: list (starting with "10 or more years..." etc.)
- Preferred Qualifications: list (starting with "Experience working with CCaaS platforms..." etc.)
- Compensation: paragraph about market-competitive salary, range $128,700 - $226,300, mention commission/bonus.
- Benefits: list of benefits (Medical, Dental, Vision Insurance, Telehealth coverage, Flexible work schedules, Development and career growth opportunities, Open Time Off in addition to 10 paid holidays, 401(k) matching program, Adoption Assistance, Fertility treatments). Also mention "Click here to view a summary overview of our Benefits." (maybe we can ignore link). Also later there is a paragraph about "Working at Genesys AI at enterprise scale – Build, support and operate AI-powered technology used by more than 8,000 organizations worldwide. 150+ new AI features were released in the last fiscal year A flexible-first culture – Join a global team of nearly 7,000 employees with flexible ways of working designed to help people do their best work Growth in the AI era – Build future-ready skills through mentorship, learning programs, leadership development and education support Time to recharge and give back – Benefits include paid volunteer time, August Free Fridays, well-being resources and regionally tailored programs for employees and their families Recognized globally – Genesys is Great Place to Work® certified in 17 countries and 94% of employees are proud to tell others they work at Genesys Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." This seems like additional culture/benefits info; could be part of Benefits or maybe a separate section like "About Genesys" but we only have allowed headings. Could incorporate into Benefits or maybe a separate "About the role"? But we have to follow allowed headings only. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we need to map content to those sections.
We have:
- About the role: could include the introductory paragraphs and summary.
- Responsibilities: could be the Minimum Requirements list (these are duties). Or we could treat Minimum Requirements as Responsibilities.
- Requirements: could be Desirable Skills? Or Minimum Requirements as Requirements? The posting has "Minimum Requirements" and "Desirable Skills" and "Preferred Qualifications". We need to decide mapping.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can assign:
- About the role: intro + summary.
- Responsibilities: the Minimum Requirements list (the actions the role will do).
- Requirements: maybe the Desirable Skills (experience, degree, etc.)? Or could be "Requirements" for mandatory qualifications? But Minimum Requirements already captured responsibilities; but they are more like duties. However the posting calls them Minimum Requirements (they are responsibilities). We could treat them as Responsibilities.
- Requirements: maybe the Desirable Skills (these are desired but not mandatory). Could also treat as Requirements.
- Qualifications: maybe the Preferred Qualifications.
- Skills: maybe we could combine Desirable Skills and Preferred Qualifications? But we have separate headings.
We need to avoid duplication and ensure we preserve all substantive info.
Let's extract each piece.
Intro paragraph(s):
Paragraph 1: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day."
Paragraph 2 (Summary): "Own and elevate how Genesys builds long term enterprise customer value by leading strategic partnerships that drive adoption, retention, and expansion across a global portfolio. This role directly influences revenue growth and customer outcomes by shaping how organizations realize the full potential of AI powered customer experience solutions. At Genesys, we enable brands to deliver empathetic, personalized experiences at scale, and this role ensures that vision translates into measurable business impact for our customers. You will act as a trusted advisor to executive stakeholders, guiding transformation strategies while aligning cross functional teams to deliver consistent value throughout the customer lifecycle. This is a highly visible leadership role with influence across revenue, product adoption, and customer advocacy, offering the opportunity to shape enterprise success at scale."
We could combine these into About the role.
Location: "Location: North America Central Region". This is metadata; we could fold into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we need to map content to those sections. We have: - About the role: could include the introductory paragraphs and summary. - Responsibilities: could be the Minimum Requirements list (these are duties). Or we could treat Minimum Requirements as Responsibilities. - Requirements: could be Desirable Skills? Or Minimum Requirements as Requirements? The posting has "Minimum Requirements" and "Desirable Skills" and "Preferred Qualifications". We need to decide mapping. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can assign: - About the role: intro + summary. - Responsibilities: the Minimum Requirements list (the actions the role will do). - Requirements: maybe the Desirable Skills (experience, degree, etc.)? Or could be "Requirements" for mandatory qualifications? But Minimum Requirements already captured responsibilities; but they are more like duties. However the posting calls them Minimum Requirements (they are responsibilities). We could treat them as Responsibilities. - Requirements: maybe the Desirable Skills (these are desired but not mandatory). Could also treat as Requirements. - Qualifications: maybe the Preferred Qualifications. - Skills: maybe we could combine Desirable Skills and Preferred Qualifications? But we have separate headings. We need to avoid duplication and ensure we preserve all substantive info. Let's extract each piece. Intro paragraph(s): Paragraph 1: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day." Paragraph 2 (Summary): "Own and elevate how Genesys builds long term enterprise customer value by leading strategic partnerships that drive adoption, retention, and expansion across a global portfolio. This role directly influences revenue growth and customer outcomes by shaping how organizations realize the full potential of AI powered customer experience solutions. At Genesys, we enable brands to deliver empathetic, personalized experiences at scale, and this role ensures that vision translates into measurable business impact for our customers. You will act as a trusted advisor to executive stakeholders, guiding transformation strategies while aligning cross functional teams to deliver consistent value throughout the customer lifecycle. This is a highly visible leadership role with influence across revenue, product adoption, and customer advocacy, offering the opportunity to shape enterprise success at scale." We could combine these into About the role. Location: "Location: North America Central Region". This is metadata; we could fold into a short
maybe under About the role or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location as a short paragraph maybe after About the role? But we need to preserve all substantive info; location is substantive. We'll include a
with location. Now Minimum Requirements list (these are responsibilities). Let's extract each bullet: - Own a portfolio of enterprise customers, acting as the primary strategic advisor to drive business outcomes and long term value realization - Develop and execute Customer Success Plans that align customer objectives with measurable KPIs and platform adoption strategies - Lead executive engagement through regular business reviews that track progress, demonstrate value, and align on future growth opportunities - Drive adoption and utilization of Genesys solutions to strengthen retention and accelerate expansion across accounts - Identify and advance expansion opportunities by aligning product capabilities to evolving customer business needs - Implement proactive risk mitigation strategies that improve customer health, reduce churn, and protect recurring revenue - Build and scale customer advocacy by increasing reference ability, satisfaction, and Net Promoter Score outcomes - Partner cross functionally with Sales, Professional Services, Renewals, and Onboarding teams to ensure seamless lifecycle execution - Influence territory and account strategies by delivering data driven insights and aligning internal resources to customer priorities - Translate complex technical capabilities into clear business value for executive stakeholders That's 10 items. Desirable Skills list: - 10 or more years of experience in technology, consulting, or enterprise account management roles - Bachelor’s degree in a technology or business related field - Proven track record of driving revenue growth and customer retention within a SaaS environment - Demonstrated experience building and maintaining relationships with C level executives - Strong understanding of customer experience platforms and enterprise SaaS solutions - Proficiency with CRM and customer success tools such as Salesforce and Gainsight - Advanced data analysis skills with the ability to present insights to executive audiences - Strong communication, stakeholder management, and strategic thinking capabilities - Ability to manage complex enterprise customer environments across technical and business dimensions Preferred Qualifications list: - Experience working with CCaaS platforms, ecosystems, and enterprise customer experience strategies - Familiarity with Genesys Cloud platform and related technologies - Experience driving customer transformation initiatives at enterprise scale - Demonstrated thought leadership within the customer experience domain Compensation paragraph: "This role has a market-competitive salary with an anticipated base compensation range listed below. Actual salaries will vary depending on a candidate’s experience, qualifications, skills, and location. This role might also be eligible for a commission or performance-based bonus opportunities. $128,700.00 - $226,300.00" Benefits list: - Medical, Dental, and Vision Insurance. - Telehealth coverage - Flexible work schedules and work from home opportunities - Development and career growth opportunities - Open Time Off in addition to 10 paid holidays - 401(k) matching program - Adoption Assistance - Fertility treatments Also later there is a paragraph about culture etc. Might be considered additional benefits or "About Genesys". Since we have no specific heading for culture, we could incorporate into Benefits or maybe a separate section like "About the role"? But we already used About the role for intro/summary. Could add a paragraph after Benefits about culture etc. But we must not create a section with filler. Could add a
after Benefits describing culture etc. That's allowed as prose. We also have "Click here to view a summary overview of our Benefits." which is a link; we can drop as it's navigation. Also there is "Working at Genesys AI at enterprise scale – Build, support and operate AI-powered technology used by more than 8,000 organizations worldwide. 150+ new AI features were released in the last fiscal year A flexible-first culture – Join a global team of nearly 7,000 employees with flexible ways of working designed to help people do their best work Growth in the AI era – Build future-ready skills through mentorship, learning programs, leadership development and education support Time to recharge and give back – Benefits include paid volunteer time, August Free Fridays, well-being resources and regionally tailored programs for employees and their families Recognized globally – Genesys is Great Place to Work® certified in 17 countries and 94% of employees are proud to tell others they work at Genesys Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." We can treat that as additional prose about company culture; we could put under a heading like "About Genesys" but not allowed. Could incorporate into Benefits or maybe a separate
after Benefits. It's substantive, not boilerplate. So we can add a
after Benefits containing that info (maybe trimmed). Ensure we don't include navigation/link phrases like "Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." That's maybe okay as it's still info but could be considered a link suggestion; but it's not a navigation instruction; it's just a suggestion. Might be okay to keep. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's more marketing. We can keep. Also there is "What Happens After You Apply" etc. That's application instructions; we must remove. Also "Stay Connected" etc. Remove. Also "Employee Referral" etc. Remove. Also "About Genesys:" paragraph after that; we might have already captured some. The "About Genesys:" paragraph: "Genesys® empowers more than 8,000 organizations worldwide to create the best customer and employee experiences. Genesys Cloud™ is the Agentic Orchestration Platform that securely connects