Partnerships Product Manager

We need to output HTML fragment with sections: About the role? Actually "Who We Are" is description of company; we can treat as "About the company" but headings allowed: About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have content: "Who We Are" description (company overview). Could be placed under a heading like "About the company" but not in allowed list. Allowed headings list includes "About the role". The "Who We Are" is about company, not role. Could we put under "About the role"? Might be okay but it's not exactly role. However we could treat "Who We Are" as a paragraph before sections, not a heading. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could use other headings if appropriate? Probably better to stick to those. We can have "About the role" heading and include the role description (The Role ...) plus maybe "Who We Are" as a paragraph before? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings besides those examples, but they gave examples. Safer to use only those headings when we have content. We have sections: Responsibilities (What You'll Do). Requirements (Role Requirements & Qualifications). Qualifications maybe same as Requirements? Could combine. Skills maybe not explicit separate. Benefits: not specified beyond generic statement about compensation includes base+bonus+equity+benefits but no specific benefits listed. So we should not create Benefits section because no specific content. Pay: they give base salary range $178,000—$223,000 USD. Also mention bonus, equity, benefits. So we can create Pay section with that info. Schedule: not mentioned, so omit. We also have "Our Values" etc. That's not a section heading per allowed list; could be omitted or put under a generic heading? Probably omit as not required. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the company overview "Who Are ..." as a paragraph maybe before sections. That's substantive. We'll include it as a

before any headings. We need to include the role description under "About the role" heading? Actually "The Role" heading is present in text. We could use

About the role

and put the paragraph(s) describing the role (the role description). Then responsibilities under maybe

Responsibilities

with list items from "What You’ll Do". Then qualifications under

Qualifications

(or Requirements). We have "Role Requirements & Qualifications" section; we can put that under

Qualifications

(or Requirements). We'll choose Qualifications. We also have "Core Performance Metrics (KPIs)" maybe could be under Skills? Not exactly. Could be under Responsibilities? Might be better to create a section "Key Performance Metrics" but not allowed. Could incorporate into Responsibilities as list items? They are metrics for success; could be under Responsibilities as bullet points. But we should not invent headings. We'll keep them under Responsibilities as additional bullet points. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we will make a list. For qualifications we will make a list. Pay section: we can put

  with salary range and note about bonus etc. We must not include boilerplate like EEO, scam warning, etc. Remove those. We must not include application instructions. We must not include duplicated lines. Let's extract content. Company overview: "Who We Are Addepar is a global data and AI platform empowering investment professionals to turn complex financial information into actionable intelligence. Addepar unifies portfolio, market and client data in a total portfolio view and delivers AI-powered insights within investment and client workflows. More than 1,400 firms in nearly 60 countries use Addepar to manage and advise on nearly $9 trillion in assets. Its open platform integrates with nearly 650 software, data and consulting partners to power end-to-end investment operations across firms of all sizes and complexity. Addepar supports clients worldwide with offices in New York City, Salt Lake City, London, Edinburgh, Pune, Dubai, Geneva, Singapore and São Paulo." That's one paragraph. Role description: "The Role Addepar is seeking a Partnerships Product Manager to join our Product Management organization and lead the strategic vision, technical execution, and ongoing governance of Addepar’s external technology partner ecosystem. In this role, you will ensure that every external technology partnership tightly aligns with Addepar’s overarching product and platform strategy enabling Addepar to become the operational hub where the most valuable work takes place. The role will report directly to Addepar’s Head of Product. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits." We might keep the recruiter sentence as part of Pay section? It mentions salary range. We'll keep it in Pay. Responsibilities (What You’ll Do): bullet points: - Strategic & Commercial Alignment - Align every partnership initiative directly with Addepar’s core product strategy, ensuring integrations and overall partnerships strengthen platform stickiness rather than creating disparate feature forks. - Deliver skilled relationship management in navigating external political organizations and influence external partners to prioritize development on the partner side to unblock additional integration capabilities or make exceptions to policies, such as restrictive rate limits or no-AI usage clauses. - Drive commercial value creation by prioritizing partnerships that increase partner-attached ARR, expand distribution channels, improve retention, and optimize gross margins. - Define and measure key value of the product partnerships in health and financial metrics, including partner adoption and co-selling impact. - Data Sovereignty, Security & Governance - Ensure data governance, zero-trust security frameworks, and granular access controls across all integration points to prevent data leakage and protect proprietary client data. - Ensure Addepar maximises ownership of the client and data experience by ensuring third-party tools and data are available within the Addepar platform. - Establish clear data-sharing protocols and audit mechanisms with external technology partners. - Partner Productization, Enablement & Operational Alignment - Lead product discovery and solution design for strategic partnerships, working with clients, partners, design, engineering, and internal product teams to understand user workflows, identify the highest-value integration points, and iterate on the target experience—from early concepts and workflow diagrams through requirements and implementation. - Lead cross-functional alignment across Legal, InfoSec, Compliance, and Commercial teams to establish streamlined, institutional-grade risk assessment and deal-structuring workflows. - Establish standards, scalable and repeatable processes and patterns for how we partner from a commercial and engagement perspective. - Work with key stakeholders to design, scale and support partner onboarding pathways, including collaborating to build out self-serve developer portals, robust sandbox environments, standardized API/SDK documentation, and client onboarding partner platform. - Serve as the primary technical and strategic interface for external partner product and engineering leadership. - Work proactively and collaboratively with services partnership program peers residing outside the product organization. - Market Scanning & Product Advisory - Proactively scan the financial services, wealthtech, and fintech landscapes to identify emerging technologies, disruptive providers, and potential strategic co-innovation opportunities. - Act as an internal advisor to domain Product Managers across Addepar, conducting build-vs-buy analyses, integration feasibility assessments, and ecosystem dependency reviews for core features. We could keep each bullet as

