Analyst I, Fraud Prevention

We need to output HTML fragment with sections: About the role, About the team, What You Will Be Doing, What You Bring, Bonus If You Have, What We Offer You (including benefits). Also maybe include Position Type etc? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove privacy statement, EEOC statement, ADA disclaimer, sourcing model, etc. We need to include sections only when posting has real, specific content. So we need to extract content. Let's parse the posting: - Position Type Full time Type Of Hire Experienced (relevant combo of work and education) -> This is metadata; we can put in a short

maybe. - Job Description: paragraph about teams innovate etc. That's generic fluff but maybe we keep? It's part of description but not specific to role? It's generic company description. Might be considered boilerplate? It's not EEO but still generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This generic intro may be considered not boilerplate but maybe we keep as part of description? However they said "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro about innovating across finance, diversity, etc. Might be considered substantive? It's generic but still part of job description. I'd keep it as a

maybe before sections. - About The Role: content: "We are a group of professionals committed to helping our partner financial institutions reduce consumer fraud across their client base. Our primary goal is to improve consumer experience while minimizing exposure to fraud losses. Our team is currently looking for a Fraud Analytics Analyst to join our Fraud Transaction Monitoring Team. In this role, you will be responsible for data analytics including rule writing to prevent fraud as well as general performance reporting for the FIS Retail Digital Payment Products (Primarily Zelle and BillPay)." - About The Team: content: "The Digital Payments Fraud Analytics team is made up people who are passionate about reducing consumer fraud within our partner financial institution’s client base. Our primary goal is to maximize our financial institution’s consumer experience while simultaneously limiting exposure to fraud losses." - What You Will Be Doing: list: "Data/trend analysisFraud strategy and transaction monitoring rule developmentMaintaining existing fraud strategiesProcess improvementsCreate and maintain team reportingAd hoc data reporting". It appears as a run-on list without commas. We need to split into items. Likely each phrase separated by no punctuation. We'll need to parse: "Data/trend analysis", "Fraud strategy and transaction monitoring rule development", "Maintaining existing fraud strategies", "Process improvements", "Create and maintain team reporting", "Ad hoc data reporting". We'll make

