Technical Program Manager II, Capacity Planning, Cloud
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have content: Minimum qualifications, Preferred qualifications, About The Job (description), Responsibilities, Pay (Individual pay... US: $138000 - $197000 + 15% bonus target + equity + benefits). Also location note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; New York, NY, USA." That's location info; maybe we can include under a short paragraph (not a heading). Also we have benefits mention: "Learn more about benefits at Google." but not specifics. The instruction: never create Benefits section unless posting actually states them. It says "Learn more about benefits at Google." That's not specific benefits; we should not create Benefits section. Pay section: we have specific pay range and bonus target etc. So include Pay section.
Schedule: not mentioned, so omit.
Skills: not explicit separate list; we could include under Qualifications? Probably not needed.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, accommodation, legal, etc. Also remove "Learn more about benefits at Google."? That's a link but it's boilerplate? It's a generic line; maybe we can keep as prose? It's not substantive benefit detail; but it's not boilerplate like EEO. It's a sentence referencing benefits. Might be okay to keep as part of description? But we could drop as it's not specific. Safer to drop? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about benefits at Google." is not exactly those but could be considered generic. I'd keep it maybe as part of a paragraph about benefits? But we aren't making a Benefits section. Could include in About the role paragraph.
We need to include location note as a short
.
We need to include Minimum qualifications and Preferred qualifications as lists under Requirements? Could combine into Requirements section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the role (description), Responsibilities, Requirements (maybe combine min and pref), Pay.
We need to decide: Should we have Requirements and Qualifications separate? The list includes both as possible headings. We have both minimum and preferred qualifications. Could make a Requirements section for minimum qualifications, and a Qualifications section for preferred qualifications. Or combine into one Requirements section with sublists? Better to follow possible headings: Requirements (minimum) and Qualifications (preferred). Use for each.
Thus:
About the role
... description from About The Job paragraph(s).
Responsibilities
- ... each responsibility line.
Requirements
- Bachelor's degree in a technical field, or equivalent practical experience.
- 2 years of experience in program management.
- Experience in capacity planning.
- Experience in data center networking.
Qualifications
- 2 years of experience managing cross-functional or cross-team projects.
- Experience in data center operations.
Pay
US: $138000 - $197000 (USD) + 15% bonus target + equity + benefits
Also location note: maybe a before sections: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; New York, NY, USA."
We must not repeat job title as heading. Not include Job ID.
We must not include boilerplate EEO etc.
Check for duplicated lines: The posting includes "Learn more about benefits at Google ." We'll drop that.
Check for any other substantive content: The paragraph about Google Cloud etc. Might be part of About the role? The About The Job section includes multiple paragraphs: first about problem solved, then description of TPM role, then description of Fleet Infrastructure Planning team, then Google Cloud paragraph. All that is substantive about the role. We'll include all in About the role paragraph(s). Could be multiple
tags.
We need to preserve all substantive information; we can split into multiple
for readability.
Let's extract the About The Job text:
"About The Job A problem isn’t truly solved until it’s solved for all. That’s why Googlers build products that help create opportunities for everyone, whether down the street or across the globe. As a Technical Program Manager at Google, you’ll use your technical expertise to lead complex, multi-disciplinary projects from start to finish. You’ll work with stakeholders to plan requirements, identify risks, manage project schedules, and communicate clearly with cross-functional partners across the company. You're equally comfortable explaining your team's analyses and recommendations to executives as you are discussing the technical tradeoffs in product development with engineers. The cross-product area Fleet Infrastructure Planning team is the strategic designer and horizontal connective tissue driving Google's end-to-end physical infrastructure plan. In an era of unprecedented AI expansion and record capital expenditure, we orchestrate the entire physical resource spectrum, unifying compute (accelerators and classic), storage, network (WAN), and power, from a visionary outlook down to actual deployed-in-fleet reality. We are intellectual incubators: when we spot systemic gaps in physical capacity readiness or supportability frameworks, we design the processes, establish the policies, and build the tools to solve them. We build the critical capacity planning and decision-making systems that steer and land fleet resources at the right place, at the right time, and at the right cost. As an Infrastructure Technical Program Manager (TPM), you will be a horizontal leader who translates complex physical requirements into executable global plans. You will own high-visibility programs that define how Google forecasts, allocates, and validates resource supportability (such as establishing workload bundles and automating network fit-checks). 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."
We'll put that in one or multiple
. Could split after first two sentences, but it's okay as one big
. We'll keep as
.
Now Responsibilities: list:
- Lead end-to-end planning and delivery of physical infrastructure resources, including compute, networking, power, and data center space, to ensure capacity lands on time and within budget.
- Manage operational workflows for resource reallocation, capacity recovery, and service transitions across global data center regions to maximize infrastructure efficiency.
- Partner with software and systems engineering teams to define tool requirements, automate planning workflows, and establish clear policies for resource utilization.
- Coordinate across engineering, operations, and business stakeholders to resolve schedule dependencies, evaluate operational trade-offs, and maintain integrated multi-quarter roadmaps.
We'll make
- each.
Now Requirements list as above.
Qualifications list as above.
Pay: as
.
Location note: as
maybe before sections.
Check for any other specifics: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's generic; we already have pay range. Could include that sentence in Pay section? It's substantive but generic. Might include as part of Pay
. But we should not invent. It's in the posting. So we can add that sentence before the range. Eg:
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $197000 (USD) + 15% bonus target + equity + benefits
Now ensure we didn't include any boilerplate: EEO, accommodation, legal, etc. Removed.
Now output only HTML fragment.
Let's craft:
Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; New York, NY, USA.
About the role
A problem isn’t truly solved until it’s solved for all. That’s why Googlers build products that help create opportunities for everyone, whether down the street or across the globe. As a Technical Program Manager at Google, you’ll use your technical expertise to lead complex, multi-disciplinary projects from start to finish. You’ll work with stakeholders to plan requirements, identify risks, manage project schedules, and communicate clearly with cross-functional partners across the company. You're equally comfortable explaining your team's analyses and recommendations to executives as you are discussing the technical tradeoffs in product development with engineers. The cross-product area Fleet Infrastructure Planning team is the strategic designer and horizontal connective tissue driving Google's end-to-end physical infrastructure plan. In an era of unprecedented AI expansion and record capital expenditure, we orchestrate the entire physical resource spectrum, unifying compute (accelerators and classic), storage, network (WAN), and power, from a visionary outlook down to actual deployed-in-fleet reality. We are intellectual incubators: when we spot systemic gaps in physical capacity readiness or supportability frameworks, we design the processes, establish the policies, and build the tools to solve them. We build the critical capacity planning and decision-making systems that steer and land fleet resources at the right place, at the right time, and at the right cost. As an Infrastructure Technical Program Manager (TPM), you will be a horizontal leader who translates complex physical requirements into executable global plans. You will own high-visibility programs that define how Google forecasts, allocates, and validates resource supportability (such as establishing workload bundles and automating network fit-checks). 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.
Responsibilities
- Lead end-to-end planning and delivery of physical infrastructure resources, including compute, networking, power, and data center space, to ensure capacity lands on time and within budget.
- Manage operational workflows for resource reallocation, capacity recovery, and service transitions across global data center regions to maximize infrastructure efficiency.
- Partner with software and systems engineering teams to define tool requirements, automate planning workflows, and establish clear policies for resource utilization.
- Coordinate across engineering, operations, and business stakeholders to resolve schedule dependencies, evaluate operational trade-offs, and maintain integrated multi-quarter roadmaps.
Requirements
- Bachelor's degree in a technical field, or equivalent practical experience.
- 2 years of experience in program management.
- Experience in capacity planning.
- Experience in data center networking.
Qualifications
- 2 years of experience managing cross-functional or cross-team projects.
- Experience in data center operations.
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $197000 (USD) +
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, accommodation, legal, etc. Also remove "Learn more about benefits at Google."? That's a link but it's boilerplate? It's a generic line; maybe we can keep as prose? It's not substantive benefit detail; but it's not boilerplate like EEO. It's a sentence referencing benefits. Might be okay to keep as part of description? But we could drop as it's not specific. Safer to drop? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about benefits at Google." is not exactly those but could be considered generic. I'd keep it maybe as part of a paragraph about benefits? But we aren't making a Benefits section. Could include in About the role paragraph. We need to include location note as a short
. We need to include Minimum qualifications and Preferred qualifications as lists under Requirements? Could combine into Requirements section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the role (description), Responsibilities, Requirements (maybe combine min and pref), Pay. We need to decide: Should we have Requirements and Qualifications separate? The list includes both as possible headings. We have both minimum and preferred qualifications. Could make a Requirements section for minimum qualifications, and a Qualifications section for preferred qualifications. Or combine into one Requirements section with sublists? Better to follow possible headings: Requirements (minimum) and Qualifications (preferred). Use
for each. Thus:
About the role
... description from About The Job paragraph(s).
Responsibilities
- ... each responsibility line.
Requirements
- Bachelor's degree in a technical field, or equivalent practical experience.
- 2 years of experience in program management.
- Experience in capacity planning.
- Experience in data center networking.
Qualifications
- 2 years of experience managing cross-functional or cross-team projects.
- Experience in data center operations.
Pay
US: $138000 - $197000 (USD) + 15% bonus target + equity + benefits
Also location note: maybe abefore sections: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; New York, NY, USA." We must not repeat job title as heading. Not include Job ID. We must not include boilerplate EEO etc. Check for duplicated lines: The posting includes "Learn more about benefits at Google ." We'll drop that. Check for any other substantive content: The paragraph about Google Cloud etc. Might be part of About the role? The About The Job section includes multiple paragraphs: first about problem solved, then description of TPM role, then description of Fleet Infrastructure Planning team, then Google Cloud paragraph. All that is substantive about the role. We'll include all in About the role paragraph(s). Could be multiple
tags. We need to preserve all substantive information; we can split into multiple
for readability. Let's extract the About The Job text: "About The Job A problem isn’t truly solved until it’s solved for all. That’s why Googlers build products that help create opportunities for everyone, whether down the street or across the globe. As a Technical Program Manager at Google, you’ll use your technical expertise to lead complex, multi-disciplinary projects from start to finish. You’ll work with stakeholders to plan requirements, identify risks, manage project schedules, and communicate clearly with cross-functional partners across the company. You're equally comfortable explaining your team's analyses and recommendations to executives as you are discussing the technical tradeoffs in product development with engineers. The cross-product area Fleet Infrastructure Planning team is the strategic designer and horizontal connective tissue driving Google's end-to-end physical infrastructure plan. In an era of unprecedented AI expansion and record capital expenditure, we orchestrate the entire physical resource spectrum, unifying compute (accelerators and classic), storage, network (WAN), and power, from a visionary outlook down to actual deployed-in-fleet reality. We are intellectual incubators: when we spot systemic gaps in physical capacity readiness or supportability frameworks, we design the processes, establish the policies, and build the tools to solve them. We build the critical capacity planning and decision-making systems that steer and land fleet resources at the right place, at the right time, and at the right cost. As an Infrastructure Technical Program Manager (TPM), you will be a horizontal leader who translates complex physical requirements into executable global plans. You will own high-visibility programs that define how Google forecasts, allocates, and validates resource supportability (such as establishing workload bundles and automating network fit-checks). 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." We'll put that in one or multiple
. Could split after first two sentences, but it's okay as one big
. We'll keep as
. Now Responsibilities: list: - Lead end-to-end planning and delivery of physical infrastructure resources, including compute, networking, power, and data center space, to ensure capacity lands on time and within budget. - Manage operational workflows for resource reallocation, capacity recovery, and service transitions across global data center regions to maximize infrastructure efficiency. - Partner with software and systems engineering teams to define tool requirements, automate planning workflows, and establish clear policies for resource utilization. - Coordinate across engineering, operations, and business stakeholders to resolve schedule dependencies, evaluate operational trade-offs, and maintain integrated multi-quarter roadmaps. We'll make
- each.
Now Requirements list as above.
Qualifications list as above.
Pay: as
. Location note: as
maybe before sections. Check for any other specifics: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's generic; we already have pay range. Could include that sentence in Pay section? It's substantive but generic. Might include as part of Pay
. But we should not invent. It's in the posting. So we can add that sentence before the range. Eg:
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $197000 (USD) + 15% bonus target + equity + benefits
Now ensure we didn't include any boilerplate: EEO, accommodation, legal, etc. Removed. Now output only HTML fragment. Let's craft:Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; New York, NY, USA.
About the role
A problem isn’t truly solved until it’s solved for all. That’s why Googlers build products that help create opportunities for everyone, whether down the street or across the globe. As a Technical Program Manager at Google, you’ll use your technical expertise to lead complex, multi-disciplinary projects from start to finish. You’ll work with stakeholders to plan requirements, identify risks, manage project schedules, and communicate clearly with cross-functional partners across the company. You're equally comfortable explaining your team's analyses and recommendations to executives as you are discussing the technical tradeoffs in product development with engineers. The cross-product area Fleet Infrastructure Planning team is the strategic designer and horizontal connective tissue driving Google's end-to-end physical infrastructure plan. In an era of unprecedented AI expansion and record capital expenditure, we orchestrate the entire physical resource spectrum, unifying compute (accelerators and classic), storage, network (WAN), and power, from a visionary outlook down to actual deployed-in-fleet reality. We are intellectual incubators: when we spot systemic gaps in physical capacity readiness or supportability frameworks, we design the processes, establish the policies, and build the tools to solve them. We build the critical capacity planning and decision-making systems that steer and land fleet resources at the right place, at the right time, and at the right cost. As an Infrastructure Technical Program Manager (TPM), you will be a horizontal leader who translates complex physical requirements into executable global plans. You will own high-visibility programs that define how Google forecasts, allocates, and validates resource supportability (such as establishing workload bundles and automating network fit-checks). 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.
Responsibilities
- Lead end-to-end planning and delivery of physical infrastructure resources, including compute, networking, power, and data center space, to ensure capacity lands on time and within budget.
- Manage operational workflows for resource reallocation, capacity recovery, and service transitions across global data center regions to maximize infrastructure efficiency.
- Partner with software and systems engineering teams to define tool requirements, automate planning workflows, and establish clear policies for resource utilization.
- Coordinate across engineering, operations, and business stakeholders to resolve schedule dependencies, evaluate operational trade-offs, and maintain integrated multi-quarter roadmaps.
Requirements
- Bachelor's degree in a technical field, or equivalent practical experience.
- 2 years of experience in program management.
- Experience in capacity planning.
- Experience in data center networking.
Qualifications
- 2 years of experience managing cross-functional or cross-team projects.
- Experience in data center operations.
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $197000 (USD) +