• . Might be long but okay. Qualifications (Role Requirements & Qualifications): list: - Experience: 5+ years in Product Management within B2B SaaS, specifically focused on financial technology, wealth management, banking software, or complex enterprise API platforms. - Technical Acumen: Strong understanding of modern web architectures, RESTful APIs, webhooks, data schemas, security protocols (OAuth, SOC2), and developer ecosystem tooling. - Data Strategy & Security Focus: Familiarity with financial data privacy regulations, data sovereignty requirements, and secure entitlement frameworks. - Cross-Functional Execution: Proven track record of navigating complex internal alignment across Legal, Security, Finance, and GTM functions while negotiating win-win commercial/technical structures with external partners. - Domain Knowledge: Deep understanding of the financial services ecosystem (e.g., core banking, ledger systems, custodians, market data vendors, KYC/AML platforms). - Strategic Thinking: Ability to evaluate build vs. buy vs. partner choices using data-driven frameworks and map them to executive-level product and commercial goals. Also Core Performance Metrics (KPIs) maybe could be under Qualifications? But they are metrics for success; could be under Responsibilities as list items. We'll add them under Responsibilities as additional bullet points maybe under a subheading? But we cannot add headings not in list. We could just add them as list items under Responsibilities without subheading. That's okay. Add KPI bullets: - Commercial Impact: Partner-driven ARR growth, deal attachment rates, and ecosystem customer retention. - Platform Security & Experience: Zero data exposure/leakage incidents and adherence to native platform UX design standards. - Partner Velocity & Onboarding Efficiency: Decreased cycle time from partner execution to live, active platform integration. - Ecosystem Usage: API call throughput, monthly active users (MAU) on partner connectors, and technical uptime/reliability. Now Pay section: include base salary range and note about bonus etc. We have: "Base Salary Range $178,000—$223,000 USD". Also earlier: "Addepar takes a market-based approach to pay. A successful candidate's starting pay will be determined based on the role, job-related skills, experience, qualifications, work location, and market conditions. The range displayed on each job posting reflects the minimum and maximum target base salary for this role within the United States. Compensation for this role includes base salary + bonus + equity + benefits. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Additionally, these ranges reflect the base salary only, and do not include bonus, equity, or benefits." We'll include that as a paragraph under Pay. We should not include the repeated sentence about recruiter sharing salary range twice; we can keep once. Now we need to output only HTML fragment, no /. Use

  for headings. Structure:

  Who We Are ...

  About the role

  The Role ...

  Responsibilities

  • ... each bullet
  ...

  Qualifications

  • ... each bullet
  ...

  Pay

  ... salary range paragraph ...

  We should not include Schedule or Benefits. Check for any duplicated lines: we need to ensure we didn't repeat the recruiter sentence twice. We'll include it once. Now ensure we preserve all substantive information: Did we miss any? The "Our Values" section we omitted; that's substantive but not under allowed headings. Could we include as a

  without heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. ...). It might be okay to have other headings but they