Group Product Manager, Grocery & Retail Selection

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - About The Role: paragraph describing role, charters, team, etc. - What The Candidate Will Do: bullet list? Actually it's a paragraph with bullet-like lines? It says: "Experience working with data ingestion systems, APIs, integration platforms, or canonical data models. Experience with marketplace, e-commerce, or catalog/menu systems. Track record of improving system reliability, detection systems, or risk mitigation frameworks. Experience driving strategy for business growth Strong executive communication skills with the ability to influence senior stakeholders." This is a list of qualifications/experience. Could be considered "Requirements" or "Qualifications". We'll need to decide sections. - Basic Qualifications: paragraph: "As we scale Uber Eats globally, your mission is to make it effortless for any merchant to get and maintain their catalog on Uber in the most optimized, compliant, and reliable way possible." Then "Here Are Some Of The Areas You'll Work On" then bullet list: "Define and drive the multi-year vision and strategy for Selection, spanning ingestion method platform, interpretation, and reliability. Bachelor's degree or equivalent Lead and develop a team of 8 PMs, clarifying ownership across charters and elevating product rigor and execution quality. Reduce integration cost and complexity by standardizing APIs, POS integrations, feed ingestion, and mapping/configuration systems. Improve merchant-facing tooling and workflows to simplify catalog setup, bulk updates, and ongoing maintenance. Establish clear structural representation standards for merchants at ingestion and build proactive configuration and compliance guardrails that prevent invalid, un-orderable, or risky catalog states. Evolve catalog health from reactive detection to predictive, automated protection with intelligent staging, blocking, and rollback systems. Tie reliability signals directly to business impact, improving precision/recall while reducing catalog-related incidents and operational load." Note: The bullet list seems to have some formatting issues: "Bachelor's degree or equivalent" appears as a separate bullet? Actually it's part of list but missing bullet. We'll treat each line as a bullet. - Preferred Qualifications: bullet list: "8+ years of product management experience, including ownership of complex, technical platform systems. Proven experience managing and developing product managers. Strong analytical and systems-thinking skills, with the ability to connect technical decisions to business impact. Demonstrated ability to lead cross-functional initiatives across engineering, data science, and operations. A bias for action and ownership, you're comfortable working through ambiguity to get to impactful outcomes" - Then salary info: For New York City, NY-based roles: The base salary range for this role is USD $252,000 per year - USD $280,000 per year. For San Francisco, CA-based roles: The base salary range for this role is USD $252,000 per year - USD $280,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. - Then "Ready to Ride?" paragraph etc. That's fluff, maybe not needed? It's not substantive? It's motivational. Could be considered part of About the role? But we should preserve substantive information; not fluff? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "Ready to Ride?" is fluff but still part of posting. However we can consider it as not essential? It's not a list of duties/requirements/benefits. It's more marketing. Might be considered boilerplate? Not exactly EEO. It's not navigation/legal. It's not duplicated lines. It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It's not application instructions. It's not duplicated lines. It's not "Explore our benefits." Actually there is "Explore our benefits." That's a call to action. Might be considered application instruction? It's not exactly instruction to apply, but it's a prompt. The instruction says remove application instructions. "Explore our benefits." could be considered a call to action, maybe remove. Also "Ready to Ride? This isn't the kind of place where you follow a playbook - it's where you help write one. If you're driven by impact, energized by challenge, and ready to shape how the world moves - we'd love to hear from you." That's also fluff/marketing. Might be considered not substantive? It's not about role duties. I'd lean to remove it as it's not substantive info about role, responsibilities, qualifications, benefits, pay, schedule. It's more marketing fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. This is not substantive? It's not required for understanding the role. It's more like a tagline. I'd remove it. - Then "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." That's schedule/location info. This is substantive about schedule (in-office requirement). So we should include a Schedule section with that info. - Then EEO boilerplate etc. Remove. Thus sections we need: - About the role: from "About The Role" paragraph(s). Could combine the initial description and maybe "What The Candidate Will Do"? Actually "What The Candidate Will Do" is more like responsibilities/experience needed. Could be placed under Responsibilities or Requirements. Let's decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: The initial paragraph describing role, charters, team, etc. That's about the role. Responsibilities: Could be the "What The Candidate Will Do" list (experience working with data ingestion systems...). Also maybe the "Here Are Some Of The Areas You'll Work On" list under Basic Qualifications? Actually that list seems like responsibilities/duties. But Basic Qualifications heading is weird; it's more like responsibilities. However we have a separate "Basic Qualifications" heading in the posting. That heading is not one of our allowed headings? We have Qualifications. So we could treat "Basic Qualifications" as Qualifications section. But the content under Basic Qualifications includes both a mission statement and a list of areas you'll work on (which are responsibilities). The "Preferred Qualifications" is separate. We need to avoid thin sections. Perhaps combine. Let's think: The posting has: - About The Role (description) - What The Candidate Will Do (list of experience/skills) - Basic Qualifications (mission + list of areas you'll work on) - Preferred Qualifications (list) - Salary/Pay info - Benefits info (401k, various benefits) - Schedule info (in-office requirement) - EEO etc (remove) Thus we can map: - About the role: the About The Role paragraph. - Responsibilities: maybe the "What The Candidate Will Do" list (experience). But that's more like qualifications/experience needed. However we could treat that as Responsibilities (what you will do). Actually the heading "What The Candidate Will Do" suggests responsibilities. So we can put that under Responsibilities. - Requirements: maybe the "Basic Qualifications" mission statement? Or we could treat Basic Qualifications as Requirements (like bachelor's degree or equivalent). But the list under Basic Qualifications includes duties. Hmm. - Qualifications: maybe the Preferred Qualifications list. - Skills: maybe we could extract skills from the lists (like data ingestion systems, APIs, etc.) but we already have them in Responsibilities/Requirements. - Benefits: the paragraph about bonus program, equity award, 401k, various benefits. - Pay: the salary range info. - Schedule: the in-office requirement. We need to avoid thin sections. If we have too many sections with little content, we should combine. The instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 4-5 sections. We could combine About the role and Responsibilities into one section? But we need headings for each section we include. If we combine, we need to decide which heading to use. Perhaps we can have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's 6 sections. Might be okay if each has substantive content. But we need to ensure we don't create sections with filler like "commensurate with experience". We have real content. Let's extract content precisely. **About The Role** paragraph: "As the Group Product Manager for Grocery & Retail Selection, you will own the strategy, roadmap, and execution for growing merchant and item selection to be delivered on the Uber Eats platform. This starts with merchant onboarding, is maximized through catalog quality and health, and refined with the addition of new item types. Catalogs power every consumer purchase decision. When they are inaccurate, poorly structured, or unreliable, we create revenue loss, operational friction, and merchant frustration. This team sits at the critical boundary where merchant data enters Uber, and is accountable for ensuring that data is correctly represented, validated, optimized, and protected before it reaches the marketplace. This is a high-impact leadership role responsible for three core charters: Merchant Selection & Onboarding: How Uber can onboard as much valuable selection as possible Ingestion Platform, Tooling & Optimization: How merchant data enters Uber through APIs, POS integrations, feeds, and merchant-facing tools. How merchant intent is structurally represented within Uber's canonical model at ingestion, and how we enable performance uplift while preserving merchant autonomy. Catalog Reliability & Protection: How we detect, prevent, and mitigate catalog-related business risk through intelligent monitoring, regression detection, and protective automation. You will lead a team of 8 PMs with the opportunity to grow the team. You will be partnering closely with Engineering, Data Science, Merchant Operations, and Consumer teams. Your mandate is to evolve from a data pipeline into an intelligent, self-protecting, growth-enabling system that makes selection and catalog integrity a competitive advantage for Uber Eats." That's substantive. **What The Candidate Will Do** (list): - Experience working with data ingestion systems, APIs, integration platforms, or canonical data models. - Experience with marketplace, e-commerce, or catalog/menu systems. - Track record of improving system reliability, detection systems, or risk mitigation frameworks. - Experience driving strategy for business growth - Strong executive communication skills with the ability to influence senior stakeholders. Note: The last line missing period but okay. **Basic Qualifications** paragraph: "As we scale Uber Eats globally, your mission is to make it effortless for any merchant to get and maintain their catalog on Uber in the most optimized, compliant, and reliable way possible." Then "Here Are Some Of The Areas You'll Work On" list: - Define and drive the multi-year vision and strategy for Selection, spanning ingestion method platform, interpretation, and reliability. - Bachelor