VP, Technology Partnerships

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes: description about company, role description, responsibilities, requirements, etc. It includes Base Salary Range. No explicit Benefits, Schedule. So we should include sections: About the role (maybe from intro), Responsibilities (Job Requirements & Core Responsibilities), Requirements (Profile of the Ideal Candidate, Required Skills and Experience), maybe Skills (but could be combined with Requirements). We need to decide sections: Could have About the role (intro), Responsibilities (list), Requirements (list), Skills (maybe list of required skills), Pay (base salary range). Benefits and Schedule not present, so omit. Also Qualifications maybe similar to Requirements; but we can include Qualifications if content. The posting includes "Profile of the Ideal Candidate", "Required Skills and Experience", "Preferred Experience". Could treat as Requirements and Qualifications. We'll include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Ensure we don't repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: DEIB, fraud disclaimer, etc. Also remove navigation, cookie, legal, EEO, etc. So we will strip those paragraphs. We need to extract content: Intro: "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 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 ImpactThis 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 the About the role and responsibilities combined. We'll separate: About the role: company description and role overview. Responsibilities: bullet list from "Job Requirements & Core Responsibilities". Let's extract responsibilities list: Under "Job Requirements & Core Responsibilities" there are subheadings: - 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'll turn each bullet into

• . Next: "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, 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. Then "Preferred Experience" 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. Then "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. Then "Base Salary Range:: $271,000 USD - $366,000 USD". Note double colon; we will keep as is. We need to decide sections: About the role (intro), Responsibilities (list from Job Requirements & Core Responsibilities), Requirements (maybe combine Required Skills and Experience + Profile of Ideal Candidate?), Qualifications (maybe Preferred Experience?), Skills (maybe list of skills from Required Skills and Experience?), Pay (salary). But we must not create thin sections; better to combine related content. We have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: company overview + role overview (the initial paragraphs up to "Insight on Your Impact" maybe). - Responsibilities: the bullet list under Job Requirements & Core Responsibilities. - Requirements: Required Skills and Experience (maybe also Profile of Ideal Candidate? but that's more about candidate traits). Could put Profile of Ideal Candidate under Requirements. - Qualifications: Preferred Experience. - Skills: maybe we could list specific skills from Required Skills and Experience? But that duplicates. Could instead put Skills as a list of technical acumen etc. But we already have Required Skills and Experience as Requirements. Might be okay to have Requirements and Skills both; but we need to avoid thin sections. Perhaps we combine Required Skills and Experience into Skills section, and Requirements into Requirements (including Profile). Let's think. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use any of those. We need to include a section only when posting has real specific content for it. So we need to decide which sections have content. We have content for About the role (yes). Responsibilities (yes). Requirements (we have Profile of Ideal Candidate and Required Skills and Experience). Qualifications (we have Preferred Experience). Skills (maybe we could extract specific skills like "Tech Ecosystem Leadership", "Partner Apps & Platform Extensibility", etc. But those are more like experience areas. Could treat them as Skills. But then Requirements would be something else? Hmm. Maybe better: About the role, Responsibilities, Requirements (combining Required Skills and Experience + Profile), Qualifications (Preferred Experience), Pay (salary). Omit Skills because we already covered skills in Requirements. But we need to use headings from list; we can omit Skills if not needed. The instruction says "Prefer a few substantive sections over many thin ones." So we can skip Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check if we have Benefits or Schedule: none, so omit. Now we need