Jobs · Business Development · Texas

Customer Success Director

Genesys · Texas, United States · 1 mo ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "Click here to view a summary overview of our Benefits." etc. Also remove "What Happens After You Apply", "Stay Connected", "Employee Referral", "About Genesys", "Reasonable Accommodations", equal opportunity employer text, etc. We need to extract substantive content: Summary paragraph(s) about role, Minimum Requirements (list), Desirable Skills (list), Preferred Qualifications (list), Compensation (salary range), Benefits (list). Also maybe "About the role" could be the summary paragraphs. Responsibilities could be derived from Minimum Requirements? Actually Minimum Requirements list seems like responsibilities/duties. Could treat them as Responsibilities. Requirements could be minimum requirements? But we have both Minimum Requirements and Desirable Skills and Preferred Qualifications. We need to map to sections: About the role (summary), Responsibilities (maybe the Minimum Requirements list), Requirements (maybe the Desirable Skills? Actually "Requirements" could be minimum qualifications; but we already used Minimum Requirements as responsibilities. However we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have: - Summary paragraphs: "Be the one building AI-powered experiences where they matter most..." etc. That's about the role. - Minimum Requirements: list of bullet points (starting with "Own a portfolio..."). - Desirable Skills: list (starting with "10 or more years..."). - Preferred Qualifications: list (starting with "Experience working with CCaaS platforms..."). - Compensation: salary range. - Benefits: list. We might not have explicit Schedule info; posting does not mention schedule specifics besides maybe flexible work schedules mentioned under Benefits. But schedule as a separate section only if posting actually states them. It mentions "Flexible work schedules and work from home opportunities" under Benefits. So we could include Schedule section maybe referencing flexible work schedules? But instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible work schedules under Benefits, but not a separate schedule section. Could we still include Schedule? Probably not, because they didn't give a specific schedule like "Full-time, 40 hrs/week". So we should omit Schedule. Pay: we have compensation range, so include Pay. Benefits: we have list, include Benefits. Skills: we have Desirable Skills (maybe treat as Skills). Could also include Preferred Qualifications under Qualifications. Requirements could be Minimum Requirements? But Minimum Requirements are more like responsibilities/duties. However the instruction says: Use
  • for any list of duties/requirements/benefits. So we can put Minimum Requirements under Responsibilities (duties). Requirements could be maybe the Desirable Skills? Actually "Requirements" could be minimum qualifications (like education, years experience). But we have those in Desirable Skills (10+ years experience, Bachelor's degree). However Desirable Skills also includes many other items. Might be better to treat Minimum Requirements as Responsibilities, Desirable Skills as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as a separate section? But we already used Skills heading for something else. Actually we have both Skills and Qualifications headings. Could assign: - About the role: summary paragraphs. - Responsibilities: Minimum Requirements list. - Requirements: Desirable Skills list (maybe focusing on experience/education etc). But Desirable Skills includes many items like "Proven track record of driving revenue growth..." etc. That's more like qualifications/skills. Could be okay. - Qualifications: Preferred Qualifications list. - Skills: maybe we could combine some technical skills? But we don't have a separate skills list besides those already covered. Could omit Skills section if no specific content beyond what's already used. But we need to avoid empty headings. So we should not include Skills if we don't have distinct content. Thus we will include: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other sections like Schedule: not present. Now we need to format as HTML fragment, using

    for each heading, then content: either

    for prose,

    • for lists. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to copy the text exactly as given, but we can format into lists. We must remove boilerplate etc. So we need to extract the relevant paragraphs and bullet points. Let's extract: Summary (About the role): "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 Location: North America Central Region 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." Note: The text includes "Job Title: Customer Success Director Location: North America Central Region Summary:" which we should not repeat job title as heading, but we can keep the location maybe as part of summary? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could include location in a short paragraph maybe. But we already have About the role section; we could include location as part of that paragraph. However the summary already includes "Job Title: Customer Success Director Location: North America Central Region Summary:" which is redundant. We should remove the "Job Title:" and "Location:" maybe keep location as a short sentence. But we must preserve ALL substantive information; location is substantive. So we could include a short

      with location. But we already have About the role heading; we could put a

      that includes the location and the summary. However we must not repeat the job title as a heading; we can still mention job title in prose? The instruction: "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid mentioning job title in prose. So we can keep it. But we should remove the "Job Title: Customer Success Director Location: North America Central Region Summary:" phrase and replace with maybe "Location: North America Central Region". Or we could keep it as is but it's redundant. Safer to remove the "Job Title:" and "Location:" labels and just keep the location as a sentence. Thus About the role 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. Location: North America Central Region. 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." Now Responsibilities: Minimum Requirements list (the bullet points). Let's extract them exactly: - 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 We need to preserve all detail; keep punctuation. Now Requirements: 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 Now Qualifications: 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 Now Benefits: list from posting: - 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 there is a line: "Click here to view a summary overview of our Benefits." which we should remove as it's a link/instruction. Now Pay: compensation range: "$128,700.00 - $226,300.00" plus preceding sentence: "Compensation: 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." We need to preserve all substantive info. So we can include a

      with that sentence and then maybe the range as separate

      or within same. Could do

      Compensation: 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

Similar jobs