Staff Product Manager, Trust & Safety
Bumble Inc. · New York, NY · 3 wk ago
HybridMarketing$225k–$255k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Use for headings. Use
for headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to parse the posting.
First part: "About The Trust & Safety Team" is description of team. Could be considered "About the role"? Actually there is "About The Trust & Safety Team" then "About The Role". The "About The Role" includes description. We'll treat that as "About the role" section.
Then "What You’ll Do" is responsibilities. So we need a Responsibilities section with bullet list.
Then "About You" includes qualifications, requirements, skills. We need to split into Requirements, Qualifications, Skills maybe. The posting includes bullet-like paragraphs: "Product expertise 8+ years...", "Trust and Safety expertise...", "Data savvy...", "Technical fluency...", "Absolute ownership...", "Communication...", "Preferred Experience ...". So we can categorize: Requirements (must-have) maybe the first six bullet points; Preferred Experience as "Preferred Qualifications" or "Skills". But we need to follow instruction: Use sections only when posting has real specific content. We can create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present, so omit.
We need to preserve all substantive information. Not invent or summarize away detail. So we need to include all details from the posting.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Us", "AI Fluency", "Final Compensation", "Inclusion at Bumble Inc.", "AI in Bumble Inc. Hiring", "Fraudulent Candidate Detection", etc. Also remove "Benefits & Perks" content we need to keep as Benefits section. Also "Compensation Range: $225K - $255K" we need to include as Pay section.
We need to ensure we don't include headings like "About The Trust & Safety Team" maybe we can incorporate into About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not use other headings like "About The Trust & Safety Team". We should incorporate that content into About the role maybe. But we must preserve all substantive information. So we can include that team description inside About the role paragraph.
Thus About the role section will contain both the team description and the role description.
Let's extract:
About The Trust & Safety Team: "You’ll join a cross-functional Trust & Safety team that designs systems to prevent harm, protect members, and empower responders. We build scalable solutions that reduce risk and promote authentic, respectful interactions across our platforms. We believe safety is at the core of everything we build at Bumble Inc.—and we’re here to build it thoughtfully, proactively, and ethically."
About The Role: "We’re looking for a Staff Product Manager, Trust & Safety to help shape and scale the systems that keep our community safe, authentic, and empowered. You’ll lead high-impact initiatives across safety tooling, abuse prevention, content moderation, identity, and platform integrity. This role sits at the intersection of product, data science, engineering, policy, operations, and legal — balancing user experience with risk mitigation at global scale, and delivering outcomes that improve user trust, operational resilience, and safety at scale. If you’re passionate about building products that protect people, reduce harm, and promote healthy interactions — we’d love to meet you."
Combine into About the role paragraph.
Responsibilities (What You’ll Do): bullet list:
- Own and evolve the Trust & Safety product strategy and roadmap
- Lead roadmaps from ideation to implementation, including but not limited to abuse proactive and reactive detection, scam and fraud prevention, reporting, blocking, and moderation
- Partner with Engineering, Data Science, Design, Legal, and Operations to deliver high-quality, scalable solutions
- Define clear success metrics balancing safety, user experience, and business impact
- Use qualitative insights, behavioral data, and experimentation to inform product decisions
- Drive cross-functional alignment on policy implementation and risk mitigation strategies
- Champion user trust, transparency, and fairness in product decisions
We need to preserve each bullet exactly.
Now About You: we need to split into Requirements, Qualifications, Skills. The posting includes:
"Product expertise 8+ years of product management experience, including ownership of complex, cross-functional initiatives"
"Trust and Safety expertise Experience shipping products in areas such as Trust & Safety, platform integrity, risk, fraud, abuse prevention, moderation, or adjacent domains"
"Data savvy Strong analytical skills and fluency with experimentation, metrics, and data-driven decision-making"
"Technical fluency Experience working closely with engineering teams on technically complex systems, comfort working with infrastructure, ML models, and risk systems"
"Absolute ownership Experience defining product roadmaps E2E from ideation to execution, and ability to balance between short-term delivery and long-term vision, also between user experience, compliance, and risk mitigation"
"Communication Demonstrated ability to influence cross-functional stakeholders (Legal, Policy, Ops, Data Science), with excellent written and verbal communication skills"
"Preferred Experience Direct experience in social media, marketplace, UGC, or two-sided platform environmentsExperience working with machine learning models for detection, ranking, or classification systemsFamiliarity with global safety regulations (e.g., Online Safety Act, DSA, platform liability frameworks)Experience designing reporting, appeals, or enforcement workflowsBackground in building internal tools for moderation or operations teamsPassion for online safety, digital well-being, and building equitable platforms"
We need to decide which go to Requirements vs Qualifications vs Skills. Typically Requirements are must-have; Qualifications maybe education? Not present. Skills maybe technical skills. But we can just put all must-have under Requirements, and Preferred Experience under Skills or Qualifications. Since we have no explicit qualifications like degree, we could put Requirements as the first six bullet points, and Skills as the Preferred Experience bullet points (maybe also include some skills like ML models, etc). However we need to avoid creating thin sections; we can combine Requirements and Qualifications if they overlap. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we can have Requirements and Skills sections. Qualifications maybe not needed if no specific qualifications like degree. But we could treat Qualifications as same as Requirements? Safer to have Requirements and Skills only. But the instruction list includes Qualifications as possible heading; we can omit if no content.
Thus:
Requirements
with - for each of the six bullet points.
Skills
with - for each of the Preferred Experience bullet points.
Now Benefits: we have "Benefits & Perks" section with list:
- Insurance: Medical/dental/vision, 30-day eligibility. Bumble has multiple competitive offerings that will be available to you on the first of the month following date of hire.
- Unlimited PTO + 1 company-wide week off + Focus Fridays every week
- Fully paid life and long-term disability insurance
- 401k with 4% company match if you contribute 6%, 90-day eligibility
- Monthly wellness benefit and access to Noom, Unmind, and Your Money Line
- Maternity and Fertility benefit + 26 week paid parental leave
- Premium App Access
We need to preserve all substantive information. So we will output as
- each.
Pay: we have "Compensation Range: $225K - $255K". Also earlier "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we should not include filler like "commensurate with experience". The instruction says 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. The posting does state a compensation range, so we can include Pay section with that range. The earlier sentence about final compensation being determined based on factors is somewhat generic but still substantive? It's not a specific number; but we already have the range. We could include both sentences? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the sentence about final compensation being determined based on factors as well, as it's substantive. However it's somewhat generic but still part of posting. It's not placeholder like "commensurate with experience". It's a statement. So we can include it in Pay section as a paragraph.
Thus Pay section:
Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations.
plus maybe Compensation Range: $225K - $255K
. Could combine into one paragraph.
Schedule: not present, omit.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
We'll start with About the role
then ... combined team and role description.
Then Responsibilities
- ... etc.
Then
Requirements
- ... six items.
Then
Skills
- ... preferred experience items.
Then
Benefits
- ... benefits items.
Then
Pay
... compensation text.
Make sure to preserve punctuation and line breaks? Not needed.
Let's write the content exactly.
About the role paragraph:
"You’ll join a cross-functional Trust & Safety team that designs systems to prevent harm, protect members, and empower responders. We build scalable solutions that reduce risk and promote authentic, respectful interactions across our platforms. We believe safety is at the core of everything we build at Bumble Inc.—and we’re here to build it thoughtfully, proactively, and ethically. We’re looking for a Staff Product Manager, Trust & Safety to help shape and scale the systems that keep our community safe, authentic, and empowered. You’ll lead high-impact initiatives across safety tooling, abuse prevention, content moderation, identity, and platform integrity. This role sits at the intersection of product, data science, engineering, policy, operations, and legal — balancing user experience with risk mitigation at global scale, and delivering outcomes that improve user trust, operational resilience, and safety at scale. If you’re passionate about building products that protect people, reduce harm, and promote healthy interactions — we’d love to meet you."
Check for any duplicated lines: none.
Now Responsibilities bullets exactly as given:
- Own and evolve the Trust & Safety product strategy and roadmap
- Lead roadmaps from ideation to implementation, including but not limited to abuse proactive and reactive detection, scam and fraud prevention, reporting, blocking, and moderation
- Partner with Engineering, Data Science, Design, Legal, and Operations to deliver high-quality, scalable solutions
- Define clear success metrics balancing safety, user experience, and business impact
- Use qualitative insights, behavioral data, and experimentation to inform product decisions
- Drive cross-functional alignment on policy implementation and risk mitigation strategies
- Champion user trust, transparency, and fairness in product decisions
Now Requirements bullets (six):
- Product expertise 8+ years of product management experience, including ownership of complex, cross-functional initiatives
- Trust and Safety expertise Experience shipping products in areas such as Trust & Safety, platform integrity, risk, fraud, abuse prevention, moderation, or adjacent domains
- Data savvy Strong analytical skills and fluency with
for prose. We need to parse the posting. First part: "About The Trust & Safety Team" is description of team. Could be considered "About the role"? Actually there is "About The Trust & Safety Team" then "About The Role". The "About The Role" includes description. We'll treat that as "About the role" section. Then "What You’ll Do" is responsibilities. So we need a Responsibilities section with bullet list. Then "About You" includes qualifications, requirements, skills. We need to split into Requirements, Qualifications, Skills maybe. The posting includes bullet-like paragraphs: "Product expertise 8+ years...", "Trust and Safety expertise...", "Data savvy...", "Technical fluency...", "Absolute ownership...", "Communication...", "Preferred Experience ...". So we can categorize: Requirements (must-have) maybe the first six bullet points; Preferred Experience as "Preferred Qualifications" or "Skills". But we need to follow instruction: Use sections only when posting has real specific content. We can create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present, so omit. We need to preserve all substantive information. Not invent or summarize away detail. So we need to include all details from the posting. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Us", "AI Fluency", "Final Compensation", "Inclusion at Bumble Inc.", "AI in Bumble Inc. Hiring", "Fraudulent Candidate Detection", etc. Also remove "Benefits & Perks" content we need to keep as Benefits section. Also "Compensation Range: $225K - $255K" we need to include as Pay section. We need to ensure we don't include headings like "About The Trust & Safety Team" maybe we can incorporate into About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not use other headings like "About The Trust & Safety Team". We should incorporate that content into About the role maybe. But we must preserve all substantive information. So we can include that team description inside About the role paragraph.
Thus About the role section will contain both the team description and the role description.
Let's extract:
About The Trust & Safety Team: "You’ll join a cross-functional Trust & Safety team that designs systems to prevent harm, protect members, and empower responders. We build scalable solutions that reduce risk and promote authentic, respectful interactions across our platforms. We believe safety is at the core of everything we build at Bumble Inc.—and we’re here to build it thoughtfully, proactively, and ethically."
About The Role: "We’re looking for a Staff Product Manager, Trust & Safety to help shape and scale the systems that keep our community safe, authentic, and empowered. You’ll lead high-impact initiatives across safety tooling, abuse prevention, content moderation, identity, and platform integrity. This role sits at the intersection of product, data science, engineering, policy, operations, and legal — balancing user experience with risk mitigation at global scale, and delivering outcomes that improve user trust, operational resilience, and safety at scale. If you’re passionate about building products that protect people, reduce harm, and promote healthy interactions — we’d love to meet you."
Combine into About the role paragraph.
Responsibilities (What You’ll Do): bullet list:
- Own and evolve the Trust & Safety product strategy and roadmap
- Lead roadmaps from ideation to implementation, including but not limited to abuse proactive and reactive detection, scam and fraud prevention, reporting, blocking, and moderation
- Partner with Engineering, Data Science, Design, Legal, and Operations to deliver high-quality, scalable solutions
- Define clear success metrics balancing safety, user experience, and business impact
- Use qualitative insights, behavioral data, and experimentation to inform product decisions
- Drive cross-functional alignment on policy implementation and risk mitigation strategies
- Champion user trust, transparency, and fairness in product decisions
We need to preserve each bullet exactly.
Now About You: we need to split into Requirements, Qualifications, Skills. The posting includes:
"Product expertise 8+ years of product management experience, including ownership of complex, cross-functional initiatives"
"Trust and Safety expertise Experience shipping products in areas such as Trust & Safety, platform integrity, risk, fraud, abuse prevention, moderation, or adjacent domains"
"Data savvy Strong analytical skills and fluency with experimentation, metrics, and data-driven decision-making"
"Technical fluency Experience working closely with engineering teams on technically complex systems, comfort working with infrastructure, ML models, and risk systems"
"Absolute ownership Experience defining product roadmaps E2E from ideation to execution, and ability to balance between short-term delivery and long-term vision, also between user experience, compliance, and risk mitigation"
"Communication Demonstrated ability to influence cross-functional stakeholders (Legal, Policy, Ops, Data Science), with excellent written and verbal communication skills"
"Preferred Experience Direct experience in social media, marketplace, UGC, or two-sided platform environmentsExperience working with machine learning models for detection, ranking, or classification systemsFamiliarity with global safety regulations (e.g., Online Safety Act, DSA, platform liability frameworks)Experience designing reporting, appeals, or enforcement workflowsBackground in building internal tools for moderation or operations teamsPassion for online safety, digital well-being, and building equitable platforms"
We need to decide which go to Requirements vs Qualifications vs Skills. Typically Requirements are must-have; Qualifications maybe education? Not present. Skills maybe technical skills. But we can just put all must-have under Requirements, and Preferred Experience under Skills or Qualifications. Since we have no explicit qualifications like degree, we could put Requirements as the first six bullet points, and Skills as the Preferred Experience bullet points (maybe also include some skills like ML models, etc). However we need to avoid creating thin sections; we can combine Requirements and Qualifications if they overlap. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we can have Requirements and Skills sections. Qualifications maybe not needed if no specific qualifications like degree. But we could treat Qualifications as same as Requirements? Safer to have Requirements and Skills only. But the instruction list includes Qualifications as possible heading; we can omit if no content.
Thus:
Requirements
with - for each of the six bullet points.
Skills
with - for each of the Preferred Experience bullet points.
Now Benefits: we have "Benefits & Perks" section with list:
- Insurance: Medical/dental/vision, 30-day eligibility. Bumble has multiple competitive offerings that will be available to you on the first of the month following date of hire.
- Unlimited PTO + 1 company-wide week off + Focus Fridays every week
- Fully paid life and long-term disability insurance
- 401k with 4% company match if you contribute 6%, 90-day eligibility
- Monthly wellness benefit and access to Noom, Unmind, and Your Money Line
- Maternity and Fertility benefit + 26 week paid parental leave
- Premium App Access
We need to preserve all substantive information. So we will output as
- each.
Pay: we have "Compensation Range: $225K - $255K". Also earlier "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we should not include filler like "commensurate with experience". The instruction says 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. The posting does state a compensation range, so we can include Pay section with that range. The earlier sentence about final compensation being determined based on factors is somewhat generic but still substantive? It's not a specific number; but we already have the range. We could include both sentences? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the sentence about final compensation being determined based on factors as well, as it's substantive. However it's somewhat generic but still part of posting. It's not placeholder like "commensurate with experience". It's a statement. So we can include it in Pay section as a paragraph.
Thus Pay section:
Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations.
plus maybe Compensation Range: $225K - $255K
. Could combine into one paragraph.
Schedule: not present, omit.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
We'll start with About the role
then ... combined team and role description.
Then Responsibilities
- ... etc.
Then
Requirements
- ... six items.
Then
Skills
- ... preferred experience items.
Then
Benefits
- ... benefits items.
Then
Pay
... compensation text.
Make sure to preserve punctuation and line breaks? Not needed.
Let's write the content exactly.
About the role paragraph:
"You’ll join a cross-functional Trust & Safety team that designs systems to prevent harm, protect members, and empower responders. We build scalable solutions that reduce risk and promote authentic, respectful interactions across our platforms. We believe safety is at the core of everything we build at Bumble Inc.—and we’re here to build it thoughtfully, proactively, and ethically. We’re looking for a Staff Product Manager, Trust & Safety to help shape and scale the systems that keep our community safe, authentic, and empowered. You’ll lead high-impact initiatives across safety tooling, abuse prevention, content moderation, identity, and platform integrity. This role sits at the intersection of product, data science, engineering, policy, operations, and legal — balancing user experience with risk mitigation at global scale, and delivering outcomes that improve user trust, operational resilience, and safety at scale. If you’re passionate about building products that protect people, reduce harm, and promote healthy interactions — we’d love to meet you."
Check for any duplicated lines: none.
Now Responsibilities bullets exactly as given:
- Own and evolve the Trust & Safety product strategy and roadmap
- Lead roadmaps from ideation to implementation, including but not limited to abuse proactive and reactive detection, scam and fraud prevention, reporting, blocking, and moderation
- Partner with Engineering, Data Science, Design, Legal, and Operations to deliver high-quality, scalable solutions
- Define clear success metrics balancing safety, user experience, and business impact
- Use qualitative insights, behavioral data, and experimentation to inform product decisions
- Drive cross-functional alignment on policy implementation and risk mitigation strategies
- Champion user trust, transparency, and fairness in product decisions
Now Requirements bullets (six):
- Product expertise 8+ years of product management experience, including ownership of complex, cross-functional initiatives
- Trust and Safety expertise Experience shipping products in areas such as Trust & Safety, platform integrity, risk, fraud, abuse prevention, moderation, or adjacent domains
- Data savvy Strong analytical skills and fluency with
Skills
with- for each of the Preferred Experience bullet points.
Now Benefits: we have "Benefits & Perks" section with list:
- Insurance: Medical/dental/vision, 30-day eligibility. Bumble has multiple competitive offerings that will be available to you on the first of the month following date of hire.
- Unlimited PTO + 1 company-wide week off + Focus Fridays every week
- Fully paid life and long-term disability insurance
- 401k with 4% company match if you contribute 6%, 90-day eligibility
- Monthly wellness benefit and access to Noom, Unmind, and Your Money Line
- Maternity and Fertility benefit + 26 week paid parental leave
- Premium App Access
We need to preserve all substantive information. So we will output as
- each.
Pay: we have "Compensation Range: $225K - $255K". Also earlier "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we should not include filler like "commensurate with experience". The instruction says 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. The posting does state a compensation range, so we can include Pay section with that range. The earlier sentence about final compensation being determined based on factors is somewhat generic but still substantive? It's not a specific number; but we already have the range. We could include both sentences? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the sentence about final compensation being determined based on factors as well, as it's substantive. However it's somewhat generic but still part of posting. It's not placeholder like "commensurate with experience". It's a statement. So we can include it in Pay section as a paragraph.
Thus Pay section:
Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations.
plus maybeCompensation Range: $225K - $255K
. Could combine into one paragraph. Schedule: not present, omit. Now we need to output only HTML fragment, no /, no markdown. Let's craft. We'll start withAbout the role
then... combined team and role description.
ThenResponsibilities
- ... etc.
Then
Requirements
- ... six items.
Then
Skills
- ... preferred experience items.
Then
Benefits
- ... benefits items.
Then
Pay
... compensation text.
Make sure to preserve punctuation and line breaks? Not needed. Let's write the content exactly. About the role paragraph: "You’ll join a cross-functional Trust & Safety team that designs systems to prevent harm, protect members, and empower responders. We build scalable solutions that reduce risk and promote authentic, respectful interactions across our platforms. We believe safety is at the core of everything we build at Bumble Inc.—and we’re here to build it thoughtfully, proactively, and ethically. We’re looking for a Staff Product Manager, Trust & Safety to help shape and scale the systems that keep our community safe, authentic, and empowered. You’ll lead high-impact initiatives across safety tooling, abuse prevention, content moderation, identity, and platform integrity. This role sits at the intersection of product, data science, engineering, policy, operations, and legal — balancing user experience with risk mitigation at global scale, and delivering outcomes that improve user trust, operational resilience, and safety at scale. If you’re passionate about building products that protect people, reduce harm, and promote healthy interactions — we’d love to meet you." Check for any duplicated lines: none. Now Responsibilities bullets exactly as given: - Own and evolve the Trust & Safety product strategy and roadmap - Lead roadmaps from ideation to implementation, including but not limited to abuse proactive and reactive detection, scam and fraud prevention, reporting, blocking, and moderation - Partner with Engineering, Data Science, Design, Legal, and Operations to deliver high-quality, scalable solutions - Define clear success metrics balancing safety, user experience, and business impact - Use qualitative insights, behavioral data, and experimentation to inform product decisions - Drive cross-functional alignment on policy implementation and risk mitigation strategies - Champion user trust, transparency, and fairness in product decisions Now Requirements bullets (six): - Product expertise 8+ years of product management experience, including ownership of complex, cross-functional initiatives - Trust and Safety expertise Experience shipping products in areas such as Trust & Safety, platform integrity, risk, fraud, abuse prevention, moderation, or adjacent domains - Data savvy Strong analytical skills and fluency with
- ... benefits items.
Then
- ... preferred experience items.
Then
- ... six items.
Then
- ... etc.
Then
- each.
Pay: we have "Compensation Range: $225K - $255K". Also earlier "Final Compensation Will be determined based on factors such as the selected candidate’s qualifications, relevant experience, skill set, and other job-related considerations." That's generic; we should not include filler like "commensurate with experience". The instruction says 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. The posting does state a compensation range, so we can include Pay section with that range. The earlier sentence about final compensation being determined based on factors is somewhat generic but still substantive? It's not a specific number; but we already have the range. We could include both sentences? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the sentence about final compensation being determined based on factors as well, as it's substantive. However it's somewhat generic but still part of posting. It's not placeholder like "commensurate with experience". It's a statement. So we can include it in Pay section as a paragraph.
Thus Pay section: