Manager of Business Analytics - Fraud

We need to output HTML fragment with sections: About the role? Actually the posting includes "What You'll Do" with subsections: Fraud Policy Development, Monitoring Suite & Risk Reporting, Product Launch Support & Ad Hoc Analysis, Cross-Functional Influence & Execution. Also "About You (Qualifications)" which is qualifications. Also "Location:" etc. Also "Salary Range:" and "Additional Compensation:" etc. Also "Benefits:" list. We must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - About the role: Could be the introductory paragraph about Koalafi and role description. The posting includes "What You'll Do" and subsections. That could be considered Responsibilities. - Responsibilities: The bullet lists under Fraud Policy Development etc. Those are duties. - Requirements: Possibly qualifications (education, experience). Could be Requirements. - Qualifications: Might be same as Requirements? The instructions list both but we can combine? They said prefer a few substantive sections over many thin ones. So we could have sections: About the role (intro), Responsibilities (duties), Requirements (qualifications/skills), Benefits, Pay. We have Pay: Salary Range and Additional Compensation. We have Benefits: list. We have Schedule: Not mentioned (no schedule info). So we should NOT include Schedule. We have Skills: Could be part of Requirements (proficiency in Excel, SQL, Python). Could be separate but we can combine. Thus produce sections: About the role, Responsibilities, Requirements, Benefits, Pay. Make sure each heading is

  . Under each, appropriate content: prose in

  , lists in

  • . We must not repeat job title. Not include Job ID. We must preserve all substantive information: need to include location, remote options, etc. Where to put? Could be in About the role paragraph or Requirements? Probably About the role includes location? Actually location is separate metadata. Could be a short

    after About the role? But we shouldn't create extra headings for minor metadata. So we can include location in a

    within About the role or Requirements. Probably About the role. We need to include "Location: Richmond, VA; Arlington, VA; or Remote (U.S.). Associates near one of our office locations may work in-office, hybrid, or remotely. Remote opportunities are available to candidates throughout the United States." Also "Salary Range: $128,000-$165,000 per year (depending on experience and location) Additional Compensation: This position will be eligible to participate in company bonus plan. The final salary offer will depend on factors including, but not limited to, experience, skills, and geographic location. The actual annualized salary amount offered to any candidate at the time of hire will be reflected solely in the candidate’s offer letter." Also "Applications will be accepted until position is filled." That's application instruction; we should remove per instruction: remove application instructions. So drop that. Also "Why choose Koalafi: ..." that's marketing fluff but still substantive? Might be considered boilerplate? It's not EEO but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those; it's about culture. Could keep as part of About the role? Might be considered substantive. But we can keep as part of About the role paragraph. Also "Benefits:" list includes items. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. Structure:

    About the role

    At Koalafi, we believe in a world where no one has to put an important purchase on hold. That’s why we’re making it easier for more people to pay for big purchases over time. Retailers across the country rely on us to offer flexible lease-to-own financing to their non-prime consumers, while increasing sales and strengthening customer loyalty. Their 2M+ customers love us because we provide a flexible way for them to make payments and give them an opportunity to improve their credit. Our 200+ Koalafi teammates enjoy inspiring and challenging work that accelerates their careers. Interested in learning more about how we’re transforming the financing experience and joining our team? The Manager of Business Analytics – Fraud will report directly to the Director of Fraud Strategy & Analytics and play a central role in developing and optimizing Koalafi’s fraud risk strategy. This role will lead analytical efforts to develop and iterate fraud policies, evaluate new fraud defense capabilities and data sources, and strengthen fraud monitoring and reporting frameworks. The position will focus on improving Koalafi’s resilience against evolving fraud trends while enabling responsible growth across new products, channels, and partners. This individual will serve as a key analytical partner to Product, Engineering, Risk Operations, and other cross-functional teams to ensure fraud controls are effectively embedded in customer and merchant workflows. Location: Richmond, VA; Arlington, VA; or Remote (U.S.). Associates near one of our office locations may work in-office, hybrid, or remotely. Remote opportunities are available to candidates throughout the United States.

    Then Responsibilities: we have four subsections each with responsibilities. Could combine into one
    with items being each responsibility group? Better to keep subheadings? But we only allowed

    for section headings; we could use

    ? Not allowed? The instruction only mentions using

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use

    • and inside each
    • we can have for subsection titles. That preserves info. Thus:

      Responsibilities

      • Fraud Policy Development
        • Analyze fraud trends and attack patterns to continuously strengthen automated and manual fraud defenses.
        • Develop and iterate fraud defense strategy (rules, policies, thresholds, decision logic) to maintain strong protection against both ambient fraud activity and coordinated fraud attacks.
        • Design and implement defenses tailored to emerging channels, including direct-to-consumer, to support enterprise-wide scaling initiatives.
        • Evaluate and integrate new fraud detection capabilities, tools, and third-party data sources that improve risk detection and operational efficiency.
        • Enhance and optimize merchant-level fraud risk monitoring and reporting, identifying patterns that may indicate merchant abuse or elevated risk exposure.
      • Monitoring Suite & Risk Reporting
        • Develop and enhance fraud monitoring dashboards and reporting that track fraud performance metrics and trends across customer segments, merchant verticals, and channels.
        • Build analytical tools and monitoring processes designed to detect segment-level anomalies and emerging fraud patterns.
        • Implement automated alerting and anomaly detection to enable timely response to new fraud threats.
        • Partner with Analytics and Data teams to ensure fraud metrics and reporting are accurate, scalable, and aligned across systems.
      • Product Launch Support & Ad Hoc Analysis
        • Support product design and rollout decisions by quantifying trade-offs among fraud risk, approval rate, unit economics, and customer experience.
        • Conduct targeted analyses to evaluate fraud exposure across new merchant partners, verticals, and products.
        • Monitor fraud performance during product launches, pilots, and scaling phases, identifying early indicators of emerging risk.
        • Provide ad hoc analytical support for fraud strategy initiatives and evolving risk mitigation efforts.
      • Cross-Functional Influence & Execution
        • Partner closely with Product and Engineering teams during product development to ensure fraud risk controls are built into key workflows.
        • Collaborate with Risk Operations to ensure manual review processes align with fraud policy intent and evolving fraud patterns.
        • Provide analytical insights that support clear decision-making across stakeholders and initiatives.
        • Help drive alignment across teams by defining project milestones, delivering analytical insights, and maintaining effective communication with key stakeholders.
      Then Requirements/Qualifications: combine education, experience, skills. We'll make a section

      Requirements

      with

      for prose and

      • for list. Content: Bachelor’s degree required, in a quantitative field such as Statistics, Mathematics, Economics, Business, or Engineering preferred; 5+ years of experience in an analyst, data science, or consulting role; 3+ years of experience in fraud risk analytics; Experience in consumer financing industry, such as credit cards, personal loans, auto loans, BNPL, or similar fields; Proficiency in Excel, SQL, and Python for data analysis; Exceptional attention to detail and strong problem-solving skills; Ability to develop strategic project plans and execute against them; Desire to work in a fast-paced, dynamic entrepreneurial environment; Strong written and verbal communication skills. We could list each as
      • . Thus:

        Requirements

        • Bachelor’s degree required, in a quantitative field such as Statistics, Mathematics, Economics, Business, or Engineering preferred
        • 5+ years of experience in an analyst, data science, or consulting role
        • 3+ years of experience in fraud risk analytics
        • Experience in consumer financing industry, such as credit cards, personal loans, auto loans, BNPL, or similar fields
        • Proficiency in Excel, SQL, and Python for data analysis
        • Exceptional attention to detail and strong problem-solving skills
        • Ability to develop strategic project plans and execute against them
        • Desire to work in a fast-paced, dynamic entrepreneurial environment
        • Strong written and verbal communication skills
        Then Benefits:

        Benefits

        • Comprehensive medical, dental, and vision coverage
        • 20 PTO days + 11 paid holidays
        • 401(k) retirement with company matching
        • Student Loan & Tuition Reimbursement
        • Commuter assistance
        • Parental leave (maternal + paternal)
        • Inclusion and Associate Engagement Programs
        Then Pay:

        Pay

        Salary Range: $128,000-$165,000 per year (depending on experience and location). Additional Compensation: This position will be eligible to participate in company bonus plan. The final salary offer will depend on factors including, but not limited to, experience, skills, and geographic location. The actual annualized salary amount offered to any candidate at the time of hire will be reflected solely in