Product Manager II, Agentic AI

We need to output HTML fragment only, with headings

for 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. No Job ID etc. Remove boilerplate. We need to parse the posting. Sections present: - About The Team (but we only use headings like About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. "About The Team" maybe not needed; we could treat as part of About the role? Actually "About The Role" is present. So we will have

About the role

with content from "About The Role" paragraph(s). Also we have "What You'll Do" which is responsibilities. So

Responsibilities

with bullet list of duties. We have "Basic Qualifications" and "Preferred Qualifications". Those map to Requirements and Qualifications? Possibly Basic Qualifications = Requirements, Preferred Qualifications = Qualifications or Skills? The instruction list includes Requirements, Qualifications, Skills. We can decide: Basic Qualifications -> Requirements. Preferred Qualifications -> Qualifications (or Skills). We also have mention of benefits, pay, schedule later. Pay: salary ranges for SF and Sunnyvale. Also mention bonus program, equity award, other comp, 401(k). So we have pay info. Benefits: mention "various benefits", "Explore our benefits", "All full-time employees are eligible to participate in a 401(k) plan." Also "you will be eligible for various benefits." So we can include Benefits 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: hybrid expectation. We should not include sections with placeholder like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; not invent or summarize away detail. So we need to keep details like "nearly one billion customer interactions annually", etc. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should list each duty as
• . For requirements/qualifications we list each bullet. We must not repeat job title. Not include headings like "About The Team". We could maybe include a short paragraph about team? But instruction says only use those headings; we could embed team info under About the role? Might be okay to include a

  about team under About the role? But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only output those headings if we have content. We could also include a

  for any prose not in list. Thus structure:

  About the role

  ... (combining About The Team and About The Role? Actually About The Team is separate but we could incorporate as context. Might be okay to include under About the role.) Then

  Responsibilities

  • ... each duty from "What You'll Do"
  Then

  Requirements

  • ... from Basic Qualifications
  Then

  Qualifications

  • ... from Preferred Qualifications
  Then

  Benefits

  • ... benefits info
  Then

  Pay

  ... salary ranges and bonus, equity, 401k

  Then

  Schedule

  ... in-office expectation

  We must not include any empty sections. Now extract content precisely. About The Team paragraph: "Uber's Customer Obsession AI team is building one of the largest GenAI products at Uber, serving nearly one billion customer interactions annually across all of Uber's products globally - Rideshare, Delivery, Merchants, Autonomous Vehicles, Third-party offerings, and more. Customer experience is at the heart of cutting-edge applied AI today. The opportunity is expanding from handling individual customer queries into an end-to-end proactive AI assistant across the full user journey. We are rebuilding the product from the ground up to be AI-native, with a world-class team across Product, Engineering, Data Science, and Design. The team is also AI-pilled - every day, we find and deploy new ways to use AI internally to accelerate development, improve quality, and increase innovation." About The Role paragraph: "We are looking for a Product Manager to help build the next generation of Agentic AI for Customer Experience at Uber. You will work on products and platform capabilities that enable AI agents to understand customers and their context, reason through complex situations, make decisions, and take actions on their behalf. Depending on the product area, you may work on the customer-facing agent experience, agent reasoning and orchestration, multimodal capabilities, context and memory, quality and evaluation systems, developer tooling, or other foundational capabilities required to operate AI agents at Uber's scale. This is an opportunity to work on AI with real-world consequences and learn how to build and operate agentic systems at massive scale. Our AI serves nearly one billion customer interactions annually across a wide range of products, markets, and customer scenarios. Building these experiences requires us to move quickly at the frontier of AI while maintaining a high bar for customer experience, quality, accuracy, and safety. You will partner closely with Engineering, Data Science, Design, User Research, and Operations to turn advances in AI into products that meaningfully improve the customer experience." We can combine these two paragraphs under About the role. Now Responsibilities: "What You'll Do" bullet points (each sentence starts with a verb). Let's list them: - Build agentic AI products: Own and ship product capabilities that help Uber's AI understand customer needs, reason through complex situations, make decisions, and take actions. - Turn AI advances into customer experiences: Stay close to rapidly evolving AI capabilities and identify opportunities to translate them into intuitive, differentiated experiences for Uber customers. - Own a product area end-to-end: Contribute to product strategy and roadmap, define requirements and success metrics, make tradeoffs, and work closely with cross-functional partners from discovery through launch and iteration. - Drive AI quality: Partner with Engineering and Data Science to understand agent behavior and improve it through capabilities such as evals, experimentation, simulations, observability, debugging, and human feedback. - Champion the customer: Use customer insights, research, data, and product intuition to deeply understand customer problems and ensure technology translates into a high-quality user experience. - Work across the stack: Develop enough technical depth to engage with how agentic systems work - from models and reasoning to tools, context, orchestration, platform infrastructure, and the experiences customers ultimately see. - Use data to learn and iterate: Define success metrics, analyze product and model performance, identify opportunities, and use experimentation and customer feedback to continuously improve the product. - Drive cross-functional execution: Work closely with Engineering, Data Science, Design, User Research, Operations, and other Uber product teams to move quickly from ideas to products in customers' hands. - Operate with speed and curiosity: Experiment with new AI tools and ways of working, including using AI to accelerate product discovery, prototyping, analysis, testing, and iteration. We'll put each as
  • . Now Requirements (Basic Qualifications): List: - Product experience: Bachelor's degree and 3+ years of Product Management experience, including high-impact internships. You have contributed to shipping and improving technology products used by real customers. - Strong product thinking: You can take an ambiguous customer or business problem, break it down, identify the highest-leverage opportunities, and translate them into a clear product plan. - AI curiosity and technical depth: You are excited about AI and have a strong desire to understand how modern AI and agentic systems work. You can engage deeply with Engineering and Data Science on technical tradeoffs without needing to be an engineer yourself. - Customer obsession: You care deeply about the quality of the end-user experience and can combine product intuition, customer research, and quantitative data to make good decisions. - Strong execution: You are comfortable operating in ambiguity, getting into the details, making tradeoffs, and driving cross-functional teams toward outcomes in a fast-moving environment. - Analytical mindset: You use data to understand problems, evaluate product performance, test hypotheses, and make decisions. - Communication and storytelling: You can clearly articulate the customer problem, product rationale, and tradeoffs to both technical and non-technical audiences. - High ownership and learning velocity: You are curious, hands-on, and eager to learn. You move with urgency, seek out feedback, and are excited to build in a space where the technology and product possibilities are evolving rapidly. We'll put each as
  • . Now Qualifications (Preferred Qualifications): List: - Experience working on mobile experiences and consumer products. - Phenomenal track record of working with engineering, analytics and design teams, with proven examples to prioritize work across the team. - Grittiness: you never hesitate to roll up your sleeves and tackle something hands-on. - Proven track record of growing and scaling a product. - For San Francisco, CA-based roles: The base salary range for this role is USD $161,000 per year - USD $179,000 per year. - For Sunnyvale, CA-based roles: The base salary range for this role is USD $161,000 per year - USD $179,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. But note that salary and benefits info maybe better placed under Pay and Benefits sections. The instruction says we should have separate Pay and Benefits sections. So we should move salary details to Pay, benefits to Benefits. The preferred qualifications list includes some of those; we should not duplicate. So for Qualifications we keep only the non-pay/benefit items: mobile experience, track record with engineering/analytics/design, gritti ness, proven track record of growing and scaling a product. Thus Qualifications section will have those four bullet points. Now Benefits section: we have "You will also be eligible for various benefits." Also "All full-time employees are eligible to participate in a 401(k) plan." Also maybe "Explore our benefits." Also maybe mention bonus program etc but that's pay. So Benefits: various benefits, 401(k) plan. We could also mention "you may be offered an equity award & other types of comp." That's compensation, maybe pay. We'll keep under Pay. Thus Benefits
    • Various benefits (details available via Uber's benefits page).
    • Eligibility to participate in Uber's 401(k) plan for full-time employees.
    Now Pay section: include salary ranges for SF and Sunnyvale, bonus program, equity award, other comp. We'll write:

    For San Francisco, CA-based roles: base salary range USD $161,000 – USD $179,000 per year. For Sunnyvale, CA-based roles: same range. For all US locations, eligible to participate in Uber's bonus program, and may be offered an equity award and other types of compensation. All full-time employees eligible for a 401(k) plan.

    But note 401(k) we already put in Benefits; maybe we should not duplicate. The instruction says preserve ALL substantive information; we can include in both sections if relevant, but better to avoid duplication. However 401(k) is a benefit, not pay. So we should keep it under Benefits only.