Technical Program Manager III, Infrastructure Capacity Planning, Google Cloud

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Job". We'll use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. We have: - Minimum qualifications: Bachelor's degree in a technical field, or equivalent practical experience. 5 years of experience in program management. Experience with data analysis, business intelligence, or dashboarding tools (e.g., SQL, Plx, or similar metrics platforms). Experience with infrastructure capacity planning. - Preferred qualifications: 5 years of experience managing cross-functional or cross-team projects. Experience in technical infrastructure, capacity planning, supply chain management, cloud computing, or business operations. Ability to synthesize strategic solutions to interdependent and broad problems, and navigate high levels of ambiguity. Excellent analytical approach and ability to organize chaotic information into useful facts and data to drive fleet efficiency. Independent with the ability to conceive, accept responsibility for, and see projects through to completion in a fast-paced environment. - About The Job: description paragraphs. - Responsibilities: list of bullet points. - Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $163000 - $236000 (USD) + 15% bonus target + equity + benefits". So we have Pay section. - Benefits: Not explicitly listed besides "benefits" mentioned in pay line. No specific benefits details. So we should not create Benefits section unless posting actually states them. It only mentions "+ benefits" generically, but not specifics. Probably we should not create Benefits section because no specific benefits listed. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated, so include Pay. Benefits not specific, so omit. - Schedule: not mentioned, omit. - Skills: Could be derived from qualifications? But we have no explicit Skills section. We could combine qualifications into Requirements and Preferred qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include. We have About the role (About The Job). Responsibilities. Requirements (minimum qualifications). Qualifications (preferred qualifications). Possibly Skills could be omitted if no explicit skills list. We'll include Requirements and Qualifications. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, accommodation, etc. Also remove "Learn more about benefits at Google ." (that's part of responsibilities line? Actually appears after responsibilities heading? In text: "Responsibilities Learn more about benefits at Google . Design, build, and maintain reporting systems..." So we need to strip "Learn more about benefits at Google ." as it's boilerplate. Also remove "Google is proud to be an equal opportunity workplace..." etc. We need to preserve all substantive information. Let's extract substantive content: About The Job paragraph(s): "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 projects of various size and scope, identifying future opportunities, improving processes and driving the technical directions of your programs. The Integrated Capacity Group (ICG) is the central nervous system for Alphabet’s infrastructure capacity. We are the single governing organization that plans, fulfills, rightsizes, and protects compute, memory, and storage across Google’s core shared fleets (TI, Core, Search, P&D, Geo). We care deeply about operating capacity management at a massive scale, balancing reliability, and driving the lowest Total Cost of Ownership (TCO). This means automating quota fulfillment, enforcing resource guardrails, and unlocking stranded capacity to drive fleet-wide efficiency. You will collaborate with a highly cross-functional group of capacity planners, TPMs, SREs, and business operations partners. As the team's anchor for business intelligence and metrics, you will advocate for data-driven decision-making, providing unified executive visibility across all fleets to protect Google's critical infrastructure from stockouts. Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems." That's the about section. Responsibilities bullet points (after removing "Learn more about benefits at Google ."): - Design, build, and maintain reporting systems and executive dashboards that provide real-time visibility into global capacity health, resource utilization, and order fulfillment metrics. - Partner with cross-functional engineering, planning, and operations teams to execute recurring capacity planning cycles and ensure infrastructure delivery aligns with long-term business forecasts. - Drive fleet efficiency and governance initiatives by monitoring utilization guardrails, identifying stranded resources, and proposing data-backed optimization strategies to reduce the total cost of ownership. - Analyze complex supply chain data to identify operational bottlenecks, measure on-time delivery Service Level Objectives (SLOs), and establish standardized business operations processes. - Lead the development of business intelligence tools and data structures to automate manual tracking and enable data-driven decision-making across multiple product areas. Minimum qualifications (as list): - Bachelor's degree in a technical field, or equivalent practical experience. - 5 years of experience in program management. - Experience with data analysis, business intelligence, or dashboarding tools (e.g., SQL, Plx, or similar metrics platforms). - Experience with infrastructure capacity planning. Preferred qualifications (list): - 5 years of experience managing cross-functional or cross-team projects. - Experience in technical infrastructure, capacity planning, supply chain management, cloud computing, or business operations. - Ability to synthesize strategic solutions to interdependent and broad problems, and navigate high levels of ambiguity. - Excellent analytical approach and ability to organize chaotic information into useful facts and data to drive fleet efficiency. - Independent with the ability to conceive, accept responsibility for, and see projects through to completion in a fast-paced environment. Pay: - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. - US: $163000 - $236000 (USD) + 15% bonus target + equity + benefits We could combine into a paragraph or list. Use

for prose,

• for list. We need to output only HTML fragment. Structure:

  About the role

  ... (the about text)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $163000 - $236000 (USD) + 15% bonus target + equity + benefits

  We should not include Schedule, Benefits, Skills. Check for any leftover boilerplate: Ensure we removed EEO lines, accommodation, etc. Now output HTML. Make sure to escape any special characters? The text includes ampersand (&) in "TI, Core, Search, P&D, Geo". That's fine as is in HTML? Actually & is special; need to escape as &. The text includes "P&D". That's "P&D". The & should be escaped. Also "TCO" fine. Also "SLOs". Also "15%". Percent sign is okay. Also "USD". Also "TI, Core, Search, P&D, Geo". We'll escape & as &. Also "business intelligence" fine. Also "data-backed". fine. Also "Total Cost of Ownership (TCO)". fine. Also "service level objectives (SLOs)". fine. Also "Google Cloud". fine. Also "Alphabet’s". Contains a curly apostrophe ’ which is okay but better to keep as is? Might be okay but we can keep as is. Usually safe. We'll escape & only. Let's rewrite about text with & escaped. About text: "The Integrated Capacity Group (ICG) is the central nervous system for Alphabet’s infrastructure capacity. We are the single governing organization that plans, fulfills, rightsizes, and protects compute, memory, and storage across Google’s core shared fleets (TI, Core, Search, P&D, Geo)." We need to escape & in "P&D". So "P&D". Also "Google’s" has curly apostrophe, fine. Also "TI, Core, Search, P&D, Geo". Also "Alphabet’s". Also "Google’s". Also "TI, Core, Search, P&D, Geo". Also "Google’s". Also "Alphabet’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "Google’s". Also "