• for each. - What You Bring: list: "Bachelor’s degree in relevant field of studyProficiency in Microsoft Office SuiteFluent in English; Strong written and verbal communication skillsAdaptability, a drive to learn, and strong problem-solving skillsAbility to work well independently and within a team". Need to split: "Bachelor’s degree in relevant field of study", "Proficiency in Microsoft Office Suite", "Fluent in English; Strong written and verbal communication skills", "Adaptability, a drive to learn, and strong problem-solving skills", "Ability to work well independently and within a team". We'll make
  . - Bonus If You Have: content: "Microsoft Excel skills are a must havePrior data analysis experienceSQL coding skills Python coding skills – not required, but nice to have". Need to split: "Microsoft Excel skills are a must have", "Prior data analysis experience", "SQL coding skills", "Python coding skills – not required, but nice to have". We'll make
  . - What We Offer You: content: "Competitive salary and excellent benefitsThe chance to work on some of the most challenging, relevant issues in financial services & technologyA broad range of professional education and personal development possibilities – FIS is your final career step!Time to support charities and give back to your communityA work environment built on collaboration, flexibility, and respectStudent Loan Repayment Program~ FIS will PAY OFF participants’ undergraduate loan balance over 10 years of service! Eligibility starts after one year of tenure in the program. The benefit applied to undergraduate student loans for US-based degrees and must be in the employee’s name. Current and future sponsorship are not available for this position*". Need to split into items: "Competitive salary and excellent benefits", "The chance to work on some of the most challenging, relevant issues in financial services & technology", "A broad range of professional education and personal development possibilities – FIS is your final career step!", "Time to support charities and give back to your community", "A work environment built on collaboration, flexibility, and respect", "Student Loan Repayment Program – FIS will PAY OFF participants’ undergraduate loan balance over 10 years of service! Eligibility starts after one year of tenure in the program. The benefit applied to undergraduate student loans for US-based degrees and must be in the employee’s name. Current and future sponsorship are not available for this position". We'll make
  . We also have Position Type Full time Type Of Hire Experienced (relevant combo of work and education). Could be a short

  at top: "Position Type: Full-time. Type of Hire: Experienced (relevant combination of work and education)." We need to avoid headings for metadata. So we can just have a

  with that. We must not include sections like Pay, Schedule, Benefits unless explicitly stated. Benefits are mentioned in "Competitive salary and excellent benefits" and also Student Loan Repayment Program. That's benefits. So we can have a Benefits section? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Benefits heading if we have benefits content. However they said "Prefer a few substantive sections over many thin ones." We already have a "What We Offer You" section which includes benefits. Could we rename that to Benefits? The instruction says use those headings as examples, not mandatory. We can keep "What We Offer You" as a heading? It's not in the list but it's okay as long as it's a heading. However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those standard headings where applicable. But we can also use other headings if they match content? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't forbid other headings, but to be safe we should map content to those headings. We have: - About the role -> matches "About The Role" - About the team -> maybe "About the team" not in list but could be considered similar to "About the role"? Not in list. Could we combine About the role and About the team under "About the role"? Might be thin. Better to keep separate but maybe use "About the team" as heading though not in list. The instruction says use those headings (e.g.) meaning those are examples, not exclusive. So we can use other headings as long as they are

  . I'd keep them. - What You Will Be Doing -> could be "Responsibilities". That's in list. So we should use

  Responsibilities

  . - What You Bring -> could be "Qualifications" or "Requirements". Use

  Qualifications

  . - Bonus If You Have -> could be "Skills". Use

  Skills

  . - What We Offer You -> could be "Benefits". Use

  Benefits

  . Thus we will output:

  Position Type: Full-time. Type of Hire: Experienced (relevant combination of work and education).

  Then maybe a

  with the introductory paragraph about innovating etc. That's generic but we keep. Then

  About the role

  with its paragraph(s). Then

  About the team

  with its paragraph. Then

  Responsibilities

  with
  • items. Then

    Qualifications

    with
    . Then

    Skills

    with
    . Then

    Benefits

    with
    . We must not include any boilerplate like privacy statement, EEOC, etc. Check for duplicated lines: none. Now ensure we preserve all substantive information: The introductory paragraph about innovating across finance, diversity, etc. We'll keep. Now format. We need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll escape any special characters? Not needed. We'll ensure proper nesting. Let's write:

    Position Type: Full-time. Type of Hire: Experienced (relevant combination of work and education).

    Every day, our teams innovate across the world of finance. We collaborate to work smarter, while making a difference. We believe in diversity and inclusivity, giving a voice to everyone on the team. And we celebrate our success together. If you want to make an impact in fintech, we’d like to know~ Are you FIS?

    Then sections. About the role paragraph: "We are a group of professionals committed to helping our partner financial institutions reduce consumer fraud across their client base. Our primary goal is to improve consumer experience while minimizing exposure to fraud losses. Our team is currently looking for a Fraud Analytics Analyst to join our Fraud Transaction Monitoring Team. In this role, you will be responsible for data analytics including rule writing to prevent fraud as well as general performance reporting for the FIS Retail Digital Payment Products (Primarily Zelle and BillPay)." About the team paragraph: "The Digital Payments Fraud Analytics team is made up people who are passionate about reducing consumer fraud within our partner financial institution’s client base. Our primary goal is to maximize our financial institution’s consumer experience while simultaneously limiting exposure to fraud losses." Responsibilities list items: - Data/trend analysis - Fraud strategy and transaction monitoring rule development - Maintaining existing fraud strategies - Process improvements - Create and maintain team reporting - Ad hoc data reporting Qualifications list: - Bachelor’s degree in relevant field of study - Proficiency in Microsoft Office Suite - Fluent in English; Strong written and verbal communication skills - Adaptability, a drive to learn, and strong problem-solving skills - Ability to work well independently and within a team Skills list: - Microsoft Excel skills are a must have - Prior data analysis experience - SQL coding skills - Python coding skills – not required, but nice to have Benefits list: - Competitive salary and excellent benefits - The chance to work on some of the most challenging, relevant issues in financial services & technology - A broad range of professional education and personal development possibilities – FIS is your final career step! - Time to support charities and give back to your community - A work environment built on collaboration, flexibility, and respect - Student Loan Repayment Program – FIS will PAY OFF participants’ undergraduate loan balance over 10 years of service! Eligibility starts after one year of tenure in the program. The benefit applied to undergraduate student loans for US-based