Senior Software Engineer, Internal Fraud Platform

We need to output HTML fragment with sections: About the role, Responsibilities, Desirable Skills, Knowledge, And Experience (maybe "Qualifications" or "Skills"), Benefits, maybe Compensation? The posting includes Compensation (Compensation may be adjusted depending on work location. Equity This role is eligible to participate in Cloudflare's equity plan.) That's compensation info. Also Benefits section present. Also maybe "About Us" but that's not a section heading we need? The instruction: 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. So we include headings for sections that have real specific content. We have: - About The Role (content after "About The Role") - Responsibilities (list) - Desirable Skills/Qualifications: "Desirable Skills, Knowledge, And Experience" (list) - Compensation (Compensation may be adjusted depending on work location. Equity This role is eligible to participate in Cloudflare's equity plan.) - Benefits (list of benefits) - Possibly "About Us" but not required; we can omit because not in list of headings? It's not required but could be included as "About Us"? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says use those for section headings. Probably we should stick to those. "About Us" is not needed; we can omit. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. So we need to extract the relevant paragraphs. Let's parse the posting: About Us: mission statement etc. Might be considered boilerplate? It's about company; could be considered substantive but not required heading. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid including About Us if we want, but we should follow the given examples. Safer to include only sections that match the examples and have content. Thus sections:

About the role

with paragraph(s) from "About The Role". Then

Responsibilities

with

• each bullet. Then

  Skills

  (or Qualifications) with list from "Desirable Skills, Knowledge, And Experience". Could label as Skills. Then

  Compensation

  with paragraph(s) about compensation and equity. Then

  Benefits

  with list of benefits. We must not include Pay or Schedule sections because not present. We need to preserve all substantive information: ensure we don't lose any details. Let's extract About The Role text: "About The Role Cloudflare's Internal Fraud Platform team is focused on protecting Cloudflare from fraud and abuse: fraudulent signups, promo and trial abuse, payment fraud, chargebacks, and account takeover that cost the company revenue and support overhead. Today the team is built around data science, developing the signals and models that detect this activity. We're hiring our first software engineer to build the platform around that work: ingesting events from the internal systems where fraud shows up (billing, signup, support), evaluating and routing them, and getting decisions and case data in front of the people who act on them. As the founding engineer on this team, you'll be the connective tissue between Cloudflare's internal systems and our fraud detection capabilities. You'll instrument the systems that generate fraud signals, build the pipelines and services that deliver those signals for evaluation, and create the tools our analysts use to investigate and resolve cases. You'll partner closely with data scientists to take models and heuristics from notebook to production, and have meaningful influence over the architecture, tooling, and engineering practices it's built on." We'll put that in

  . Responsibilities bullets: - Build the Platform: Design, build, and operate the services and pipelines that ingest fraud-relevant events from internal systems (billing, signup, support, and others), evaluate them, and route decisions and case data to the right destinations. - Deliver Signals for Scoring: Partner with the team's Data Scientists and Machine Learning Engineer to expose the event data and contextual features their models need, and integrate model decisions back into the pipelines and tools that act on them. - Build Investigation Tooling: Create the internal tools and workflows that let Trust & Safety, Support, and Finance analysts investigate flagged accounts and events and take action. - Own Projects End to End: Drive initiatives from problem definition through design, implementation, rollout, and operation with minimal oversight. In many ways this is a 0-to-1 team, and you'll be expected to fill in the gaps. - Ensure Accuracy and Reliability: Build fault-tolerant systems that handle retries, failures, and high event volumes without silently dropping or duplicating fraud signals, and maintain the operational health of what you ship, including addressing the root cause of recurring issues. - Shape Technical Direction: As one of the team's first engineers, help establish the architecture patterns, tooling choices, and engineering standards that will scale as the team grows. - Collaborate Cross-Functionally: Work with Trust & Safety, Data Science, Billing/Fintech, Support, and Product teams to understand fraud vectors and turn them into engineering requirements. We'll put each as

