VP, Technology Partnerships

We need to output HTML fragment with sections: About the role? The posting includes description of company, role, responsibilities, requirements, etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have Pay: Base Salary Range given. Benefits? Not explicit; there is mention of "Everything that makes you unique is welcome; join us and let’s build what’s next - together!" but no explicit benefits. There's mention of "Supported by operating principles..." but not benefits. There's no schedule. So we should include Pay section only. Possibly also include "About the role" as a heading? The posting includes description of role and impact. Could treat that as About the role. Also "Job Requirements & Core Responsibilities" includes responsibilities and requirements. Could split into Responsibilities and Requirements sections. Also "Profile of the Ideal Candidate" could be Qualifications/Skills. Also "Key Metrics for Success" maybe not needed as a heading (not in list). We should not invent sections like Benefits if not present. Also we should not repeat job title as heading. Should not include Job ID etc. Should remove boilerplate like DEIB, fraud disclaimer, etc. Also remove navigation etc. So we need to extract substantive content. Let's parse: Company description: At Anaplan... (first paragraph). Could be considered "About the role"? Actually it's about company. Could be "About the role" or maybe "About Anaplan". But headings limited to given list. We could use "About the role" to include role description and impact. Or we could skip About the role if not explicit. But we have "Insight on Your Impact" and description of role. That could be under About the role. Responsibilities: The bullet points under "Job Requirements & Core Responsibilities" include many responsibilities: Strategy & Technology Partnership Development (subpoints), GTM Translation & Cross-Functional Alignment, Team Building & Performance Leadership. We can list them as

• . Requirements: The "Profile of the Ideal Candidate" and "Required Skills and Experience" list required skills/experience. Could be Requirements section. Qualifications/Skills: Could combine but we have separate headings Qualifications and Skills. Might split: Qualifications (education/experience) and Skills (specific abilities). But we have limited content; maybe better to put all under Requirements and skip Qualifications/Skills if thin. However we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Pay. That's four sections. We must not include Benefits or Schedule as they aren't specified. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details like specific CSPs, Data Cloud/AI platforms, ISVs, etc. Also mention "Power of Three", etc. Also mention metrics for success? That's substantive but not under given headings; maybe we could include under Responsibilities or Requirements? But we should not create new headings not in list. Could we include them as part of Responsibilities? Possibly under Responsibilities we can add a bullet about metrics? But metrics are for success evaluation, not responsibilities. Could we include them under Requirements? Not ideal. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding extra sections not in list, but the allowed headings are given; we should use those headings for sections. It says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use other headings? It says use

  for section headings (e.g. ...). Likely they expect only those headings. Safer to stick to those. Thus we need to map content to those headings. About the role: include company description, role title, impact description. Responsibilities: include the bullet points under Job Requirements & Core Responsibilities (the responsibilities). Also maybe include "Insight on Your Impact" as part of About the role. Requirements: include Profile of the Ideal Candidate, Required Skills and Experience, maybe also Key Metrics for Success? But metrics are not requirements; they'd be evaluation. Could we put them under Requirements? Might be okay but could be considered not accurate. However we have no other section for metrics. Could we omit metrics? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include metrics somewhere. If we cannot create a new heading, we could include them as a paragraph under Requirements or maybe under About the role? But that would misrepresent. However maybe we can include them under Requirements as "Key success metrics" as a paragraph (still under Requirements heading). That's not inventing a heading; it's just content under that heading. That seems acceptable. Pay: include Base Salary Range. We must not include Benefits or Schedule. We must strip boilerplate: DEIB, fraud disclaimer, etc. Now produce HTML fragment. Structure:

  About the role

  ... company description and role impact ...

  Responsibilities

  • ...
  ...

  Requirements

  ... profile of ideal candidate ...

  ... required skills and experience ...

  Key metrics for success: ...

  Pay

  Base Salary Range: $271,000 USD - $366,000 USD

  Make sure to preserve details. Let's craft About the role paragraph: "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 is the engine that drives our teams of innovators. We champion diversity of thought and ideas, we behave like leaders regardless of title, we are committed to achieving ambitious goals, and we love celebrating our wins – big and small. Supported by operating principles of being strategy-led, values-based and disciplined in execution, you’ll be inspired, connected, developed and rewarded here. Everything that makes you unique is welcome; join us and let’s build what’s next - together! Anaplan is looking for an entrepreneurial and highly strategic VP, Technology Partnerships. This is a stellar opportunity to lead a high-visibility, global organization within a leading enterprise cloud company. If you are an ecosystem builder who thrives on defining technology alliance strategies, rolling up your sleeves to drive execution, scaling a developer and partner apps ecosystem, and building a high-performing global team from the ground up, this role is for you. Insight on Your Impact: This role serves as the strategic leader for Anaplan's global technology and product ecosystem. You will be responsible for defining and executing our global technology partnership strategy, building innovative alliances with Cloud Service Providers (CSPs), Data Cloud/AI platforms, and Independent Software Vendors (ISVs), while scaling our Partner Apps program. You will translate complex technical integrations into high-impact, revenue-generating go-to-market motions executed in collaboration with regional partner sales teams. Your focus will be centered on developing strategic Technology, Data/AI, and Cloud partnerships, alongside leading and expanding the Partner Apps program to drive platform extensibility and customer value. In parallel, you will curate high-leverage 'Power of Three' motions—aligning Anaplan, technology partners, and System Integrators (SIs) to deliver comprehensive, differentiated enterprise solutions. You will own this function end-to-end: from initial strategy development and team build-out to hands-on partner development, solution co-innovation, and global scaling." That's a lot but okay. Now Responsibilities: list bullet points from "Job Requirements & Core Responsibilities". Let's extract each bullet: - 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. We need to preserve all details. We'll put each as
• maybe with sub-bullets? But we can just put each bullet as a
• with the content. Could also nest but not required. Now Requirements: include Profile of the Ideal Candidate paragraph and Required Skills and Experience list. 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." Then Required Skills and Experience 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,