VP, Technology Partnerships
for each section heading. Use - for lists. Use
for prose.
We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: DEIB, fraud disclaimer, etc. Also remove "Our Commitment to Diversity..." and fraud disclaimer. Also remove "Supported by operating principles..." maybe part of About the role? It's about culture; could be included in About the role. But we need to preserve substantive info; but we can keep it as part of About the role.
We must not create sections with filler like "commensurate with experience". Not needed.
Thus sections:
- About the role: include introductory paragraphs describing Anaplan, role overview, impact.
- Responsibilities: list of duties from "Job Requirements & Core Responsibilities" maybe split into responsibilities and requirements. But we need both sections if content exists. The posting has "Job Requirements & Core Responsibilities" which includes both responsibilities and requirements. We could split: Responsibilities: the bullet points under that heading (Strategy & Technology Partnership Development, GTM Translation..., Team Building & Performance Leadership). Requirements: the "Profile of the Ideal Candidate" and "Required Skills and Experience" plus "Preferred Experience". Also "Key Metrics for Success" maybe could be under Responsibilities? But it's evaluation metrics; could be under Responsibilities or a separate section? Not specified headings; we could put under Responsibilities as part of duties? But better to put under Requirements? Actually metrics are for success evaluation; could be under Responsibilities? Might be considered part of role expectations. We'll include a section "Key Metrics for Success" maybe as its own heading? Not in allowed list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those. Qualifications and Skills could be used for required skills etc. We'll decide:
- About the role: intro.
- Responsibilities: the bullet points under "Job Requirements & Core Responsibilities" (Strategy & Technology Partnership Development, GTM Translation & Cross-Functional Alignment, Team Building & Performance Leadership). Also maybe "Key Metrics for Success" could be considered responsibilities? But it's evaluation; maybe put under Responsibilities as a list.
- Requirements: "Profile of the Ideal Candidate" paragraph.
- Skills: "Required Skills and Experience" bullet list.
- Qualifications: maybe "Preferred Experience" bullet list.
- Pay: Base Salary Range.
- Benefits: none -> omit.
- Schedule: none -> omit.
We must not create empty sections.
Now format.
We need to preserve all substantive info; not invent or summarize away detail. Must keep details like specific CSPs, platforms, etc.
Let's extract text.
About the role: combine first paragraphs up to "Insight on Your Impact". Actually the posting starts: "At Anaplan, we are a team of innovators...". Then description of culture, customers, winning culture. Then "Anaplan is looking for an entrepreneurial and highly strategic VP, Technology Partnerships. This is a stellar opportunity...". Then "Insight on Your ImpactThis role serves as the strategic leader...". We'll combine into About the role.
We'll need to ensure we don't repeat job title as heading; fine.
Now Responsibilities: list items:
From "Job Requirements & Core Responsibilities":
- Strategy & Technology Partnership Development
- Ecosystem Vision: Define, build, and execute the strategic roadmap for next-generation technology partnerships, including Cloud Service Providers (CSPs such as AWS, GCP, Azure), Data Cloud/AI platforms (such as Snowflake, Databricks), and strategic enterprise ISVs.
- Tip of the Spear Execution: Identify emerging technological trends—particularly in Data Cloud, AI, and enterprise planning architectures—to design, incubate, and pilot joint technology partner initiatives. Ensure the organization adapts quickly to market shifts and customer requirements.
- Partner Apps Program Leadership: Lead the end-to-end strategy, governance, technical enablement, and commercial execution of Anaplan’s Partner Apps program to accelerate platform extensibility, marketplace growth, and new recurring revenue streams.
- Joint Solution Innovation: Partner with technology partners' product and engineering teams to identify high-value integration use cases, co-create architectural blueprints, and bring differentiated joint solutions to market.
- GTM Translation & Cross-Functional Alignment
- GTM Integration & Scalability: Translate technical integrations and strategic alliance agreements into structured, repeatable GTM plays that can be adopted and executed by regional partner sales and direct sales teams.
- "Power of 3" Orchestration: Curate and champion high-impact "Power of 3" motions, aligning Anaplan, Cloud/Data technology partners, and Global Systems Integrators (GSIs/SIs) to deliver complete, market-leading industry solutions.
- Cross-Functional Collaboration: Partner closely with Product Management, Engineering, Marketing, Alliances, and Regional Theater Leaders (AMER, EMEA, APAC) to ensure seamless technical roadmap alignment and commercial throughput of technology partnership plays.
- Team Building & Performance Leadership
- Global Team Build-Out: Take full accountability for designing the organizational structure, hiring, and mentoring a world-class team of technology partner directors, alliance managers, and partner app specialists.
- Accountability & Execution: Move seamlessly between high-level strategic alliance design and hands-on operational execution. Foster a high-performance culture that manages partner milestones strictly to plan and continuously measures partner-sourced and partner-influenced impact.
- Ecosystem Evangelism: Serve as a prominent executive sponsor and thought leader for Anaplan’s technology alliances and Partner Apps ecosystem, representing Anaplan at industry conferences, partner summits, and executive advisory boards.
Also Key Metrics for Success: list:
- Partner-Driven & Influenced ACV: Net-new annual contract value (ACV) sourced and influenced through technology partnerships and tripartite "Power of 3" plays.
- Partner Apps Program Expansion: Growth in active partner apps, developer adoption, customer installations, and attributable revenue generated via the Partner Apps program.
- Strategic Alliances Formalized: Successful initiation, contractual execution, and executive launch of tier-1 technology, cloud, and data alliances.
- Joint Solutions Delivered: Number of certified, customer-facing technical integrations and joint solution briefs successfully launched to the market.
- Field Enablement & Velocity: Successful operationalization and enablement of regional partner sales teams to execute technology partner plays across AMER, EMEA, and APAC.
We could include these under Responsibilities as well (they are metrics of success). Or maybe under Requirements? But they are evaluation metrics; we can put under Responsibilities as a subsection "Key Metrics for Success". Since we only have headings allowed, we can still include a
for "Key Metrics for Success"? Not allowed. But we could embed them under Responsibilities as a list. That's fine.
Now Requirements: "Profile of the Ideal Candidate" paragraph: "The ideal candidate is an agile, strategic executive with deep credibility across the enterprise software ecosystem and strong technical acumen. You are energized by ambiguity, possess an entrepreneurial mindset, and have a proven track record of establishing high-impact technology partnerships and commercializing platform application ecosystems."
We'll put that as
.
Skills: "Required Skills and Experience" bullet list:
- Tech Ecosystem Leadership: Deep, verifiable experience identifying, structuring, and expanding strategic partnerships with ISVs, Data Cloud/AI platforms (e.g., Snowflake, Databricks), and major Cloud Service Providers (AWS, Azure, GCP).
- Partner Apps & Platform Extensibility: Proven success establishing, scaling, or commercializing a Partner Apps program, ISV marketplace, or platform extension ecosystem.
- Incubation to Revenue: Demonstrated track record of converting technical product integrations into active, revenue-generating GTM motions that deliver measurable ACV.
- Executive Presence & Influence: Outstanding communication, negotiation, and relationship-building capabilities, with demonstrated success influencing C-suite executives and product leaders both internally and externally.
- Technical Acumen: Strong understanding of enterprise SaaS architectures, APIs, data pipelines, and cloud platform topologies to credibly lead joint solution development with product and engineering counterparts.
- Team Building & People Leadership: Extensive experience building, leading, and mentoring high-performing global alliance teams, with clear accountability for execution and pipeline results.
Qualifications: "Preferred Experience" bullet list:
- SI & "Power of Three" Collaboration: Strong familiarity with Global System Integrators (GSIs) and proven experience curating tripartite ("Power of 3") motions combining technology partners, SIs, and software platforms to win large enterprise transformations.
- Hyper-Growth SaaS Track Record: 10+ years of progressive leadership in technology alliances, strategic business development, or partner ecosystems within high-growth enterprise software companies.
Pay: Base Salary Range:: $271,000 USD - $366,000 USD (note double colon). We'll output as "$271,000 USD - $366,000 USD".
Now ensure we don't include boilerplate: DEIB, fraud disclaimer, etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... maybe we need subheadings? But we can just list each responsibility as
- with internal detail. Could also nest
but spec says use - for any list of duties/requirements/benefits. So we can have top-level
with each duty as - . Inside
- we can have further detail as sentences.
We'll produce
- Strategy & Technology Partnership Development: ...
etc.
Similarly for GTM..., Team Building...
Then after those, we can add another for Key Metrics? But spec says use - for any list of duties/requirements/benefits. Metrics could be considered duties? We'll just add another
under Responsibilities for metrics.
Better to keep one for responsibilities and another for metrics? But both are lists; we can have two separate sections under same heading. That's fine.
Now Requirements: Requirements
...
Skills: Skills
...
Qualifications: Qualifications
...
Pay: Pay
$271,000 USD - $366,000 USD
Make sure no extra whitespace? It's fine.
Now craft the About the role paragraph: combine:
"At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture
for prose. We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: DEIB, fraud disclaimer, etc. Also remove "Our Commitment to Diversity..." and fraud disclaimer. Also remove "Supported by operating principles..." maybe part of About the role? It's about culture; could be included in About the role. But we need to preserve substantive info; but we can keep it as part of About the role. We must not create sections with filler like "commensurate with experience". Not needed. Thus sections: - About the role: include introductory paragraphs describing Anaplan, role overview, impact. - Responsibilities: list of duties from "Job Requirements & Core Responsibilities" maybe split into responsibilities and requirements. But we need both sections if content exists. The posting has "Job Requirements & Core Responsibilities" which includes both responsibilities and requirements. We could split: Responsibilities: the bullet points under that heading (Strategy & Technology Partnership Development, GTM Translation..., Team Building & Performance Leadership). Requirements: the "Profile of the Ideal Candidate" and "Required Skills and Experience" plus "Preferred Experience". Also "Key Metrics for Success" maybe could be under Responsibilities? But it's evaluation metrics; could be under Responsibilities or a separate section? Not specified headings; we could put under Responsibilities as part of duties? But better to put under Requirements? Actually metrics are for success evaluation; could be under Responsibilities? Might be considered part of role expectations. We'll include a section "Key Metrics for Success" maybe as its own heading? Not in allowed list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those. Qualifications and Skills could be used for required skills etc. We'll decide: - About the role: intro. - Responsibilities: the bullet points under "Job Requirements & Core Responsibilities" (Strategy & Technology Partnership Development, GTM Translation & Cross-Functional Alignment, Team Building & Performance Leadership). Also maybe "Key Metrics for Success" could be considered responsibilities? But it's evaluation; maybe put under Responsibilities as a list. - Requirements: "Profile of the Ideal Candidate" paragraph. - Skills: "Required Skills and Experience" bullet list. - Qualifications: maybe "Preferred Experience" bullet list. - Pay: Base Salary Range. - Benefits: none -> omit. - Schedule: none -> omit. We must not create empty sections. Now format. We need to preserve all substantive info; not invent or summarize away detail. Must keep details like specific CSPs, platforms, etc. Let's extract text. About the role: combine first paragraphs up to "Insight on Your Impact". Actually the posting starts: "At Anaplan, we are a team of innovators...". Then description of culture, customers, winning culture. Then "Anaplan is looking for an entrepreneurial and highly strategic VP, Technology Partnerships. This is a stellar opportunity...". Then "Insight on Your ImpactThis role serves as the strategic leader...". We'll combine into About the role. We'll need to ensure we don't repeat job title as heading; fine. Now Responsibilities: list items: From "Job Requirements & Core Responsibilities": - Strategy & Technology Partnership Development - Ecosystem Vision: Define, build, and execute the strategic roadmap for next-generation technology partnerships, including Cloud Service Providers (CSPs such as AWS, GCP, Azure), Data Cloud/AI platforms (such as Snowflake, Databricks), and strategic enterprise ISVs. - Tip of the Spear Execution: Identify emerging technological trends—particularly in Data Cloud, AI, and enterprise planning architectures—to design, incubate, and pilot joint technology partner initiatives. Ensure the organization adapts quickly to market shifts and customer requirements. - Partner Apps Program Leadership: Lead the end-to-end strategy, governance, technical enablement, and commercial execution of Anaplan’s Partner Apps program to accelerate platform extensibility, marketplace growth, and new recurring revenue streams. - Joint Solution Innovation: Partner with technology partners' product and engineering teams to identify high-value integration use cases, co-create architectural blueprints, and bring differentiated joint solutions to market. - GTM Translation & Cross-Functional Alignment - GTM Integration & Scalability: Translate technical integrations and strategic alliance agreements into structured, repeatable GTM plays that can be adopted and executed by regional partner sales and direct sales teams. - "Power of 3" Orchestration: Curate and champion high-impact "Power of 3" motions, aligning Anaplan, Cloud/Data technology partners, and Global Systems Integrators (GSIs/SIs) to deliver complete, market-leading industry solutions. - Cross-Functional Collaboration: Partner closely with Product Management, Engineering, Marketing, Alliances, and Regional Theater Leaders (AMER, EMEA, APAC) to ensure seamless technical roadmap alignment and commercial throughput of technology partnership plays. - Team Building & Performance Leadership - Global Team Build-Out: Take full accountability for designing the organizational structure, hiring, and mentoring a world-class team of technology partner directors, alliance managers, and partner app specialists. - Accountability & Execution: Move seamlessly between high-level strategic alliance design and hands-on operational execution. Foster a high-performance culture that manages partner milestones strictly to plan and continuously measures partner-sourced and partner-influenced impact. - Ecosystem Evangelism: Serve as a prominent executive sponsor and thought leader for Anaplan’s technology alliances and Partner Apps ecosystem, representing Anaplan at industry conferences, partner summits, and executive advisory boards. Also Key Metrics for Success: list: - Partner-Driven & Influenced ACV: Net-new annual contract value (ACV) sourced and influenced through technology partnerships and tripartite "Power of 3" plays. - Partner Apps Program Expansion: Growth in active partner apps, developer adoption, customer installations, and attributable revenue generated via the Partner Apps program. - Strategic Alliances Formalized: Successful initiation, contractual execution, and executive launch of tier-1 technology, cloud, and data alliances. - Joint Solutions Delivered: Number of certified, customer-facing technical integrations and joint solution briefs successfully launched to the market. - Field Enablement & Velocity: Successful operationalization and enablement of regional partner sales teams to execute technology partner plays across AMER, EMEA, and APAC. We could include these under Responsibilities as well (they are metrics of success). Or maybe under Requirements? But they are evaluation metrics; we can put under Responsibilities as a subsection "Key Metrics for Success". Since we only have headings allowed, we can still include a
for "Key Metrics for Success"? Not allowed. But we could embed them under Responsibilities as a list. That's fine. Now Requirements: "Profile of the Ideal Candidate" paragraph: "The ideal candidate is an agile, strategic executive with deep credibility across the enterprise software ecosystem and strong technical acumen. You are energized by ambiguity, possess an entrepreneurial mindset, and have a proven track record of establishing high-impact technology partnerships and commercializing platform application ecosystems." We'll put that as
. Skills: "Required Skills and Experience" bullet list: - Tech Ecosystem Leadership: Deep, verifiable experience identifying, structuring, and expanding strategic partnerships with ISVs, Data Cloud/AI platforms (e.g., Snowflake, Databricks), and major Cloud Service Providers (AWS, Azure, GCP). - Partner Apps & Platform Extensibility: Proven success establishing, scaling, or commercializing a Partner Apps program, ISV marketplace, or platform extension ecosystem. - Incubation to Revenue: Demonstrated track record of converting technical product integrations into active, revenue-generating GTM motions that deliver measurable ACV. - Executive Presence & Influence: Outstanding communication, negotiation, and relationship-building capabilities, with demonstrated success influencing C-suite executives and product leaders both internally and externally. - Technical Acumen: Strong understanding of enterprise SaaS architectures, APIs, data pipelines, and cloud platform topologies to credibly lead joint solution development with product and engineering counterparts. - Team Building & People Leadership: Extensive experience building, leading, and mentoring high-performing global alliance teams, with clear accountability for execution and pipeline results. Qualifications: "Preferred Experience" bullet list: - SI & "Power of Three" Collaboration: Strong familiarity with Global System Integrators (GSIs) and proven experience curating tripartite ("Power of 3") motions combining technology partners, SIs, and software platforms to win large enterprise transformations. - Hyper-Growth SaaS Track Record: 10+ years of progressive leadership in technology alliances, strategic business development, or partner ecosystems within high-growth enterprise software companies. Pay: Base Salary Range:: $271,000 USD - $366,000 USD (note double colon). We'll output as "$271,000 USD - $366,000 USD". Now ensure we don't include boilerplate: DEIB, fraud disclaimer, etc. Now produce HTML fragment. Structure:
About the role
...
Responsibilities
- ... maybe we need subheadings? But we can just list each responsibility as
- with internal detail. Could also nest
- but spec says use
- for any list of duties/requirements/benefits. So we can have top-level
- with each duty as
- . Inside
- we can have further detail as sentences. We'll produce
- Strategy & Technology Partnership Development: ... etc. Similarly for GTM..., Team Building... Then after those, we can add another
- for any list of duties/requirements/benefits. Metrics could be considered duties? We'll just add another
- under Responsibilities for metrics.
Better to keep one
- for responsibilities and another for metrics? But both are lists; we can have two separate
- sections under same heading. That's fine.
Now Requirements:
Requirements
...
Skills:Skills
- ...
Qualifications
- ...
Pay
$271,000 USD - $366,000 USD
Make sure no extra whitespace? It's fine. Now craft the About the role paragraph: combine: "At Anaplan, we are a team of innovators focused on optimizing business decision-making through our leading AI-infused scenario planning and analysis platform so our customers can outpace their competition and the market. What unites Anaplanners across teams and geographies is our collective commitment to our customers’ success and to our Winning Culture. Our customers rank among the who’s who in the Fortune 50. Coca-Cola, LinkedIn, Adobe, LVMH and Bayer are just a few of the 2,400+ global companies who rely on our best-in-class platform. Our Winning Culture
- for Key Metrics? But spec says use
- for any list of duties/requirements/benefits. So we can have top-level