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 heading. No Job ID. Remove boilerplate. Use

for headings. Use

• for lists. Use

  for prose. We need to parse the posting. Key sections: - About The Product Team (maybe not needed? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "About The Role" content: description of role, responsibilities. That can go under "About the role" heading. Responsibilities: bullet list from "What You’ll Do". We'll extract each bullet. Requirements/Qualifications/Skills: The "What We Look For" list includes many items. Could split into Requirements (experience), Qualifications (education), Skills (technical fluency, stakeholder management, communication). But we need to decide based on content. We have "Base Pay Grade - V Equity Grade - USA 21 Employees new to Affirm typically come in at the start of the pay range..." then pay ranges. So we have Pay section. Benefits: "Benefits Designed For You" list. Schedule: Not mentioned explicitly. There's remote-first flexibility, but not schedule specifics. Should we include Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated, so omit Schedule. We must not include placeholder like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is some legal text about privacy notice, arrest and conviction records, etc. That's boilerplate; remove. Also remove "We’re committed to providing an inclusive interview process..." etc. That's boilerplate. Now craft HTML. Structure:

  About the role

  ... (the paragraph from About The Role)

  Then Responsibilities:

  Responsibilities

  • ... each bullet
  Then Requirements: maybe combine experience requirements. Could list bullet points from "What We Look For" that are experience/requirements: 15+ years product management experience, with at least 3–5 years managing and developing PM teams including people managers; Deep experience in loans or lending systems; Meaningful experience in money movement, payments infrastructure, or financial operations; 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. We could separate Requirements (experience) and Qualifications (education) and Skills (technical fluency, stakeholder management, communication, AI tools). But the instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they ask to use headings for those categories if content exists. We have content for each. Let's decide: - Requirements: experience requirements (years, loan experience, money movement, fintech, etc.) - Qualifications: Bachelor's degree or equivalent. - Skills: technical fluency, AI-assisted tools, stakeholder management, communication, ability to set strategy, track record building teams. But some overlap. However we must not invent or summarize away detail; we can list all bullets under appropriate headings, ensuring we don't lose any. Let's extract each bullet from "What We Look For": 1. 15+ years of product management experience, with at least 3–5 years managing and developing PM teams including people managers 2. 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 3. 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 4. Experience in fintech, financial services, or banking; familiarity with BNPL, platform products, or backend infrastructure is strongly preferred; capital markets background is a plus 5. Demonstrated ability to set and execute long-term platform strategy in ambiguous, fast-moving environments 6. Strong technical fluency — you're comfortable diving into data models and API discussions with engineers and holding informed opinions 7. Proficiency with AI-assisted tools (e.g., Claude, Cursor) to accelerate your own work and raise the bar for your team 8. Track record of building and scaling distributed, high-performing PM teams across multiple domains simultaneously 9. Exceptional stakeholder management skills — you can align Legal, Finance, Engineering, and executive leadership around a common direction 10. Outstanding written and verbal communication; you tell crisp, data-driven stories to diverse audiences 11. Bachelor's degree in a related field or equivalent practical experience Now assign: Requirements: items 1-4 (experience). Possibly also item 5 (ability to set strategy) could be considered requirement but it's more skill. We'll put 5 under Skills. Qualifications: item 11 (Bachelor's degree). Skills: items 5-10 (strategy, technical fluency, AI tools, track record building teams, stakeholder management, communication). Now Benefits: list from "Benefits Designed For You": 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 mention "We’re committed to providing an inclusive interview process..." but that's boilerplate; remove. Pay: Base pay ranges: USA base pay range (CA, CT, NJ, NY, WA) per year: $340,000 - $375,000; USA base pay range (all other U.S. states) per year: $305,000 - $340,000. Also mention Base Pay Grade - V Equity Grade - USA 21 Employees new to Affirm typically come in at the start of the pay range. Affirm focuses on providing a simple and transparent pay structure which is based on a variety of factors, including location, experience and job-related skills. Base pay is part of a total compensation package that may include equity rewards, monthly stipends for health, wellness and tech spending, and benefits (including 100% subsidized medical coverage, dental and vision for you and your dependents.) We should include all that. Now About the role paragraph: from "About The Role Our Financial Platform sits at the heart..." up to before "What You’ll Do". Let's capture: "Our Financial Platform sits at the heart of every loan Affirm makes and every dollar we move. We're looking for a Senior Director of Product Management to lead and scale the teams behind two of our most critical and complex domains: Loans Lifecycle and Money Movement. This is a role for a seasoned product leader who thrives in the intersection of financial systems, platform engineering, and organizational scale." We could also include preceding sentences about Product Team? But that's under About The Product Team; maybe not needed. The instruction says use headings like About the role, Responsibilities, etc. So we can put the About the role paragraph as above. Now Responsibilities: list each bullet from "What You’ll Do". Let's extract: - 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. Now we need to output HTML fragment only. Let's construct. We'll have sections:

  About the role

  Our Financial Platform sits at the heart of every loan Affirm makes and every dollar we move. We're looking for a Senior Director of Product Management to lead and scale the teams behind two of our most critical and complex domains: Loans Lifecycle and Money Movement. This is a role for a seasoned product leader who thrives in the intersection of financial systems, platform engineering, and organizational scale.

  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