AI Success Strategist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the job description and extract content for each relevant heading. Let's identify sections: - About the role: The initial paragraphs: "Why This Role? Why Now? Customer experience is transforming through AI-driven innovation..." etc. Also "Mission", "Overarching Objective For The Role". Could be considered about the role. - Responsibilities: The "How You’ll Make an Impact Strategic Responsibilities" bullet list. - Requirements: maybe "What You’ll Need to Succeed Strategic Skills & Expertise" includes skills. Also "Qualifications" separate. - Skills: maybe the bullet list under "What You’ll Need to Succeed Strategic Skills & Expertise" includes skills. - Qualifications: The "Qualifications" bullet list. - Benefits: Not explicitly listed; there is mention of "benefits" in compensation line: "This position may also be eligible for bonus, benefits, or related incentives." But no specific benefits described. So we should not create Benefits section because no specific content. - Pay: The US annualized OTE range is given: "$118,000.00-$178,000.00 with a pay mix of 70/30 (base/commission)." Also mention bonus etc. So we have pay info. Should include Pay section. - Schedule: Not mentioned; maybe hybrid way of working described later: "Our hybrid way of working, enables us to purposefully come together in person, at one of our many Zendesk offices around the world, to connect, collaborate and learn whilst also giving our people the flexibility to work remotely for part of the week." That's schedule info (hybrid). So we can include Schedule section with that description. We must not include boilerplate like EEO, equal opportunity, scam warning, etc. Also remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format into

or