• . Skills list: - Five or more years of professional software engineering experience, or equivalent practical experience. - Experience building and operating distributed systems or backend services in production. - Experience designing and building data or event pipelines (e.g., Kafka, Pub/Sub, or similar). - Strong understanding of RESTful APIs, service security, and API standards such as OpenAPI, OAuth, or JWT. - Working knowledge of SQL, data modeling, and relational databases such as PostgreSQL or MySQL. - Comfort owning ambiguous, 0-to-1 problems with limited existing infrastructure or precedent. - Strong troubleshooting, cross-functional communication, and project ownership skills. - Bonus Points: - Experience in fraud, risk, trust & safety, or payments engineering. - Familiarity with ML serving and feature engineering concepts - Experience with billing, subscriptions, or other financial/transactional systems. - Experience building internal tools or dashboards for non-engineering stakeholders (analysts, support, finance). We need to keep bullet points; maybe treat "Bonus Points" as a subheading? But we can just include as items with note. We'll output as
  • ... etc. Compensation paragraph: "Compensation may be adjusted depending on work location. Equity This role is eligible to participate in Cloudflare's equity plan." We need to keep that exactly; maybe separate sentences: "Compensation may be adjusted depending on work location." "Equity This role is eligible to participate in Cloudflare's equity plan." Actually the text: "Compensation Compensation may be adjusted depending on work location. Equity This role is eligible to participate in Cloudflare's equity plan." There's a duplication of "Compensation". We'll keep as is but maybe fix duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The duplication is likely a typo in source; we should preserve it exactly? It says "Compensation Compensation may be adjusted depending on work location." That seems like a mistake but we must preserve it. We'll keep the exact text. Thus

    Compensation Compensation may be adjusted depending on work location. Equity This role is eligible to participate in Cloudflare's equity plan.

    Benefits: list of benefits as given. We need to extract the benefits section: "Benefits Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S. Health & Welfare Benefits Medical/Rx InsuranceDental InsuranceVision InsuranceFlexible Spending AccountsCommuter Spending AccountsFertility & Family Forming BenefitsOn-demand mental health support and Employee Assistance ProgramGlobal Travel Medical Insurance Financial Benefits Short and Long Term Disability InsuranceLife & Accident Insurance401(k) Retirement Savings PlanEmployee Stock Participation Plan Time Off Flexible paid time off covering vacation and sick leaveLeave programs, including parental, pregnancy health, medical, and bereavement leave" We need to format as list items. The text is jammed together; we need to split logically. We can create list items for each benefit: - Medical/Rx Insurance - Dental Insurance - Vision Insurance - Flexible Spending Accounts - Commuter Spending Accounts - Fertility & Family Forming Benefits - On-demand mental health support and Employee Assistance Program - Global Travel Medical Insurance - Short and Long Term Disability Insurance - Life & Accident Insurance - 401(k) Retirement Savings Plan - Employee Stock Participation Plan - Flexible paid time off covering vacation and sick leave - Leave programs, including parental, pregnancy health, medical, and bereavement leave Also there is introductory sentence: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." We can include that as a

    before the list. Thus Benefits section:

    Benefits

    Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S.

    • ...
    Now ensure we don't include any boilerplate like EEO etc. We removed. Now produce HTML fragment. Check that we didn't miss any substantive info: The "About Us" paragraph about mission etc. Not included; but it's not required heading; but maybe we should include as a paragraph without heading? The instruction says output ONLY the HTML fragment; we can include any content not under headings? It didn't forbid extra paragraphs; but better to stick to sections. The "About Us" is not under a heading we are using; we could include it as a

    before any heading? But then it's not under a heading; still okay. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings or paragraphs outside headings. But to be safe, we could include a brief intro paragraph without heading? Might be considered boilerplate? It's about company mission; maybe they want to keep it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Us is substantive. So we should include it. But where? Could be a

    before the first heading. There's no rule against that. We'll include a

    with the About Us content. Let's extract About Us text: "About Us At Cloudflare, we are on a mission to help build a better Internet. Today the company runs one of the world’s largest networks that powers millions of websites and other Internet properties for customers ranging from individual bloggers to SMBs to Fortune 500 companies. Cloudflare protects and accelerates any Internet application online without adding hardware, installing software, or changing a line of code. Internet properties powered by Cloudflare all have web traffic routed through its intelligent global network, which gets smarter with every request. As a result, they see significant improvement in performance and a decrease in spam and other attacks. Cloudflare was named to Entrepreneur Magazine’s Top Company Cultures list and ranked among the World’s Most Innovative Companies