Platform Integrity Operations Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We need to extract content from posting. First, there is a preamble about what we’re building and why, but that is not a section heading; we should not repeat job title. The posting includes sections: "About The Role", "Role Responsibilities", "Minimum Qualifications", "Preferred Qualifications", "What You’ll Bring", "Why This Role Matters", "Compensation", then benefits details. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: content under "About The Role". Use that. - Responsibilities: content under "Role Responsibilities". Use that. - Requirements: could be Minimum Qualifications? Or Requirements could be Minimum Qualifications. We'll treat Minimum Qualifications as Requirements. - Qualifications: maybe Preferred Qualifications as Qualifications? Or we could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have Minimum Qualifications (requirements) and Preferred Qualifications (maybe Qualifications). Also "What You’ll Bring" could be Skills? Might map to Skills. We also have "Why This Role Matters" - not in list; maybe we could omit or incorporate elsewhere? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We can include extra headings not in list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should stick to those. So we should not create headings like "Why This Role Matters". We could incorporate that content into About the role or Responsibilities? Probably better to incorporate into About the role or maybe omit if not fitting. But we must preserve ALL substantive information; we cannot drop content. So we need to embed that content somewhere within allowed sections. Could add a paragraph under About the role describing why role matters. Or we could create a separate section but not in allowed list? The instruction says use those headings for section headings (e.g...). It doesn't explicitly forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we should follow that pattern. It also says "include a section ONLY when the posting has real, specific content for it". So we can include any of those headings if we have content. We should not create other headings. Thus we need to map all content to those headings. We have: - About the role: includes description of what we’re building, role purpose, etc. Also includes "Why This Role Matters" maybe could be part of About the role. - Responsibilities: list of duties. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: "What You’ll Bring" maybe plus some skill aspects from other sections. - Benefits: details about compensation and benefits. - Pay: base salary range. - Schedule: mention full-time, remote/office. We need to ensure we don't repeat job title as heading. Not needed. We must not include boilerplate like EEO etc. Remove that. We must not include application instructions. We must preserve all substantive information. Let's extract content. First, About the role content: The paragraph starting "What we’re building and why we’re building it." Actually that is before About The Role. But we can treat that as part of About the role. The About The Role section begins: "Fetch is building the world’s most rewarding shopping experience, helping millions of consumers turn everyday purchases into value. As our platform grows, protecting the integrity of our ecosystem is critical to maintaining trust with users, partners, and the business. The Platform Integrity team is responsible for identifying, preventing, and responding to fraud, abuse, and other forms of misuse across Fetch’s platform. This work requires strong operational processes, clear policies and guidance, consistent enforcement, and close collaboration across Detection & Intelligence, Operations, Product Risk, Partner Trust, Product, Engineering, Data Science, Legal, Support, and Business teams. As the Platform Integrity Operations Coordinator, you will help strengthen the operational foundation that enables Platform Integrity teams to detect, assess, and respond to fraud consistently and at scale. You will develop and maintain clear SOPs and decision guidance, identify workflow gaps and inefficiencies, coordinate operational changes, and partner across teams to improve the quality, consistency, and scalability of fraud review. This role is ideal for someone with strong operations experience who is highly organized, writes clearly, and can turn complex or ambiguous processes into practical workflows that others can follow. You should be comfortable managing multiple workstreams, working cross-functionally, and using operational data and feedback to drive continuous improvement. This is a full-time role that can be held from one of our US offices or remotely in the United States." Then after that there is "Role Responsibilities" list. Then "Minimum Qualifications" list. Then "Preferred Qualifications" list. Then "What You’ll Bring" list. Then "Why This Role Matters" paragraph. Then "Compensation" paragraph with salary range and benefits. Then benefits details. We need to map: - About the role: combine the initial "What we’re building and why we’re building it." plus the About The Role paragraph plus maybe "Why This Role Matters". We'll include all that as prose under About the role. - Responsibilities: the bullet list under Role Responsibilities. - Requirements: Minimum Qualifications bullet list. - Qualifications: Preferred Qualifications bullet list. - Skills: What You’ll Bring bullet list (maybe also include some skill aspects from other sections but we can keep as is). - Benefits: the benefits paragraph after Compensation (including equity, 401k match, benefits for humans and pets, continuing education, ERGs, PTO, leave policies, Calvin Care Cash, flexible work environment). We'll put that under Benefits. - Pay: the base salary range sentence: "The base salary range for this position is $59,554-$70,064." - Schedule: mention full-time, remote/office: "This is a full-time role that can be held from one of our US offices or remotely in the United States." Also maybe mention flexible work environment but that's benefits. We'll put schedule info under Schedule. We must not include duplicated lines. Ensure we don't include boilerplate like EEO etc. Now produce HTML fragment: use

