Senior Leadership Technical Program Manager, AI/ML

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 like EEO, accommodation, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Application window open until at least Oct 1, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA; New York, NY, USA. - Minimum qualifications: Bachelor's degree in a technical field, or equivalent practical experience. 10 years of experience in program management. 7 years of experience in leadership roles with/without direct reports. Experience designing organizational processes, business planning cycles, or governance frameworks for engineering organizations. Experience in building AI features or AI platforms. - Preferred qualifications: 10 years of experience managing cross-functional/team projects. 10 years of experience in product, engineering, operations, or technical consulting roles. Experience rolling out new processes or tools to resistant stakeholders and driving adoption through clear value proposition and empathy. - About The Job: description about Google Drive, GenAI, etc. - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $240000 - $333000 (USD) + 25% bonus target + equity + benefits - Responsibilities: list bullet points: Build, manage, and mentor a high-performing team of Technical Program Managers. Drive the successful delivery of Drive's critical Generative AI roadmap, including our agentic initiatives. Act as a strategic thought partner to Engineering and Product leadership to translate highly ambiguous AI goals into concrete, accelerated delivery plans. Orchestrate complex, interdependent programs across highly federated and matrixed teams. Lead focused initiatives to swarm dependencies, resolve cross-Workspace architectural tensions, and eliminate execution bottlenecks early. Design and implement robust product and platform engineering operating processes. Streamline business planning cycles (OKRs), drive the adoption of developer enablement tools (DevAI), and establish scalable governance frameworks that increase iteration velocity across hundreds of engineers. - Benefits: Not explicitly listed besides "equity + benefits". No specific benefits listed. So we should not create a Benefits section unless posting actually states them. It only mentions "equity + benefits" generically, not specific benefits. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay and mentions benefits generically but not specifics. Should we include a Benefits section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "equity + benefits". That is a statement that benefits exist, but not specific. Might be considered stating benefits exist, but we need specific content. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist (equity + benefits). However they also say "Prefer a few substantive sections over many thin ones." And "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')". Since benefits are not detailed, it's filler. So we should not create a Benefits section. - Pay: we have specific pay range: US: $240000 - $333000 (USD) + 25% bonus target + equity + benefits. That's specific enough. So include Pay section. - Schedule: not mentioned. So no Schedule section. - Skills: not explicitly listed as a separate section; but we could incorporate skills within Requirements/Qualifications. The rule: use headings for sections like Skills if there is content. There's no explicit Skills list separate. So we may not create Skills. - About the role: we have About The Job description. That's suitable for About the role heading. - Responsibilities: we have list. - Requirements: we have Minimum qualifications. - Qualifications: we have Preferred qualifications. Could combine Requirements and Qualifications? The rule says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications sections. We need to preserve all substantive information. So we need to include the location note and application window info somewhere. Where to put? Could be a short paragraph under About the role or maybe a separate section like "Details". But we only have prescribed headings; we could put that info in a

under About the role or maybe under Responsibilities? Better to include under About the role as it's about the job location and timing. Or we could create a separate section like "Details" but not in allowed headings; better to incorporate into About the role. We must not include boilerplate like EEO, accommodation, etc. Remove those lines. We must not repeat job title. We must not include markdown fences. We need to output only HTML fragment. Let's craft:

About the role

The application window will be open until at least October 01, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA; New York, NY, USA.

[Then the About The Job paragraph...] We need to include the description about Google Drive, GenAI, etc. Ensure we keep all substantive info.

Then

Responsibilities

with

