Operations Enablement Lead
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- About The Operations Team (maybe part of About the role? Could be "About the team" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We have "About The Operations Team" describing team. Could be part of "About the role" or maybe we can treat as "About the role". The posting also has "About The Role". So we can combine both into About the role section.
Responsibilities: "What You'll Do" bullet list.
Requirements/Qualifications/Skills: "What We Look For" includes experience, expertise, etc. Could be Requirements and Qualifications. We need to decide which headings to use. We can have Requirements (experience), Qualifications (certifications), Skills (influence, communication, analytical). But we must avoid thin sections. Perhaps combine into one "Requirements" section covering all. But we have allowed headings; we can choose to include only those with substantive content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we include About the role, Responsibilities, Requirements (covering experience, qualifications, skills), Benefits, Pay. Schedule maybe not present (no schedule details). So omit Schedule.
We must not include placeholder like "commensurate with experience". Not present.
We need to extract substantive content.
Let's gather:
About the role: combine About The Operations Team and About The Role paragraphs.
About The Operations Team: "The Operations team delivers seamless customer experiences and enables new product capabilities while ensuring operational excellence. The team owns strategy, planning, technical execution, customer service, fraud operations, process design, quality, training, and program management. We drive efficiency, resolve issues quickly, and scale operations as the business grows. Our goal is to deliver seamless support while maintaining high standards and reducing risk."
About The Role: "Affirm is seeking an Operations Enablement leader to drive scalable, compliant, and high-quality servicing experiences across our Operations organization. In this role, you will define and execute strategies that enable our servicing operations to scale efficiently while maintaining exceptional customer and merchant outcomes. You will set the vision for operational readiness, ensuring that people, processes, and enablement systems evolve in lockstep with Affirm’s servicing strategy. As a member of the Operations Enablement team, you will own a portfolio of cross-functional initiatives aligned to strategic priorities - driving delivery across timelines, dependencies, and measurable business outcomes. You will define and execute servicing strategies by developing clear program roadmaps and execution plans and be responsible for planning, coordination, documentation, change management and measurement across assigned initiatives to ensure operational readiness and measurable outcomes. This role works closely with partners across Product, Engineering, Operations, Compliance, and external vendors to align priorities and ensure readiness for key business and regulatory changes. Serving as a connector between servicing strategy and day-to-day execution, you will translate strategy into scalable operational capabilities. We are looking for a hands-on, data-driven leader who thrives in complex, regulated environments and is passionate about building durable, high-quality servicing experiences at scale."
We can combine into a few paragraphs.
Responsibilities: "What You'll Do" list items:
- Own Program Performance: Lead complex cross-functional programs and initiatives, ensuring alignment with servicing strategy, OKRs, and long-term business priorities.
- Set Strategic Direction: Define and execute the servicing strategy developing clear program roadmaps and execution plans, tracking progress against KPIs, timelines, and budgets.
- Lead Transformation Initiatives: Drive enterprise-wide improvements leveraging Lean Six Sigma, change management, and data-driven methodologies to unlock efficiency, compliance, and customer satisfaction.
- Build Technical Resources: Collaborate with product and engineering teams to translate technical concepts into clear manuals and resources for both human and AI agents.
- Elevate Knowledge Management: Architect and evolve our knowledge ecosystem (SOPs, job aids, learning platforms, AI-enabled knowledge tools), ensuring resources are accurate, engaging, and accessible at scale.
- Translate Technical Concepts: Apply technical depth to plan, design, and create complex operational, instructional, and procedural content, translating technical concepts into clear resources for both human and AI agents.
- Own Learning & Training Strategy: Oversee end-to-end design and delivery of training programs (onboarding, continuous learning, new product rollouts), ensuring effectiveness through measurement and feedback loops.
- Champion Global Readiness: Anticipate and design for operational needs tied to product launches, program expansion, and regulatory changes.
- Drive Insights: Use metrics, dashboards, and qualitative feedback to continuously assess workflows, knowledge adoption, training impact, and localization quality, while influencing senior leadership decisions.
- Influence & Partner at Scale: Serve as a trusted advisor to executives, cross-functional partners, and vendor leaders - driving alignment between company goals and day-to-day execution.
- Build a High-Performing Ecosystem: Lead and coach augmented staff, contractors, and cross-functional contributors to deliver world-class content and learning experiences.
- Lead Change at Scale: Ensure global teams successfully adopt new processes, platforms, and resources through structured change management practices.
- Expand Program Scope: Take on additional program and project management responsibilities as needed, developing working knowledge across adjacent domains to support evolving business needs.
We can put each as
- .
Requirements/Qualifications/Skills: "What We Look For" list:
- 5+ years of experience in program management or product operations, preferably within large-scale or global operations.
- Proven track record of setting strategy and delivering measurable impact across efficiency, compliance, and customer experience.
- Expertise in Lean Six Sigma, project/program management, and change management (Black Belt, PMP, or Prosci certification preferred).
- Experience implementing and scaling knowledge management and training (Salesforce, Confluence, LMS platforms, or AI-driven knowledge tools).
- Strong background in regulated industries (financial services, fintech, or consumer lending highly preferred).
- Exceptional influence and communication skills, with the ability to engage executives, coach teams, and align diverse stakeholders.
- Analytical and data-driven mindset, with a focus on measurable outcomes and continuous improvement.
- Comfort operating in ambiguous, high-growth environments with a builder’s mindset.
- Global perspective with experience supporting vendor/partner operations and distributed teams.
We could split into Requirements (experience, background), Qualifications (certifications), Skills (influence, communication, analytical, builder mindset, global perspective). But to avoid thin sections, maybe combine into one "Requirements" section covering all. However the instruction says use headings for sections like Requirements, Qualifications, Skills. It doesn't forbid combining but we should follow semantics: we can include multiple headings if they have substantive content. Each of those would be substantive. Let's see if we can split meaningfully:
- Requirements: 5+ years experience, proven track record, strong background in regulated industries, global perspective, comfort in ambiguous environments.
- Qualifications: Expertise in Lean Six Sigma, project/program management, change management (certifications), experience implementing and scaling knowledge management and training (specific platforms).
- Skills: Exceptional influence and communication skills, analytical and data-driven mindset, ability to engage executives, coach teams, align stakeholders.
That seems reasonable.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Benefits: section "Benefits Designed For You" with bullet list:
- 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.
- We’re committed to providing an inclusive interview process, including accommodations for candidates with disabilities. If you need support, we’re happy to help.
- For positions based in San Francisco or Los Angeles: Affirm considers qualified applicants with arrest and conviction records, as required by law.
Also mention: "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.)" This overlaps with benefits but we can incorporate.
Pay: "Base Pay Grade - J Equity Grade - 5 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.) USA base pay range (CA, WA, NY, NJ, CT) per year: $130,000 - $180,000 USA base pay range (all other U.S. states) per year: $115,000 - $165,000"
We should include Pay section with those ranges.
Schedule: Not present; omit.
We must not include boilerplate like "By clicking 'Submit Application,' you acknowledge..." etc. Also remove "We’re committed to providing an inclusive interview process..." maybe that's part of benefits? It's more about interview process; could be considered boilerplate but it's about accommodations. Might be considered EEO? It's about accommodations for disabilities. Might be considered EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that line. 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 also EEO-related (ban the box). Likely remove as well. Also "If you need support, we’re happy to help." That's part of that line; remove.
Thus benefits section should include only substantive benefits: health coverage, spending stipends, time off, ESPP. Also maybe mention equity rewards, monthly stipends for health, wellness and tech spending (already covered). The benefits description includes "monthly stipends for health, wellness and tech spending" which is similar to spending stipends. We'll keep.
Now construct HTML.
We need
for each section heading.
We'll have:
About the role
...combined paragraphs...
Responsibilities
- ...
...
Requirements
- 5+ years of experience in program management or product operations, preferably within large-scale or global operations.
- Proven track record of setting strategy and delivering measurable impact across efficiency, compliance, and customer experience.
- Strong background in regulated industries (financial services, fintech, or consumer lending highly preferred).
- Global perspective with experience supporting vendor/partner operations and distributed teams.
- Comfort operating in ambiguous, high-growth environments with a builder’s mindset.
Qualifications
- Expertise in Lean Six Sigma, project/program management, and change management (Black Belt, PMP, or Prosci certification preferred).
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - About The Operations Team (maybe part of About the role? Could be "About the team" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have "About The Operations Team" describing team. Could be part of "About the role" or maybe we can treat as "About the role". The posting also has "About The Role". So we can combine both into About the role section. Responsibilities: "What You'll Do" bullet list. Requirements/Qualifications/Skills: "What We Look For" includes experience, expertise, etc. Could be Requirements and Qualifications. We need to decide which headings to use. We can have Requirements (experience), Qualifications (certifications), Skills (influence, communication, analytical). But we must avoid thin sections. Perhaps combine into one "Requirements" section covering all. But we have allowed headings; we can choose to include only those with substantive content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we include About the role, Responsibilities, Requirements (covering experience, qualifications, skills), Benefits, Pay. Schedule maybe not present (no schedule details). So omit Schedule. We must not include placeholder like "commensurate with experience". Not present. We need to extract substantive content. Let's gather: About the role: combine About The Operations Team and About The Role paragraphs. About The Operations Team: "The Operations team delivers seamless customer experiences and enables new product capabilities while ensuring operational excellence. The team owns strategy, planning, technical execution, customer service, fraud operations, process design, quality, training, and program management. We drive efficiency, resolve issues quickly, and scale operations as the business grows. Our goal is to deliver seamless support while maintaining high standards and reducing risk." About The Role: "Affirm is seeking an Operations Enablement leader to drive scalable, compliant, and high-quality servicing experiences across our Operations organization. In this role, you will define and execute strategies that enable our servicing operations to scale efficiently while maintaining exceptional customer and merchant outcomes. You will set the vision for operational readiness, ensuring that people, processes, and enablement systems evolve in lockstep with Affirm’s servicing strategy. As a member of the Operations Enablement team, you will own a portfolio of cross-functional initiatives aligned to strategic priorities - driving delivery across timelines, dependencies, and measurable business outcomes. You will define and execute servicing strategies by developing clear program roadmaps and execution plans and be responsible for planning, coordination, documentation, change management and measurement across assigned initiatives to ensure operational readiness and measurable outcomes. This role works closely with partners across Product, Engineering, Operations, Compliance, and external vendors to align priorities and ensure readiness for key business and regulatory changes. Serving as a connector between servicing strategy and day-to-day execution, you will translate strategy into scalable operational capabilities. We are looking for a hands-on, data-driven leader who thrives in complex, regulated environments and is passionate about building durable, high-quality servicing experiences at scale." We can combine into a few paragraphs. Responsibilities: "What You'll Do" list items: - Own Program Performance: Lead complex cross-functional programs and initiatives, ensuring alignment with servicing strategy, OKRs, and long-term business priorities. - Set Strategic Direction: Define and execute the servicing strategy developing clear program roadmaps and execution plans, tracking progress against KPIs, timelines, and budgets. - Lead Transformation Initiatives: Drive enterprise-wide improvements leveraging Lean Six Sigma, change management, and data-driven methodologies to unlock efficiency, compliance, and customer satisfaction. - Build Technical Resources: Collaborate with product and engineering teams to translate technical concepts into clear manuals and resources for both human and AI agents. - Elevate Knowledge Management: Architect and evolve our knowledge ecosystem (SOPs, job aids, learning platforms, AI-enabled knowledge tools), ensuring resources are accurate, engaging, and accessible at scale. - Translate Technical Concepts: Apply technical depth to plan, design, and create complex operational, instructional, and procedural content, translating technical concepts into clear resources for both human and AI agents. - Own Learning & Training Strategy: Oversee end-to-end design and delivery of training programs (onboarding, continuous learning, new product rollouts), ensuring effectiveness through measurement and feedback loops. - Champion Global Readiness: Anticipate and design for operational needs tied to product launches, program expansion, and regulatory changes. - Drive Insights: Use metrics, dashboards, and qualitative feedback to continuously assess workflows, knowledge adoption, training impact, and localization quality, while influencing senior leadership decisions. - Influence & Partner at Scale: Serve as a trusted advisor to executives, cross-functional partners, and vendor leaders - driving alignment between company goals and day-to-day execution. - Build a High-Performing Ecosystem: Lead and coach augmented staff, contractors, and cross-functional contributors to deliver world-class content and learning experiences. - Lead Change at Scale: Ensure global teams successfully adopt new processes, platforms, and resources through structured change management practices. - Expand Program Scope: Take on additional program and project management responsibilities as needed, developing working knowledge across adjacent domains to support evolving business needs. We can put each as
for each section heading.
We'll have:
About the role
...combined paragraphs...
Responsibilities
- ... ...
Requirements
- 5+ years of experience in program management or product operations, preferably within large-scale or global operations.
- Proven track record of setting strategy and delivering measurable impact across efficiency, compliance, and customer experience.
- Strong background in regulated industries (financial services, fintech, or consumer lending highly preferred).
- Global perspective with experience supporting vendor/partner operations and distributed teams.
- Comfort operating in ambiguous, high-growth environments with a builder’s mindset.
Qualifications
- Expertise in Lean Six Sigma, project/program management, and change management (Black Belt, PMP, or Prosci certification preferred).