Program Manager, Regulatory Reporting

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 that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate (cookie/navigation/legal/EEO etc). Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: description of Waymo, mission, SWQOps team, why essential, etc. This is prose. - Responsibilities: bullet list of "You Will Drive outcomes..." etc. That's a list. - Requirements: bullet list of "You Have ..." (Bachelor's degree..., 10+ years..., etc). Also maybe "We Prefer ..." could be separate "Preferred Qualifications" but we only have sections: Requirements, Qualifications, Skills. Could treat "You Have" as Requirements, "We Prefer" as Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Requirements and Qualifications separate. - Benefits: mention "Waymo employees are also eligible to participate in Waymo’s discretionary annual bonus program, equity incentive plan, and generous Company benefits program". Also maybe remote note? But remote note is about remote jobs only - we might drop as boilerplate? It's a note about remote work eligibility; could be considered part of Benefits? It's not a benefit per se. Might be considered part of "Schedule"? Not sure. Probably we can include a brief note under Benefits? But we should not invent. The posting says: "(Remote jobs only - Please note that Waymo may not be able to employ remotely in all locations. Please speak with your recruiter about your preferred location for remote work when you begin the interview process.)" That's a note about remote work; could be considered part of "Schedule" or "Benefits"? It's more about work arrangement. Since we have Schedule section only if posting actually states schedule. It doesn't state schedule (like full-time, hours). It mentions full-time position. Could include Schedule: "Full-time". But we need actual content: The posting says "The expected base salary range for this full-time position is listed below." So we know it's full-time. That's schedule info. So we can include Schedule section with "Full-time". However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time, so we can include Schedule with "Full-time". But is that too thin? It's okay. - Pay: Salary Range $190,000—$234,000 USD. Also mention discretionary annual bonus program, equity incentive plan. That's compensation/benefits. So Pay section should include salary range and maybe bonus/equity? But Benefits section could include bonus, equity, generous Company benefits program. We'll separate: Pay: salary range. Benefits: bonus program, equity incentive plan, generous Company benefits program. - Skills: maybe not explicitly listed; we have "Experience with Lean / Six Sigma process improvement methodologies". That could be a skill. Also "Experience working with offshore teams / multiple local operations hubs", "Experience within A/V space", "Increased competency in supporting all phases of the machine learning development lifecycle". Those could be skills or qualifications. We could put them under Skills. But we already have Qualifications for "We Prefer". Might be better to treat "You Have" as Requirements, "We Prefer" as Qualifications, and the specific skill items as Skills. However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one? But we have headings list; we can choose to include only those with substantive content. Let's see: - Requirements: Bachelor's degree..., 10+ years..., 5+ years people management, Experience in Regulatory Compliance..., Proven ability..., Ability to thrive... - Qualifications (Preferred): Experience working with offshore teams..., Experience within A/V space, Increased competency..., Experience with Lean/Six Sigma... - Skills: maybe not needed separately if we treat those as Qualifications. Could combine Qualifications and Skills into one section called "Qualifications & Skills". But we have to use headings from list; we could use "Qualifications" for preferred and also include skills there. That's acceptable. Thus sections: About the role (prose), Responsibilities (ul), Requirements (ul), Qualifications (ul), Pay (p with salary range), Benefits (p with bonus/equity/benefits), Schedule (p with Full-time). Ensure we don't repeat filler. Now we need to strip boilerplate: The initial paragraph about Waymo mission etc is substantive. The "Why This Team Is Essential To Waymo's Success" is also substantive. The "We are on the front lines of:" bullet-like paragraphs (but not actual list). We need to preserve all substantive info; we can turn those into prose or maybe a list? The instruction: Use

