VP, Technology Partnerships

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 that have real content. We need to parse the job posting and extract relevant content. We should not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove DEIB statement? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. DEIB is not exactly EEO but could be considered equal-opportunity? It's about diversity, equity, inclusion. Likely considered EEO boilerplate and should be removed. Also Fraud Recruitment Disclaimer is scam-warning, remove. We need to preserve substantive info: company description, role description, impact, responsibilities, requirements, qualifications, skills, metrics for success, base salary range. We need to decide sections: About the role (maybe summary), Responsibilities, Requirements (or Qualifications), Skills, Benefits? There's no explicit benefits listed besides maybe DEIB but removed. Pay: base salary range given. Schedule: not mentioned. So we can include Pay section with salary range. Benefits: none explicit, so omit. We need to use

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

  for prose. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like bullet points. Let's extract sections: - About the role / Overview: The introductory paragraphs describing Anaplan, mission, culture, and the role: "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." Also earlier description of Anaplan: "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...." That's substantive. We could combine into About the role. - Insight on Your Impact: This is a paragraph describing impact. Could be part of About the role or separate section maybe "Impact". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put impact under About the role or Responsibilities. Probably About the role includes overview and impact. - Responsibilities: The "Job Requirements & Core Responsibilities" section includes many bullet points under headings: Strategy & Technology Partnership Development (with subpoints), GTM Translation & Cross-Functional Alignment, Team Building & Performance Leadership. We need to extract those as list items under Responsibilities. We need to preserve all substantive info, not lose details. So we need to list each bullet as

• . The bullet points are: Under 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. Under 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. Under 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 keep these as list items. - Requirements / Qualifications: The "Profile of the Ideal Candidate" and "Required Skills and Experience" and "Preferred Experience" and "Key Metrics for Success". We need to separate maybe Requirements (required) and Qualifications (preferred) or Skills. The allowed headings: Requirements, Qualifications, Skills. We need to decide. We have Required Skills and Experience (list). Also Preferred Experience (list). Also Key Metrics for Success (list). Also Profile of the Ideal Candidate (paragraph). We could treat Required Skills and Experience as Requirements, Preferred Experience as Qualifications, Key Metrics for Success as maybe Skills? But Skills heading is for skills list. However we already have Required Skills and Experience which includes skills. Could put that under Skills. But we also have Requirements heading for maybe the profile paragraph. Let's think. We need to follow instruction: Use headings only when posting has real, specific content for it. So we can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with content. We have content for About the role (overview + impact). Responsibilities (list). Requirements (maybe the Profile of the Ideal Candidate paragraph). Qualifications (maybe Required Skills and Experience? Actually that's skills). But we could treat Required Skills and Experience as Skills. Qualifications could be Preferred Experience. Key Metrics for Success could be maybe under Requirements? But it's metrics for success, not a qualification. Could be under Responsibilities? Not exactly. Could be its own section but not in allowed headings. Could we put under Requirements? Might be okay but it's not a requirement. However we could put under Requirements as "Key Metrics for Success" as a list. But the heading would be Requirements, which might be misleading. Better to have a separate section like "Qualifications" for required skills, and "Skills" for preferred? Hmm. Let's map: - About the role: overview + impact. - Responsibilities: list of duties. - Requirements: maybe the "Profile of the Ideal Candidate" paragraph (describes ideal candidate). - Qualifications: maybe "Required Skills and Experience" (list of required skills/experience). - Skills: maybe "Preferred Experience" (list of preferred). - Pay: base salary range. - Benefits: none. - Schedule: none. Key Metrics for Success: could be placed under Responsibilities? It's about how performance will be evaluated. Could be a separate section but not allowed. Could be placed under Requirements? Not ideal. Could be placed under Qualifications? Not ideal. Could be placed under About the role? Not ideal. Perhaps we can treat Key Metrics for Success as a subsection under Responsibilities? It's about outcomes, not duties. But we could still include as a list under Responsibilities with heading "Key Metrics for Success" as a subheading? Not allowed because only

  for section headings. We could embed as a

  inside Responsibilities? But we need to preserve all substantive info; we could add a

  after the list describing metrics. That would be okay. Thus we can have:

  About the role

  ... (overview + impact)

  Responsibilities

  • ... each duty

  Key Metrics for Success: ... list

  Requirements

  Profile of the Ideal Candidate paragraph.

  Qualifications

  • Required Skills and Experience items

  Skills

  • Preferred Experience items

  Pay

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

  We need to ensure we don't repeat "Base Salary Range::" maybe there is double colon. Keep as is. We need to remove boilerplate: DEIB, Fraud Recruitment Disclaimer, etc. Also need to remove duplicated lines: there may be duplicate sentences? Not seeing. Now craft the HTML. We need to preserve all substantive info: ensure we include all bullet points exactly as given. Let's extract the exact text for each bullet. From posting: 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