AI Success Strategist
Zendesk · Denver Metropolitan Area · 1 mo ago
Business Development$118k–$178k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content.
The posting includes: "Why This Role? Why Now?" maybe as intro. Then "Mission", "Overarching Objective For The Role", "How You’ll Make an Impact", then "Strategic Responsibilities" (list), then "What You’ll Need to Succeed" (list of skills), then "Qualifications" (list), then compensation info (Pay). Also mention hybrid way of working (Schedule? maybe not explicit schedule). Benefits not mentioned. So we should include sections: About the role (maybe from "Why This Role? Why Now?" and Mission etc). Responsibilities (Strategic Responsibilities). Requirements (maybe combine Qualifications and What You'll Need to Succeed? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what to put where. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive info, not invent. Avoid filler like "commensurate with experience". Pay section: we have OTE range $118k-$178k with pay mix 70/30 base/commission. Also mention bonus, benefits, or related incentives. So we can include Pay section with that info.
Schedule: not explicit schedule; maybe hybrid way of working mentioned: "Our hybrid way of working, enables us to purposefully come together in person... 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.
Benefits: not explicitly listed; only mention "bonus, benefits, or related incentives" but not specifics. So we should not create Benefits section because no specific benefits listed.
Skills: we have "What You’ll Need to Succeed Strategic Skills & Expertise" which lists skills. So we can put that under Skills heading.
Requirements: maybe we can put "Qualifications" heading for qualifications list. Requirements could be maybe the "Must have a minimum of 5+ years..." etc. That's qualifications. But we have both Qualifications and Requirements headings. We could treat Qualifications as the list of qualifications (education, experience). Requirements could be the "What You’ll Need to Succeed" (skills). But we already have Skills heading. Hmm.
We need to decide mapping: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; only include when posting has real specific content. So we can choose which headings to use based on content.
We have content for: About the role (intro/mission/objective). Responsibilities (Strategic Responsibilities). Skills (What You’ll Need to Succeed). Qualifications (Qualifications). Pay (compensation). Schedule (hybrid way of working). Possibly Requirements could be omitted if we already covered under Qualifications/Skills. But we could also put Requirements as the "Must have a minimum of 5+ years..." etc. However Qualifications already includes that. To avoid duplication, we could put Requirements as the list of mandatory experience/education, and Qualifications as preferred qualifications (advanced degrees, certifications). But the posting lumps them together. Safer: Use Requirements for the mandatory experience (5+ years, 1+ year AI, previous GTM, etc.) and Qualifications for education/degrees/certifications. Skills for the skill list.
Let's extract:
Mandatory experience:
- 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. (This is education, but could be qualification)
- 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.
That's a mix.
We could separate: Requirements = the experience bullets (5+ years, 1+ year AI, GTM, adoption analytics, managing AI programs, designing success plans, program management skills). Qualifications = education (Bachelor's degree, advanced degrees, certifications). Skills = the skill list (Strategic Skills & Expertise). But the skill list includes many similar items. Might be overlapping.
Given the instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But headings are separate; we could still have both but ensure they have content.
Let's decide:
- About the role: include "Why This Role? Why Now?" paragraph, Mission, Overarching Objective For The Role, How You’ll Make an Impact (maybe summarised). We'll keep prose.
- Responsibilities: the "Strategic Responsibilities" bullet list.
- Requirements: the mandatory experience bullets (5+ years, 1+ year AI, GTM, adoption analytics, managing AI programs, designing success plans, program management skills). We'll list as
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content.
The posting includes: "Why This Role? Why Now?" maybe as intro. Then "Mission", "Overarching Objective For The Role", "How You’ll Make an Impact", then "Strategic Responsibilities" (list), then "What You’ll Need to Succeed" (list of skills), then "Qualifications" (list), then compensation info (Pay). Also mention hybrid way of working (Schedule? maybe not explicit schedule). Benefits not mentioned. So we should include sections: About the role (maybe from "Why This Role? Why Now?" and Mission etc). Responsibilities (Strategic Responsibilities). Requirements (maybe combine Qualifications and What You'll Need to Succeed? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what to put where. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We need to preserve all substantive info, not invent. Avoid filler like "commensurate with experience". Pay section: we have OTE range $118k-$178k with pay mix 70/30 base/commission. Also mention bonus, benefits, or related incentives. So we can include Pay section with that info.
Schedule: not explicit schedule; maybe hybrid way of working mentioned: "Our hybrid way of working, enables us to purposefully come together in person... 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.
Benefits: not explicitly listed; only mention "bonus, benefits, or related incentives" but not specifics. So we should not create Benefits section because no specific benefits listed.
Skills: we have "What You’ll Need to Succeed Strategic Skills & Expertise" which lists skills. So we can put that under Skills heading.
Requirements: maybe we can put "Qualifications" heading for qualifications list. Requirements could be maybe the "Must have a minimum of 5+ years..." etc. That's qualifications. But we have both Qualifications and Requirements headings. We could treat Qualifications as the list of qualifications (education, experience). Requirements could be the "What You’ll Need to Succeed" (skills). But we already have Skills heading. Hmm.
We need to decide mapping: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; only include when posting has real specific content. So we can choose which headings to use based on content.
We have content for: About the role (intro/mission/objective). Responsibilities (Strategic Responsibilities). Skills (What You’ll Need to Succeed). Qualifications (Qualifications). Pay (compensation). Schedule (hybrid way of working). Possibly Requirements could be omitted if we already covered under Qualifications/Skills. But we could also put Requirements as the "Must have a minimum of 5+ years..." etc. However Qualifications already includes that. To avoid duplication, we could put Requirements as the list of mandatory experience/education, and Qualifications as preferred qualifications (advanced degrees, certifications). But the posting lumps them together. Safer: Use Requirements for the mandatory experience (5+ years, 1+ year AI, previous GTM, etc.) and Qualifications for education/degrees/certifications. Skills for the skill list.
Let's extract:
Mandatory experience:
- 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. (This is education, but could be qualification)
- 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.
That's a mix.
We could separate: Requirements = the experience bullets (5+ years, 1+ year AI, GTM, adoption analytics, managing AI programs, designing success plans, program management skills). Qualifications = education (Bachelor's degree, advanced degrees, certifications). Skills = the skill list (Strategic Skills & Expertise). But the skill list includes many similar items. Might be overlapping.
Given the instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But headings are separate; we could still have both but ensure they have content.
Let's decide:
- About the role: include "Why This Role? Why Now?" paragraph, Mission, Overarching Objective For The Role, How You’ll Make an Impact (maybe summarised). We'll keep prose.
- Responsibilities: the "Strategic Responsibilities" bullet list.
- Requirements: the mandatory experience bullets (5+ years, 1+ year AI, GTM, adoption analytics, managing AI programs, designing success plans, program management skills). We'll list as - .
- Qualifications: education bullets (Bachelor's degree in Business, Computer Science, Engineering, or related field; advanced degrees; certifications in AI strategy or project management preferred). Also maybe "Great to have AI Domain Expertise" could be qualification but it's more skill. We'll keep as qualification.
- Skills: the "Strategic Skills & Expertise" list (Project & Program Management, Product and Technical Knowledge, Business & Strategic Acumen, Consultation & Communication, Analytical & Outcome-Focused, Forward-Thinking & Pragmatic, Responsible AI & Compliance). We'll list.
- Pay: compensation info.
- Schedule: hybrid way of working description.
We must not include boilerplate like EEO, legal, etc.
Now produce HTML fragment with
headings and appropriate
or
- . Ensure no extra text outside.
Let's craft.
About the role: combine the intro paragraphs: "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." Then Mission paragraph: "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: maybe combine two bullet sentences? Actually there are three bullet lines under 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". It seems messed up due to missing punctuation. We'll preserve as is but maybe separate into sentences. We'll keep as prose: "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 scale. Own customers’ multi‑year AI roadmap and execute cross‑functional delivery—aligning Product, Services, Sales, and Partners to scale safe, sustainable AI programs. Deliver quantifiable commercial outcomes—protect renewals, grow account expansion, and translate AI adoption into predictable revenue and retention improvements."
How You’ll Make an Impact: we could include as part of About the role or separate? Might be redundant. We'll incorporate into About the role as additional prose.
Now Responsibilities: list each bullet under 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.
Now Requirements (mandatory experience):
- 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.
- 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.
We could also include "Familiarity with emerging AI trends is a plus" but that's a plus, maybe not required. We'll keep as optional maybe under Skills.
Qualifications (education/preferred):
- Bachelor’s degree in Business, Computer Science, Engineering, or related field; advanced degrees; certifications in AI strategy or project management preferred.
- 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
headings and appropriate
or
- . Ensure no extra text outside. Let's craft. About the role: combine the intro paragraphs: "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." Then Mission paragraph: "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: maybe combine two bullet sentences? Actually there are three bullet lines under 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". It seems messed up due to missing punctuation. We'll preserve as is but maybe separate into sentences. We'll keep as prose: "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 scale. Own customers’ multi‑year AI roadmap and execute cross‑functional delivery—aligning Product, Services, Sales, and Partners to scale safe, sustainable AI programs. Deliver quantifiable commercial outcomes—protect renewals, grow account expansion, and translate AI adoption into predictable revenue and retention improvements." How You’ll Make an Impact: we could include as part of About the role or separate? Might be redundant. We'll incorporate into About the role as additional prose. Now Responsibilities: list each bullet under 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. Now Requirements (mandatory experience): - 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. - 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. We could also include "Familiarity with emerging AI trends is a plus" but that's a plus, maybe not required. We'll keep as optional maybe under Skills. Qualifications (education/preferred): - Bachelor’s degree in Business, Computer Science, Engineering, or related field; advanced degrees; certifications in AI strategy or project management preferred. - 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