• for any list of duties/requirements/benefits. The "We are on the front lines of:" includes items separated by line breaks but not explicitly list. Could treat as prose. Safer to keep as prose. Now we need to remove duplicated lines, cookie/navigation/legal/EEO etc. There's none visible besides the remote note parentheses. We'll keep remote note maybe as part of Schedule? Actually remote note is about remote work eligibility; could be considered part of Schedule? Not exactly. Might be considered part of "Benefits"? It's about work arrangement. Since we already have Schedule as Full-time, we could add a note about remote eligibility within Schedule? But that might be too specific. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. The remote note is minor metadata; we could fold into a short

  under Schedule or Benefits. But we already have Schedule as Full-time; we could add a sentence: "Remote work eligibility subject to location; discuss with recruiter." That preserves info. However we must not invent; we can include that note as is. Thus Schedule section could be:

  Full-time position. Remote work eligibility subject to location; please discuss with recruiter.

  But the remote note originally: "(Remote jobs only - Please note that Waymo may not be able to employ remotely in all locations. Please speak with your recruiter about your preferred location for remote work when you begin the interview process.)" We'll rephrase slightly but must preserve meaning; we can't invent but we can rephrase? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Rephrasing might be okay as long as we keep the meaning. Safer to keep the exact sentence within quotes? Could include as is inside

  . Let's include the exact note: "(Remote jobs only - Please note that Waymo may not be able to employ remotely in all locations. Please speak with your recruiter about your preferred location for remote work when you begin the interview process.)" That's substantive. Thus Schedule:

  Full-time position. (Remote jobs only - Please note that Waymo may not be able to employ remotely in all locations. Please speak with your recruiter about your preferred location for remote work when you begin the interview process.)

  Now Benefits: "Waymo employees are also eligible to participate in Waymo’s discretionary annual bonus program, equity incentive plan, and generous Company benefits program, subject to eligibility requirements." We'll put that. Pay: "

  The expected base salary range for this full-time position is $190,000—$234,000 USD.

  " Also note actual starting pay based on factors; but that's generic; we could include that sentence as well? It's substantive: "Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level." We'll include that. Thus Pay section could have two sentences. Now Responsibilities: list items from "You Will Drive outcomes..." each sentence starts with a verb. We'll make
  • each. Let's extract: - Drive outcomes for large and complex technical operations programs that span multiple organizations. - Develop and drive execution on strategic roadmaps, own forecasting and resource planning. - Partner with the Regulatory Compliance team to operationalize reporting requirements and be responsible for standing up new workflows and scaling existing workflows to support US and International expansions. - Define program / workflow KPIs and SLAs. - Drive high-quality outcomes through deployments with a global vendor workforce. - Drive workflow transformation efforts to meet evolving business needs. - Partner with Engineering to design, test, and deploy cutting-edge Machine Learning (ML) and Generative AI (Gen-AI) models and tools to drive step-change improvements in issue discovery & detection, triage efficiency, and quality assurance. - Communicate overall program status, risks and current priorities to executive stakeholders. - Drive strategic decisions making across functions. - Mentor a high-performing team of Technical Specialists, fostering a culture of "quality-first" in a high-velocity environment. That's 10 items. Now Requirements: list from "You Have": - Bachelor's degree in technical, legal or business discipline - 10+ years of experience managing complex, tech-enabled operations and experience working across cross-functional partners (Legal, Product, Engineering, Data Science, Systems Engineering) to drive outcomes - 5+ years of people management experience - Experience in Regulatory Compliance, Vehicle Qualification, or similar domains, and ability to assess and operationalize legal reporting requirements - Proven ability to manage complex technical operations programs, including structuring project plans, identifying dependencies, and driving execution - Ability to thrive in a high ambiguity, dynamic environment Now Qualifications (Preferred): from "We Prefer": - Experience working with offshore teams / multiple local operations hubs - Experience within A / V space - Increased competency in supporting all phases of the machine learning development lifecycle, from data preparation and training to validation, deployment, and continuous monitoring - Experience with Lean / Six Sigma process improvement methodologies Now About the role: combine the initial paragraphs up to "Why This Team Is Essential To Waymo's Success" and the subsequent paragraphs describing the team's role. We'll need to preserve all substantive info. Let's craft a prose paragraph(s) that includes all details. We have: "Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo has focused on building the Waymo Driver—The World's Most Experienced Driver™—to improve access to mobility while saving thousands of lives now lost to traffic crashes. The Waymo Driver powers Waymo’s fully autonomous ride-hail service and can also be applied to a range of vehicle platforms and product use cases. The Waymo Driver has provided over ten million rider-only trips, enabled by its experience autonomously driving over 100 million miles on public roads and tens of billions in simulation across 15+ U.S. states. The Software Quality Operations (SWQOps) team is at the heart of ensuring the safety, reliability, and quality of the Waymo Driver. Our mission is to build an adaptable and scalable operation, increasingly powered by AI, to deliver the crucial insights necessary to confidently deploy and grow Waymo's autonomous vehicle service. Why This Team Is Essential To Waymo's Success Waymo is undergoing unprecedented growth, rapidly expanding into new cities (targeting ~20 new cities by EOY 2026) and launching new vehicle platforms. SWQ Ops plays a critical role in this expansion, making it possible to scale safely and efficiently. The Regulatory Reporting Operations team within SWQ Ops owns the scaled delivery of datasets and methodologies used to evaluate events of regulatory interest and ensure reporting accuracy as Waymo continues to scale. We are on the front lines of: De-risking New Deployments: Through meticulous triage of driving and simulated events, issue discovery, and continuous