Sr Product Manager - Enterprise Risk

We need to output HTML fragment with sections: About the role (maybe heading "About the role"), Responsibilities (maybe "What The Candidate Will Do"), Requirements (maybe "Basic Qualifications" and "Preferred Qualifications" combined?), Benefits, Pay, Schedule. Must include only sections with real content. We have content: About The Role paragraph(s). Responsibilities: bullet list under "What The Candidate Will Do". Requirements: Basic Qualifications list, Preferred Qualifications list. Also extra notes about experience. Benefits: mention "eligible to participate in Uber's bonus program, may be offered an equity award & other types of comp. All full-time employees are eligible to participate in a 401(k) plan. You will also be eligible for various benefits." Also "Explore our benefits." So we can include Benefits section with those details. Pay: salary ranges for SF and Sunnyvale: USD $190,000 - $211,000 per year. Also mention bonus program, equity award. So Pay section. Schedule: mention "Offices remain key to collaboration... Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles... require full-time in-office presence." So schedule info. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info, not invent or summarize away detail. Must not include filler like "commensurate with experience". Not present. We need to decide sections: About the role, Responsibilities, Requirements (maybe split into Basic Qualifications and Preferred Qualifications? Could combine under Requirements with two sublists? But spec says use

  for section headings; we could have separate headings for Basic Qualifications and Preferred Qualifications, but they'd be under Requirements? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have headings like About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Qualifications maybe not needed. We'll put Requirements heading and inside we can have two

  lists: one for Basic Qualifications, one for Preferred Qualifications. Or we could have separate headings Basic Qualifications and Preferred Qualifications but they are not in the list; but they could be considered subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. We'll use Requirements heading and inside we can have

  for intro then two

  lists with maybe labels? But we must not invent filler. We can just list items; we can precede each list with a

  like "Basic Qualifications:" but that's extra text not in original? It's okay as it's directly from the posting. The original has headings "Basic Qualifications" and "Preferred Qualifications". We could treat those as headings too, but they are not in the example list; but they are still headings. 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 use other headings, but to be safe we could treat Basic Qualifications and Preferred Qualifications as

  ? Not allowed? Probably better to keep them as

  as they are section headings. The examples are not exhaustive. So we can have headings: About the role, What The Candidate Will Do (maybe Responsibilities), Basic Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. That seems fine. We must not repeat job title as heading. So we won't. Now produce HTML fragment. Let's extract content. About The Role: paragraphs: "Uber's Risk team is critical to enabling trusted growth across our global marketplace by preventing fraud and abuse while minimizing friction for legitimate users. Enterprise (B2B) accounts are a major and fast-growing part of that marketplace, and managing their risk is one of the most structurally complex domains in Payment Risk. In this senior, high-impact individual contributor role, the Product Manager for Enterprise & Payment Risk will own the full risk lifecycle of B2B entities at scale - from onboarding and information acquisition, through manual review processes, to real-time risk decisioning at checkout and payment. The role also owns the underlying account and billing infrastructure that enterprise risk decisions run on, and the recovery/verification experiences enterprise customers rely on when something goes wrong. A defining challenge of this role is that the enterprise customer base spans many distinct cohorts, each with a different risk tolerance and a different sensitivity to friction and actioning. Success requires calibrating risk treatment differently across these cohorts rather than applying a single, one-size-fits-all policy - balancing fraud prevention against growth and satisfaction for legitimate business customers. This is the most stakeholder-intensive scope in the Payment Risk organization, requiring close, sustained partnership with business/BD leadership in addition to Engineering, Data Science, and platform teams. This position is ideal for a senior product leader who thrives in ambiguous, high-stakes problem spaces, has strong command of B2B/enterprise payment or billing systems, and can drive outcomes through influence across a large and often-competing set of stakeholders and shared engineering capacity." We'll put that in

  . Responsibilities: bullet list under "What The Candidate Will Do". Items: - Own the B2B entity risk lifecycle end-to-end at scale: onboarding and information acquisition, manual review workflows, and real-time risk decisioning at checkout and payment. - Segment and calibrate risk policy across distinct enterprise customer cohorts, each with different risk tolerance and sensitivity to friction/actioning. - Define the product requirements and roadmap for enterprise risk capabilities, including underlying account and billing infrastructure modernization and its associated cross-functional dependencies. - Own recovery and verification experiences for enterprise customers, including fallback challenges, admin verification, and cross-party messaging. - Partner with Engineering and Data Science to scope and land payment authorization and decisioning improvements against concrete loss-reduction targets. - Triage, prioritize, and negotiate a high volume of cross-functional dependency requests against shared and constrained engineering capacity. - Build and maintain trusted relationships with business/BD stakeholders, translating enterprise account needs into a risk product roadmap. - Measure impact using well-defined KPIs (e.g., loss-rate reduction, authorization effectiveness, dispute/chargeback rates) and iterate based on learnings. - Coordinate with Risk Operations, Risk Governance/Compliance, and payments platform teams to ensure solutions are practical, compliant, and operationally sound. We'll put each as

  . Requirements: Basic Qualifications list: - 8+ years of product management experience delivering software products as an individual contributor in a technology company. - Experience owning a complex, technically deep product domain (e.g., payments, billing, risk, or platform infrastructure) with significant stakeholder breadth. - Strong analytical skills and comfort using data to inform decisions and measure impact. - Clear written and verbal communication skills, with the ability to explain complex problems simply to both technical and business audiences. - Proven ability to work cross-functionally with Engineering, Data Science, Business/BD, Design, and Operations, including negotiating priority against shared/constrained resources. - Bachelor's degree in Computer Science, Engineering, Data/Analytics, or a related quantitative field (or equivalent experience). Preferred Qualifications list: - Risk & Fraud Domain Expertise - Experience in risk, fraud, or trust & safety within a B2B/enterprise or multi-sided marketplace, particularly billing risk, checkout/payment decisioning, or auth-hold systems. - B2B/Enterprise Product Ownership - Prior ownership of a product serving business or organizational accounts (rather than purely consumer-facing products), including billing configuration, credit management, or account administration. - Business Acumen - Demonstrated ability to drive P&L improvements through loss reduction or account-health initiatives, with strong intuition for how risk interventions affect the broader business. - Strategic Judgment - Strong product instincts for navigating ambiguous, structurally complex problem spaces and balancing competing constraints across risk, business, engineering capacity, and compliance. - Advanced Business Education - MBA or equivalent business experience. - Extra notes: Prefer candidates with prior experience in engineering, data scientist, consulting, finance, or a B2B/enterprise SaaS product role before moving into PM, given the domain's billing/payments complexity. We could include extra notes as a separate bullet. Benefits: content: - For San Francisco, CA-based roles: The base salary range for this role is USD $190,000 per year - USD $211,000 per year. For Sunnyvale, CA-based roles: The base salary range for this role is USD $190,000 per year - USD $211,000 per year. For all US locations, you will be eligible to participate in Uber's bonus program, and may be offered an equity award & other types of comp. All full-time employees are eligible to participate in a 401(k) plan. You will also be eligible for various benefits. Also "Explore our benefits." and "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." We'll combine. Pay section: maybe we separate Pay from Benefits? The instruction says include Pay and Benefits sections only if posting actually states them. It does state salary range and bonus etc. So we can have Pay section with salary ranges and bonus/equity. Benefits section with 401(k) and various benefits. Schedule: content: "Offices remain key to collaboration and Uber's culture. Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles, like those at greenlight hubs, require full-time in-office presence. Ask your Recruiter for details about this role's requirements." We'll put that. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Basic Qualifications

  ...

  Preferred Qualifications

  ...

  Benefits

  ...

  Pay

  ...

  Schedule

  ...

  Check for any boilerplate: we removed EEO, equal opportunity, scam warning, navigation, cookie, application instructions, "Ready to Ride?" etc. Also removed "Explore our benefits." maybe it's okay as it's part of benefits but could be considered boilerplate? It's a call to action; but it's not EEO. Might be okay to keep. However it's somewhat generic; but it's part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "Explore our benefits." is not exactly those; it's a call to action but could be considered application instruction? It's not exactly instruction to apply. It's more like a link. Might be safe to keep. But we could drop it as it's not substantive. Safer to drop. We'll keep substantive benefits description. Also "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." is similar to benefits; we can incorporate. Let's craft Benefits paragraph: "All full-time employees are eligible to participate in a 401(k) plan. You will also be eligible for various benefits, including eligibility for Uber's bonus program and potential equity awards." Pay paragraph: "For San Francisco, CA-based roles and Sunnyvale, CA-based roles, the base salary range is USD $190,000