Associate, Fraud Operations

Here's a thinking process: 1. **Analyze the Request:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules specified: - Use `

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

• ` for any list of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** Let me carefully read and extract the meaningful content, structure, and metadata from the job posting. The posting is for a "Fraud and Risk platforms" role, specifically "Fraud Operations Associate" or "Process Manager" (salary says Process Manager). Let me parse it section by section. **Headings/Sections I can identify:** - "What This Role Is About" / "About the role" - describes the role's focus - "Core Responsibilities" / "Responsibilities" - detailed bulleted list of duties - "Basic Qualifications" / "Qualifications" - degree + experience - "Preferred Qualifications" / "Skills" maybe? The rules say use headings for Skills, but I need to check if there's a separate "Skills" section. There's "Preferred Qualifications" which I can map to Skills or Qualifications. - "Pay" / "Salary" - explicitly provided with locations and ranges - "Benefits" - mentioned briefly: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits..." but no specific details. The rules say: never create Benefits section unless the posting actually states them. It does state they exist but no specifics. I should probably either drop it or put a very brief mention if it's substantive. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them exist, but doesn't list details. I think I should not create a Benefits section with placeholder content. I'll check the exact wording: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being. Learn more at the Capital One Careers website. Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level." This is generic, not specific benefits. I'll skip a Benefits section to avoid filler. - "Schedule" - not mentioned explicitly. I won't create it. - "Pay" - explicitly stated with salary ranges by location. I should include a Pay section with the specific data. - "This role is also eligible to earn performance based incentive compensation..." - this is part of pay/compensation, I can include it in Pay or as part of prose. **Metadata to handle:** - Job ID / requisition numbers: Not explicitly shown, but there might be implicit IDs. I'll drop them or fold into a

  . - "At this time, Capital One will not sponsor a new applicant for employment authorization for this position." - this is a substantive policy detail, should be preserved. - "This role is also eligible to earn performance based incentive compensation..." - substantive. - "Capital One offers a comprehensive..." - I'll handle benefits carefully. - "This role is expected to accept applications for a minimum of 5 business days." - application instruction, per rules: "Remove... application instructions." So I drop this. - "No agencies please." - drop. - "Capital One is an equal opportunity employer (EOE, including disability/vet)..." - boilerplate, remove per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - "Capital One promotes a drug-free workplace." - boilerplate, remove. - "Capital One will consider for employment qualified applicants with a criminal history..." - legal/EEO, remove. - "If you have visited our website..." - remove. - "For technical support or questions..." - remove. - "Capital One does not provide, endorse nor guarantee..." - remove. - "Capital One Financial is made up of several different entities..." - remove. - "Please note that any position posted in Canada is for Capital One Canada..." - remove. - "All information you provide will be kept confidential..." - remove. - "This role sits at the operational center..." - this is opening description, I'll include it under "About the role" or as prose. Let me restructure the content respecting the rules. **Identify headings to use (only when there's real content):** - About the role (or "What This Role Is About") - yes, substantive - Responsibilities (or "Core Responsibilities") - yes, detailed list - Qualifications (or "Basic Qualifications" / "Preferred Qualifications") - yes - Pay - yes, specific salary ranges - Maybe "Skills" - the posting has "Preferred Qualifications" which I can treat as Skills, but I need to be careful not to create thin sections. I'll combine Basic and Preferred Qualifications under one "Qualifications" section, or use two sub-sections within a

  . The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists "Qualifications" and "Skills" as examples. I'll likely use "Qualifications" to cover both basic and preferred, or have separate headings if there's enough content. Let me check the content: "Basic Qualifications" and "Preferred Qualifications" are both present. I'll use `

  Qualifications

  ` and list both, or use two headings. To be safe and follow "include a section ONLY when the posting has real, specific content for it", I'll use one "Qualifications" heading and list both basic and preferred within it, using
  • . Or I could use "Requirements" but the example list includes "Qualifications" and "Skills". I'll stick to "Qualifications" and include both sets of criteria. Actually, re-reading the rules: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I should use the most appropriate ones. I'll use: - About the role (from "What This Role Is About") - Responsibilities (from "Core Responsibilities") - Qualifications (covering both Basic and Preferred) - Pay (explicit salary ranges) I won't create Skills, Benefits, Schedule sections because there's no specific content for them that isn't generic/filler. Let me re-examine "Skills". The posting doesn't have a "Skills" section per se, but has "Preferred Qualifications" which are essentially skills/attributes. I'll fold them into Qualifications. **Now, extract and format content:** *About the role:* "This role sits at the operational center of how our Travel platform manages risk, prevents losses, and protects our customers. Our Fraud and Risk platforms are the shield that allows every product team to process transactions securely and confidently. The role focuses on supporting the day-to-day engine of our fraud operations, mitigating risk, and continuously improving our operational processes. Capital One provides a fast paced, dynamic environment where you can excel in your career. At Capital One, diversity, inclusion & belonging are valued at our core, sparking and enabling us to do good for our associates, customers and communities. Guided by our shared values, we thrive in an environment where collaboration and openness are valued. We nurture an environment that attracts and develops talent from all backgrounds and experiences, and empower our associates to do great work by creating a culture of belonging that values diverse perspectives, fosters collaboration and encourages innovative ideas – and are routinely recognized as one of the best companies to work for." Actually, the very first paragraph is the "About the role" essence. I'll condense appropriately but preserve all substantive info. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to keep the text but maybe format it as prose

    . I'll keep it as a coherent block, but I need to be careful not to invent/omit. I'll extract the core "About" text. The posting starts with "This role sits at the operational center..." and goes through the Capital One diversity spiel. I'll include the whole thing as prose under an "About the role" heading, but wait—the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title isn't repeated as a heading by me; the heading is "About the role". That's fine. Let me re-read carefully: "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an `

    ` that is the job title. I'll use `

    About the role

    ` etc. *Responsibilities:* The "Core Responsibilities" section has a lot of bullet points. I need to convert them to `
    • ` items. Let me list them: - Own day-to-day fraud operations: Act as the first line of defense for investigating and resolving complex fraud escalations, high-risk transactions, and account anomalies. - Manage risk disruptions: Handle large-scale incidents as they occur (e.g. spikes in fraudulent activity or coordinated attacks), coordinating impact analysis and operational response. - Handle ad-hoc privacy & compliance workflows: Execute critical, time-sensitive tasks, such as managing customer data deletion requests securely and accurately. - Optimize dispute strategies: Own the continuous improvement and refinement of our chargeback response templates to maximize our dispute win rates and recover revenue. - Oversee third-party performance: Facilitate monthly business reviews for outsourced fraud operations agents, driving course correction and verifying performance incentives. - Maintain operational excellence: Lead the regular review and update of agent Standard Operating Procedures (SOPs) to ensure optimal performance across the team. - Bridge external and internal systems: Partner closely with internal data and risk teams to map transaction data across different systems, streamlining fraud investigations. - Translate operations into strategy: Use the insights gained from daily fraud reviews to flag gaps in our data and inform the broader platform strategy. - Scale your impact: While core fraud operations are your primary mandate, as the role evolves and you build capacity, you will have the opportunity to expand your scope into the payments side of the house - learning how we route, authorize, and reconcile transactions, and taking on projects in that domain. Also there's "How Does The Role Evolve Over the next phase..." which describes evolution. I should include that too, maybe under Responsibilities or as a separate subsection. The rules say "include a section ONLY when the posting has real, specific content for it". The evolution content is specific and substantive, so I'll include it. I could add it as part of Responsibilities or under a separate heading like "Role Evolution" but the allowed headings are the examples. I'll