• items. Then

  Requirements

  with
  • for Minimum qualifications. Then

    Qualifications

    with
    • for Preferred qualifications. Then

      Pay

      with

      containing the pay details. We must not include Benefits section. Check for any other substantive info: maybe mention "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's part of Pay. Now ensure we don't include any boilerplate like "Google is proud to be an equal opportunity workplace..." etc. Remove. Also remove lines like "Learn more about benefits at Google ." That's part of responsibilities? Actually appears before responsibilities: "Learn more about benefits at Google ." That's a line; we should remove as it's boilerplate/link. Also remove "See also Google's EEO Policy and EEO is the Law." etc. Now craft HTML. Let's write the About the role paragraph: combine the application window and location note, then the About The Job description. We need to preserve all substantive info from About The Job: It's a long paragraph. Let's copy it exactly but ensure we don't include any boilerplate. About The Job text: "Google's projects, like our users, span the globe and require managers to keep the big picture in focus while being able to dive into the unique engineering challenges we face daily. As a Technical Program Manager at Google, you lead complex, multi-disciplinary engineering projects using your engineering expertise. You plan requirements with internal customers and usher projects through the entire project lifecycle. This includes managing project schedules, identifying risks and clearly communicating them to project stakeholders. You're equally at home explaining your team's analyses and recommendations to executives as you are discussing the technical trade-offs in product development with engineers. Using your extensive technical and leadership expertise, you manage various Engineering-specific programs and teams. Google Drive is committed to creating a secure, intelligent, beautiful, and universally accessible means of storing, sharing, organizing, and finding information. With billions of users, deep integration across Google’s first-party products (including Workspace, Search, Chrome, and Gemini), and a thriving ecosystem of thousands of third-party integrations, Drive is the market leader in content management. Our immediate top focus is leveraging Generative AI (GenAI) to fundamentally revolutionize how users interact with their content, unlocking unprecedented value from their personal and enterprise knowledge. The Drive Technical Program Management (TPgM) team plays a critical role in bringing this GenAI-driven vision to life. We stand at the nexus of strategic planning, engineering leadership, and cross-functional orchestration. We help define the technical roadmap, proactively mitigating risks across highly distributed teams, and ensuring seamless execution from ideation to launch. AI will change the future of work in profound ways, and our products— Gmail, Docs, Drive, Calendar, Sheets, Vids and Meet are at the forefront. From pre-computed summaries for email threads, summaries for meetings, and videos created from a document using lifelike AI avatars, our AI opportunity is huge. Our mission is to meaningfully connect people so they can create, build, and grow together and as part of the team you can build how productivity tools should work 5-10 years into the future. You will work with model builders (Google DeepMind), work with exceptional leaders, and have the ability to impact billions of users across the world." We need to keep that. Now Responsibilities list: - Build, manage, and mentor a high-performing team of Technical Program Managers. - Drive the successful delivery of Drive's critical Generative AI roadmap, including our agentic initiatives. - Act as a strategic thought partner to Engineering and Product leadership to translate highly ambiguous AI goals into concrete, accelerated delivery plans. - Orchestrate complex, interdependent programs across highly federated and matrixed teams. - Lead focused initiatives to swarm dependencies, resolve cross-Workspace architectural tensions, and eliminate execution bottlenecks early. - Design and implement robust product and platform engineering operating processes. - Streamline business planning cycles (OKRs), drive the adoption of developer enablement tools (DevAI), and establish scalable governance frameworks that increase iteration velocity across hundreds of engineers. Now Requirements (Minimum qualifications): - Bachelor's degree in a technical field, or equivalent practical experience. - 10 years of experience in program management. - 7 years of experience in leadership roles with/without direct reports. - Experience designing organizational processes, business planning cycles, or governance frameworks for engineering organizations. - Experience in building AI features or AI platforms. Now Qualifications (Preferred qualifications): - 10 years of experience managing cross-functional/team projects. - 10 years of experience in product, engineering, operations, or technical consulting roles. - Experience rolling out new processes or tools to resistant stakeholders and driving adoption through clear value proposition and empathy. Now Pay: - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $240000 - $333000 (USD) + 25% bonus target + equity + benefits We could put that in a

      . Now ensure we didn't miss any substantive info: The note about "By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA; New York, NY, USA." included. Also the application window note. Now check for any other substantive info like "Google Drive is committed to creating a secure, intelligent, beautiful, and universally accessible means..." we kept. Now ensure we didn't inadvertently include any boilerplate like "Google is proud to be an equal opportunity workplace..." removed. Now output HTML. We need to wrap sections in appropriate tags. No or . Just fragment. Let's produce:

      About the role

      The application window will be open until at least October 01, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Boulder, CO, USA; New York, NY, USA.