for each heading, then content:

for prose,

• for lists. We need to ensure we don't include any markdown fences. Let's craft. First heading:

  About the role

  Then paragraphs: combine the introductory paragraph and About The Role paragraph and Why This Role Matters. Introductory paragraph: "What we’re building and why we’re building it. Fetch helps people live rewarded every day, with a vision to become the rewards destination for everyone. We turn everyday activities into meaningful rewards, whether it’s grocery shopping, grabbing a quick meal, or playing a favorite mobile game. To date, we’ve awarded more than $1 billion in Fetch Points to our users. Each day, more than 13 million receipts are submitted on Fetch, providing visibility into over $212 billion in gross merchandise value. This creates the largest retail-agnostic, SKU-level view of household spending, powering Fetch as an outcomes-based advertising platform that helps brands acquire and retain lifelong consumers. The Fetch app is available on the App Store and Google Play, with more than 6 million five-star reviews from a highly engaged and loyal user base. It’s not just our users who believe in Fetch: with investments from Softbank, ICONIQ, DST, Greycroft, and partnerships ranging from challenger brands to Fortune 500 companies, Fetch is reshaping how brands and consumers connect in the marketplace. When you work at Fetch, you play a vital role in a platform that drives brand loyalty and creates lifelong consumers with the power of Fetch points. User and partner success are at the heart of everything we do, and we extend that same commitment to our employees. At Fetch, we value curiosity, adaptability, and the confidence to explore new tools, especially AI, to drive smarter, faster work. You don’t need to be an expert, but you should be ready to learn quickly and think critically. We welcome learners who move fast, challenge the status quo, and shape what’s next, with us. Ranked as one of America’s Best Startup Employers by Forbes for two years in a row, Fetch fosters a people-first culture rooted in trust, accountability, and innovation. We encourage our employees to challenge ideas, think bigger, and always bring the fun to Fetch." Then About The Role paragraph: "Fetch is building the world’s most rewarding shopping experience, helping millions of consumers turn everyday purchases into value. As our platform grows, protecting the integrity of our ecosystem is critical to maintaining trust with users, partners, and the business. The Platform Integrity team is responsible for identifying, preventing, and responding to fraud, abuse, and other forms of misuse across Fetch’s platform. This work requires strong operational processes, clear policies and guidance, consistent enforcement, and close collaboration across Detection & Intelligence, Operations, Product Risk, Partner Trust, Product, Engineering, Data Science, Legal, Support, and Business teams. As the Platform Integrity Operations Coordinator, you will help strengthen the operational foundation that enables Platform Integrity teams to detect, assess, and respond to fraud consistently and at scale. You will develop and maintain clear SOPs and decision guidance, identify workflow gaps and inefficiencies, coordinate operational changes, and partner across teams to improve the quality, consistency, and scalability of fraud review. This role is ideal for someone with strong operations experience who is highly organized, writes clearly, and can turn complex or ambiguous processes into practical workflows that others can follow. You should be comfortable managing multiple workstreams, working cross-functionally, and using operational data and feedback to drive continuous improvement. This is a full-time role that can be held from one of our US offices or remotely in the United States." Then Why This Role Matters paragraph: "Fraud prevention depends on more than identifying bad activity. It requires operational systems that help teams make accurate, consistent decisions at scale. The PI Operations Coordinator helps create that foundation by turning risk and operational needs into clear processes, documentation, and improvements that strengthen the quality and efficiency of fraud operations." We can combine into maybe two paragraphs: one for intro+about role, another for why role matters. But we can just put all as separate

  tags. Now Responsibilities:

  Responsibilities

  then
  with each bullet. List items: - Develop, document, and maintain PI operations processes, SOPs, decision guidance, and workflows for reviewing suspicious activity across user accounts, receipts, and other fraud vectors. - Write clear, concise operational documentation that translates complex processes into guidance that frontline teams and cross-functional partners can easily understand and apply. - Evaluate existing workflows to identify gaps, inefficiencies, inconsistencies, and opportunities for process, tooling, or automation improvements. - Use operational data, case trends, QA findings, and team feedback to recommend and implement process improvements. - Coordinate operational changes from planning through rollout, including stakeholder alignment, documentation updates, communications, training readiness, and post-launch follow-up. - Partner with PI Operations leaders, Training, QA, Product, Engineering, Data, Support, and other teams to resolve workflow issues, improve tooling, and ensure consistent execution. - Monitor key fraud operations metrics and surface trends, risks, or process issues that may require further investigation or action. - Support retrospectives, audits, and process reviews to evaluate whether operational changes are working