• . Must not repeat job title. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Possibly also "Benefits" omitted. We need to ensure we don't create sections with placeholder text like "commensurate with experience". Not present. Now extract content. About the role: Combine the initial paragraphs up to before "How You’ll Make an Impact". Let's capture: "Why This Role? Why Now? Customer experience is transforming through AI-driven innovation. At Zendesk, we don’t just embrace this change — we lead it. As visionary architects of our AI-powered Resolution Platform, AI Success Strategists shape and deliver long-term AI success for our customers. This role transcends technical deployment; it is about owning the strategic AI roadmap, maximizing business impact, and builds executive partnerships from day one so AI initiatives start strong and scale predictably. Mission You will own end-to-end delivery of customers’ AI roadmaps: translating product capabilities into clear business strategies, defining a long-term AI vision, aligning internal and external teams, and driving execution from initial adoption through sustained expansion. Your success is measured by high customer satisfaction, increased automated resolution usage, and improved retention—while orchestrating the right mix of product, services, and partner resources. You will lead structured discovery and success-planning engagements that create measurable playbooks and milestones early in the lifecycle. Overarching Objective For The Role Accelerate customers’ time‑to‑value by driving adoption and operational excellence for Zendesk AI solutions, ensuring customers realize measurable business impact from initial deployment through scaleOwn customers’ multi‑year AI roadmap and execute cross‑functional delivery—aligning Product, Services, Sales, and Partners to scale safe, sustainable AI programsDeliver quantifiable commercial outcomes—protect renewals, grow account expansion, and translate AI adoption into predictable revenue and retention improvements" Note there is a missing space after "scaleOwn". We'll keep as is. We'll put that in

  maybe multiple paragraphs. Responsibilities: The bullet list under "How You’ll Make an Impact Strategic Responsibilities". Let's extract each bullet: - Full Ownership of AI Roadmap Delivery: Lead the design, planning, and execution of comprehensive AI adoption and expansion roadmaps for key customers, ensuring alignment to their broader business goals and customer success vision. - Design Authority: Serve as the design authority for customers’ AI deployments — lead solution design reviews, ensure deployments align with the latest best practices and collaborate with Professional Services on integration and configuration guidance. For complex agent implementations, coordinate troubleshooting and technical escalations with Professional Services, Product and Engineering to resolve blockers quickly. - Long-term AI Vision & Business Strategy: Partner with executive stakeholders to co-create and refine a forward-looking AI strategy that anticipates market trends and customer needs. Serve as the primary AI thought leader and trusted advisor throughout the engagement lifecycle. - Internal and External Stakeholder Alignment: Dedicate effort to internal cross-functional collaboration, aligning Product, Professional Services, Sales, Success, and other teams to deliver on the AI roadmap. Serve as the Engagement Lead: Coordinate and sequence activities, identify and escalate risks early, and ensure the right technical, product, and services resources are engaged at the appropriate times. - Sustain Engagement & Mutual AI Roadmap: Maintain recurring outcome-driven cadences and mutual AI Roadmap that define strategic goals, shared initiatives, measurable success, and a roadmap to maximize value and secure renewal. - Channel & Adoption Strategy: Own the channel strategy for AI solution dissemination and adoption, balancing direct customer delivery with channel enablement and partner engagement. - Measure and Drive Impact: Utilize data-driven insights to track AI adoption, resolution metrics, and gross revenue retention improvements. Continuously refine strategies to optimize outcomes and customer satisfaction. We need to ensure we keep the exact phrasing. Now Requirements vs Skills vs Qualifications. The section "What You’ll Need to Succeed Strategic Skills & Expertise" lists bullet points: - Project & Program Management: Proven ability to orchestrate multi-phase technology adoption projects, managing diverse teams and timelines with clarity and agility. - Product and Technical Knowledge: Product expert who assesses customers' use case automation potential and technical readiness (generative AI, integrations, authentication), helps craft user journeys and translates features into value. Liaise with ProdDev teams to remove blockers for adoption, implement fixes and provide feedback on (beta) features. - Business & Strategic Acumen: Demonstrated skill in aligning AI solutions to customer business challenges, driving revenue growth, and influencing executive decision-making. - Consultation & Communication: Strong stakeholder engagement skills—whether customer executives or internal teams—to advance AI adoption and sustain strategic partnerships. - Analytical & Outcome-Focused: Strong analytical capacity to interpret adoption data, develop predictive health scores, forecast retention/expansion, and translate metrics into prioritized action plans. - Forward-Thinking & Pragmatic: Visionary in embracing AI’s potential with a grounded, realistic approach to execution—balancing innovation with practical delivery feasibility. - Responsible AI & Compliance: Confidently advise customers on ethical AI practices, data governance, and compliance considerations — framing use cases within safe, explainable, and policy‑aligned guardrails These could be considered Skills. Then "Qualifications" bullet list: - Must have a minimum of 5+ years of related experience in Customer Success / Experience, 1+ years of AI related experience - Previous experience in go-to-customer/GTM roles in enterprise technology / SaaS — either customer success management, professional services/consulting, technical account management, or solutions engineering/pre-sales consulting - Demonstrated experience in using adoption and health analytics to forecast churn and expansion; surface early risk signals and recommended mitigations to secure retention and growth. - Bachelor’s degree in Business, Computer Science, Engineering, or related field; advanced degrees; certifications in AI strategy or project management preferred. - Experience managing AI or software adoption programs with demonstrated impact on business metrics such as retention or satisfaction. - Demonstrated experience designing and executing success plans or roadmaps that drive measurable customer outcomes - Excellent program management and cross-functional influence skills. - Familiarity with emerging AI trends is a plus - Ability to distill complex AI concepts for diverse audiences, especially executive stakeholders. - Great to have AI Domain Expertise: Deep understanding of AI capabilities within Zendesk’s platform, not necessarily hands-on technical, but sufficient to translate product features into business value and strategic initiatives. We need to decide what goes under Requirements vs Qualifications. The instruction says use headings: Requirements, Qualifications, Skills. We can allocate: - Requirements: maybe the mandatory qualifications (like years experience, degree, etc.) but we have to follow the posting's sections. The posting has "What You’ll Need to Succeed Strategic Skills & Expertise" (skills) and "Qualifications". So we can map: Skills: the bullet list under "What You’ll Need to Succeed Strategic Skills & Expertise". Qualifications: the bullet list under "Qualifications". Requirements: maybe we could combine some overlapping? But we have no explicit "Requirements" section besides qualifications. However we could treat "Qualifications" as Requirements? But we need both headings if content exists. Since there is a separate "Qualifications" heading in the posting, we should use that. For "Requirements", we might not have distinct content; but we could consider the "Must have a minimum of 5+ years..." as requirements. However that is part of Qualifications list. To avoid duplication, we could put all qualification bullets under Requirements, and leave Qualifications empty? But we must not create a heading with filler. Better to treat the "Qualifications" list as Qualifications, and maybe treat the "What You’ll Need to Succeed Strategic Skills & Expertise" as Skills. For Requirements, we could maybe include the "Must have a minimum of 5+ years..." etc. but that duplicates. Perhaps we can treat the "Qualifications" list as Requirements, and not have a Qualifications section. But the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must use all; we include only when posting has real specific content. So we can include Requirements if there is content distinct from Qualifications and Skills. The posting does not have a separate "Requirements" heading; but we could interpret the "Qualifications" as Requirements. However there is also a "Qualifications" heading in the posting. So we have both. To avoid duplication, we could assign: - Requirements: the "Must have a minimum of 5+ years..." etc (the first few bullets maybe). But that's arbitrary. Better approach: Since the posting explicitly has a "Qualifications" section, we will use that heading for Qualifications. For Requirements, we could use the "What You’ll Need to Succeed Strategic Skills & Expertise" as Requirements? But that is more about skills. However the heading "Skills" exists; we could put that there. So we need to decide mapping: Option: Requirements: the bullet list under "What You’ll Need to Succeed Strategic Skills & Expertise" (these are skills/expertise). Skills: maybe we could treat the same list as Skills, but then we would have duplicate. Not good. Alternative: Use Requirements for the mandatory qualifications (like years experience, degree, etc.) and Qualifications for the preferred qualifications (advanced degrees, certifications, etc.). But the posting does not separate them. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section, but we must use headings only when there is real specific content. We could choose to include only Qualifications (since it's explicit) and omit Requirements. Similarly, we could include Skills from the "What You’ll Need to Succeed..." section. Thus final sections: About the role, Responsibilities, Skills, Qualifications, Pay, Schedule. We must not include Benefits (no specific content). We'll not include Requirements. Now we need to