Senior Director, Product Management (Financial Platforms)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting. Content: - About The Product Team (maybe not needed? It's about product team; could be part of About the role? The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "About The Role" section: description of role, responsibilities. We have "What You’ll Do" list: bullet points. We have "What We Look For": list of requirements/qualifications/skills. We have "Base Pay Grade - V Equity Grade - USA 21 Employees new to Affirm typically come in at the start of the pay range..." includes pay ranges. We have "Remote-first with flexibility built in" (schedule? maybe schedule not specified; remote-first indicates flexibility but not schedule specifics. Should we include Schedule? Only if posting actually states schedule details. It says remote-first, flexibility built in, some positions may occasionally require in-person work, few office-based. Not specific schedule like full-time, hours. Probably we should not include Schedule because no explicit schedule. We have "Benefits Designed For You" with bullet points. We have other text: At Affirm we exist..., About The Product Team (maybe we can include as part of About the role? But we already have About The Role. The product team description could be considered part of About the role or maybe we can include as a separate section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those. Thus: -

About the role

: include the paragraph about role and maybe the product team description? The "About The Product Team" could be considered part of about the role context. We'll include it as prose. -

Responsibilities

: list from "What You’ll Do". Use

• . -

  Requirements

  : maybe combine "What We Look For" items that are requirements: years of experience, deep experience in loans, money movement, fintech, etc. Could also include technical fluency, AI-assisted tools, stakeholder management, communication, bachelor's degree. -

  Qualifications

  : maybe overlapping; but we need to avoid duplication. Could split: Requirements = experience years, domain expertise; Qualifications = education, technical fluency, AI tools, stakeholder management, communication, etc. However the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We could have both if we have distinct content. We have "What We Look For" list includes many items; we can split into Requirements (experience, domain) and Qualifications (education, skills). Let's parse: List: - 15+ years of product management experience, with at least 3–5 years managing and developing PM teams including people managers - Deep experience in loans or lending systems — you understand loan lifecycle mechanics, platform architecture for loan servicing, and the compliance and operational requirements that come with it - Meaningful experience in money movement, payments infrastructure, or financial operations — you're fluent in payment rails, settlement flows, cross-border transfers, and the reliability and accuracy standards these systems demand - Experience in fintech, financial services, or banking; familiarity with BNPL, platform products, or backend infrastructure is strongly preferred; capital markets background is a plus - Demonstrated ability to set and execute long-term platform strategy in ambiguous, fast-moving environments - Strong technical fluency — you're comfortable diving into data models and API discussions with engineers and holding informed opinions - Proficiency with AI-assisted tools (e.g., Claude, Cursor) to accelerate your own work and raise the bar for your team - Track record of building and scaling distributed, high-performing PM teams across multiple domains simultaneously - Exceptional stakeholder management skills — you can align Legal, Finance, Engineering, and executive leadership around a common direction - Outstanding written and verbal communication; you tell crisp, data-driven stories to diverse audiences - Bachelor's degree in a related field or equivalent practical experience Thus we could treat first four as Requirements (experience). The rest as Qualifications (skills, education). Or we could have Requirements = experience, Qualifications = education + skills. Let's do that. -

  Skills

  : maybe we could list technical fluency, AI tools, stakeholder management, communication as skills. But we already have Qualifications covering those. Could combine Qualifications and Skills? The instruction says prefer few substantive sections over many thin ones. So maybe we just have Requirements and Qualifications, and skip Skills. But we need to include Skills heading only if we have specific content. We could put skills under Qualifications. Let's decide to have Requirements and Qualifications only, plus About the role, Responsibilities, Benefits, Pay. No Schedule. Now Benefits: we have bullet list: Health coverage at no cost, Spending stipends, Time off to recharge, Own a piece of what you build (ESPP), inclusive interview process, accommodations, etc. Also mention remote-first? That's more about schedule/location but we can include in Benefits? Might be better to put remote-first under Benefits? But it's about work arrangement. Since we don't have Schedule, we could include remote-first under Benefits as a bullet. However the Benefits Designed For You section already lists health coverage, spending stipends, time off, ESPP. The remote-first paragraph is separate. We could include it as a bullet under Benefits as well. Pay: we have base pay ranges for certain states and other states. Also mention Base Pay Grade - V Equity Grade - USA 21. Also mention equity rewards, monthly stipends for health, wellness and tech spending, and benefits (including 100% subsidized medical coverage, dental and vision). That's already in benefits. For Pay section, we should include the base pay ranges. Also mention equity grade? Could include equity grade as part of Pay. We'll include base pay ranges and equity grade. Now we need to ensure we don't include boilerplate like "We’re committed to providing an inclusive interview process..." that's actually part of Benefits? It's about interview process, not benefits. Might be considered boilerplate but it's specific to Affirm's process. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusive interview process is not exactly EEO but could be considered EEO? It's about accommodations for disabilities. Might be considered EEO boilerplate. Safer to remove that line. Also the sentence about "By clicking 'Submit Application,' you acknowledge..." is application instruction, remove. Also "We’re committed to providing an inclusive interview process, including accommodations for candidates with disabilities. If you need support, we’re happy to help." That's EEO-ish; remove. Also "For positions based in San Francisco or Los Angeles: Affirm considers qualified applicants with arrest and conviction records, as required by law." That's legal/EEO; remove. Thus Benefits section will include: Health coverage at no cost: We cover 100% of premiums for employees and their dependents. Spending stipends: Monthly stipends support your tech setup, and the ability to choose health and wellness options that are right for you. Time off to recharge: Flexible time off and generous holiday calendars help you rest when you need to. Own a piece of what you build: Our employee stock purchase plan (ESPP) lets you buy Affirm stock at a discount. Also maybe include remote-first flexibility as a benefit? Could add bullet: Remote-first with flexibility built in: Most roles can be done from almost anywhere within the country of employment; occasional in-person work may be required. Now schedule: we have remote-first but not explicit schedule; we could skip Schedule. Now produce HTML. Structure:

  About the role

  ... (combined About The Product Team and About The Role description)

  Responsibilities

  • Lead and grow a high-performing PM team. Build, mentor, and manage a team of 6–10 product managers, including people managers. You'll set the bar for craft, create development paths, and cultivate a culture of ownership, rigor, and candor.
  • Own the vision and strategy for Loans Lifecycle and Money Movement. Define the multi-year product strategy for Affirm's foundational loan systems and global money movement infrastructure — ensuring they are scalable, compliant, and capable of supporting rapid product innovation. Translate that vision into clear roadmaps and decisions that teams can execute against.
  • Be the domain authority. Serve as the executive-level subject matter expert on loan lifecycle mechanics, payment rails, settlement flows, and institutional transfers — guiding product, engineering, and business partners on tradeoffs, best practices, and platform decisions.
  • Drive cross-functional alignment at scale. Partner closely with Engineering, Accounting, Treasury, Capital Markets, Legal, Compliance, and Client Success teams. Navigate complexity, balance competing stakeholder needs, and build trust through clear communication and a strong delivery track record.
  • Enable platform scalability and international expansion. Architect platform strategies that simplify domain boundaries, standardize loan behaviors across products and markets, and unlock faster time-to-market for new geographies and product lines.
  • Measure and improve platform health. Define success metrics — including settlement success rates, reconciliation coverage, exception volumes, and time-to-resolution — and hold teams accountable to the reliability and accuracy standards these critical systems demand.
  • Influence up and across the organization. Regularly present strategy, tradeoffs, and priorities to senior leadership. Shape organizational thinking on where to invest and what to deprioritize.

  Requirements

  • 15+ years of product management experience, with at least 3–5 years managing and developing PM teams including people managers.
  • Deep experience in loans or lending systems — you understand loan lifecycle mechanics, platform architecture for loan servicing, and the compliance and operational requirements that come with it.
  • Meaningful experience in money movement, payments infrastructure, or financial operations — you're fluent in payment rails, settlement flows, cross-border transfers, and the reliability and accuracy standards these systems demand.
  • Experience in fintech, financial services, or banking; familiarity with BNPL, platform products, or backend infrastructure is strongly preferred; capital markets background is a plus.

  Qualifications

  • Demonstrated ability to set and execute long-term platform strategy in ambiguous, fast-moving environments.
  • Strong technical fluency — you're comfortable diving into data models and API discussions with engineers and holding informed opinions.
  • Proficiency with AI-assisted tools (e.g., Claude, Cursor) to accelerate your own work and raise the bar for your team.
  • Track record of building and scaling distributed, high-performing PM teams across multiple domains simultaneously.
  • Exceptional stakeholder management skills — you can align Legal, Finance, Engineering, and executive leadership around a common direction.
  • Outstanding written and verbal communication; you tell crisp, data-driven stories to diverse audiences.
  • Bachelor's degree in a related field or equivalent practical experience.

  Benefits

  • Health coverage at no cost: We cover 100% of premiums for employees and their dependents.
  • Spending stip