Program Manager III, Network Planning, Cloud Infrastructure
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
Minimum qualifications: Bachelor's degree or equivalent practical experience.5 years of experience in program or project management.Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).Experience working with data analytics tools and reporting platforms.
Preferred qualifications: 5 years of experience managing cross-functional or cross-team projects.Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.Experience in managing technical programs with hardware teams. Ability to take accountability and ownership for end-to-end project lifecycle.
About The Job: paragraph.
Then responsibilities list: bullet points (starting with "Learn more about benefits at Google ." Actually that line is weird: "Learn more about benefits at Google ." It's likely a stray line. Then bullet points: Identify changes introduced by large scale business initiatives, drive business requirements and lead development/implementation with engineering teams to successfully land the programs. Partner with cross functional teams in deployments, supply chain planning, operations and engineering to identify, develop and lead large scale programs that improve our deployment velocity, inventory efficiency and supply resiliency. Develop and lead new forums, reports with key stakeholders and leaders to identify and flag risks, delivery challenges that need escalation, and highlight achievement of key milestones throughout the planning and execution cycles. Define, track and report on key performance metrics and raise issues proactively to ensure on-time follow-through. Define continuous improvement areas based upon metrics and work with engineering/systems team to establish program roadmaps to deliver the improvements.
Then after that: "Google is proud to be an equal opportunity workplace..." That's EEO boilerplate, should be removed.
Also "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". That's pay info. So we need a Pay section.
Also there is mention of benefits: "Learn more benefits at Google ." Actually that line is weird but we can treat as mention of benefits. However we need to include Benefits section only if posting actually states them. There's "Learn more about benefits at Google ." That's a reference but not a description. The posting also says "+ equity + benefits" in pay line. So we have mention of benefits but not details. According to rule: never create Benefits section unless posting actually states them. It does state "benefits" generically but not specifics. Might be considered stating them? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits in the pay line: "+ equity + benefits". So we can include a Benefits section but we need to include substantive content. We have no detail beyond that. Could we include a short
that says "Benefits include equity and other benefits as described by Google." But that might be inventing detail. Better to not create Benefits section if we have no specifics. The rule says "Prefer a few substantive sections over many thin ones." So maybe we omit Benefits section.
Pay: we have specific salary range and bonus target etc. So we should include Pay section with that info.
Schedule: not mentioned, so omit.
Now sections: We could have About the role (the About The Job paragraph). Responsibilities (list). Requirements/Qualifications: we have Minimum qualifications and Preferred qualifications. Could combine into a Qualifications section with two sublists? But we need to use
for section headings only, not subheadings. We could have a Qualifications section with - for each qualification (both minimum and preferred). But we need to differentiate? Not required. Could just list all qualifications.
Alternatively we could have Requirements (minimum) and Preferred qualifications separate sections. But rule: prefer few substantive sections over many thin ones. So maybe combine into one Qualifications section.
Also we might have Skills section? Not explicitly; but qualifications include skills. Could treat as Skills.
But we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content.
We have content for About the role (About The Job). Responsibilities. Qualifications (minimum and preferred). Pay.
Thus we will output:
About the role
... paragraph ...
Responsibilities
- ...
...
Qualifications
- Bachelor's degree or equivalent practical experience.
- 5 years of experience in program or project management.
- Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).
- Experience working with data analytics tools and reporting platforms.
- 5 years of experience managing cross-functional or cross-team projects.
- Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.
- Experience in managing technical programs with hardware teams.
- Ability to take accountability and ownership for end-to-end project lifecycle.
Pay
US: $159,000 - $230,000 (USD) + 15% bonus target + equity + benefits
We need to preserve ALL substantive information; do not invent or summarize away detail. The About The Job paragraph: we need to copy exactly the text from "About The Job" heading to before responsibilities? Let's extract.
The text after "About The Job" (note capitalization) is:
"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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be responsible for enabling various data center networking deployments by working with cross functional teams to develop end to end strategies that connect our demand, supply, inventory, data center labor and deployment planning. Your role will directly enable improving effectiveness of network planning team and overall network domain. This role requires an individual to leverage strategic and end to end thinking. Successful individuals in this role have strong planning backgrounds with an engineering mindset, while being expert communicators and leaders. They are comfortable with ambiguity and complexity, yet strive to increase maturity in processes. They also have the ability to handle multiple programs at the same time while being highly customer focused. Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's product portfolio possible. We're proud to be our engineers' engineers and love voiding warranties by taking things apart so we can rebuild them. We keep our networks up and running, ensuring our users have the best and fastest experience possible."
We need to preserve that exactly. Ensure we keep punctuation, apostrophes, etc.
Now responsibilities: The list after "Responsibilities Learn more about benefits at Google ." Actually there is a stray sentence: "Learn more about benefits at Google ." That seems like a placeholder. Should we include it? It's not a responsibility; it's a line that likely is a link. According to rule: Remove duplicated lines, and application instructions. This line is not a responsibility but maybe it's a link to benefits. It's not substantive. Probably we should drop it. The responsibilities start after that. So we will list the bullet points:
- Identify changes introduced by large scale business initiatives, drive business requirements and lead development/implementation with engineering teams to successfully land the programs.
- Partner with cross functional teams in deployments, supply chain planning, operations and engineering to identify, develop and lead large scale programs that improve our deployment velocity, inventory efficiency and supply resiliency.
- Develop and lead new forums, reports with key stakeholders and leaders to identify and flag risks, delivery challenges that need escalation, and highlight achievement of key milestones throughout the planning and execution cycles.
- Define, track and report on key performance metrics and raise issues proactively to ensure on-time follow-through.
- Define continuous improvement areas based upon metrics and work with engineering/systems team to establish program roadmaps to deliver the improvements.
We need to keep the exact phrasing.
Now qualifications: we need to combine minimum and preferred. Ensure we keep each bullet exactly as in text.
Minimum qualifications bullets:
- Bachelor's degree or equivalent practical experience.
- 5 years of experience in program or project management.
- Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).
- Experience working with data analytics tools and reporting platforms.
Preferred qualifications bullets:
- 5 years of experience managing cross-functional or cross-team projects.
- Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.
- Experience in managing technical programs with hardware teams.
- Ability to take accountability and ownership for end-to-end project lifecycle.
We'll list them all.
Now Pay: The line: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". We need to preserve all substantive information. Should we include the first sentence? It's about pay determination. That's substantive. So include both sentences.
Thus Pay section Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits
We need to format numbers with commas? The original has no commas: $159000 - $230000. We should keep as is.
Now ensure we don't include any boilerplate like EEO, etc.
Now output only HTML fragment.
Check for any duplicate lines: The responsibilities list includes "Learn more about benefits at Google ." We omitted. Good.
Now final HTML:
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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: Minimum qualifications: Bachelor's degree or equivalent practical experience.5 years of experience in program or project management.Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).Experience working with data analytics tools and reporting platforms. Preferred qualifications: 5 years of experience managing cross-functional or cross-team projects.Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.Experience in managing technical programs with hardware teams. Ability to take accountability and ownership for end-to-end project lifecycle. About The Job: paragraph. Then responsibilities list: bullet points (starting with "Learn more about benefits at Google ." Actually that line is weird: "Learn more about benefits at Google ." It's likely a stray line. Then bullet points: Identify changes introduced by large scale business initiatives, drive business requirements and lead development/implementation with engineering teams to successfully land the programs. Partner with cross functional teams in deployments, supply chain planning, operations and engineering to identify, develop and lead large scale programs that improve our deployment velocity, inventory efficiency and supply resiliency. Develop and lead new forums, reports with key stakeholders and leaders to identify and flag risks, delivery challenges that need escalation, and highlight achievement of key milestones throughout the planning and execution cycles. Define, track and report on key performance metrics and raise issues proactively to ensure on-time follow-through. Define continuous improvement areas based upon metrics and work with engineering/systems team to establish program roadmaps to deliver the improvements. Then after that: "Google is proud to be an equal opportunity workplace..." That's EEO boilerplate, should be removed. Also "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". That's pay info. So we need a Pay section. Also there is mention of benefits: "Learn more benefits at Google ." Actually that line is weird but we can treat as mention of benefits. However we need to include Benefits section only if posting actually states them. There's "Learn more about benefits at Google ." That's a reference but not a description. The posting also says "+ equity + benefits" in pay line. So we have mention of benefits but not details. According to rule: never create Benefits section unless posting actually states them. It does state "benefits" generically but not specifics. Might be considered stating them? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits in the pay line: "+ equity + benefits". So we can include a Benefits section but we need to include substantive content. We have no detail beyond that. Could we include a short
that says "Benefits include equity and other benefits as described by Google." But that might be inventing detail. Better to not create Benefits section if we have no specifics. The rule says "Prefer a few substantive sections over many thin ones." So maybe we omit Benefits section. Pay: we have specific salary range and bonus target etc. So we should include Pay section with that info. Schedule: not mentioned, so omit. Now sections: We could have About the role (the About The Job paragraph). Responsibilities (list). Requirements/Qualifications: we have Minimum qualifications and Preferred qualifications. Could combine into a Qualifications section with two sublists? But we need to use
for section headings only, not subheadings. We could have a Qualifications section with - for each qualification (both minimum and preferred). But we need to differentiate? Not required. Could just list all qualifications.
Alternatively we could have Requirements (minimum) and Preferred qualifications separate sections. But rule: prefer few substantive sections over many thin ones. So maybe combine into one Qualifications section.
Also we might have Skills section? Not explicitly; but qualifications include skills. Could treat as Skills.
But we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content.
We have content for About the role (About The Job). Responsibilities. Qualifications (minimum and preferred). Pay.
Thus we will output:
About the role
... paragraph ...
Responsibilities
- ...
...
Qualifications
- Bachelor's degree or equivalent practical experience.
- 5 years of experience in program or project management.
- Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).
- Experience working with data analytics tools and reporting platforms.
- 5 years of experience managing cross-functional or cross-team projects.
- Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.
- Experience in managing technical programs with hardware teams.
- Ability to take accountability and ownership for end-to-end project lifecycle.
Pay
US: $159,000 - $230,000 (USD) + 15% bonus target + equity + benefits
We need to preserve ALL substantive information; do not invent or summarize away detail. The About The Job paragraph: we need to copy exactly the text from "About The Job" heading to before responsibilities? Let's extract.
The text after "About The Job" (note capitalization) is:
"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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be responsible for enabling various data center networking deployments by working with cross functional teams to develop end to end strategies that connect our demand, supply, inventory, data center labor and deployment planning. Your role will directly enable improving effectiveness of network planning team and overall network domain. This role requires an individual to leverage strategic and end to end thinking. Successful individuals in this role have strong planning backgrounds with an engineering mindset, while being expert communicators and leaders. They are comfortable with ambiguity and complexity, yet strive to increase maturity in processes. They also have the ability to handle multiple programs at the same time while being highly customer focused. Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's product portfolio possible. We're proud to be our engineers' engineers and love voiding warranties by taking things apart so we can rebuild them. We keep our networks up and running, ensuring our users have the best and fastest experience possible."
We need to preserve that exactly. Ensure we keep punctuation, apostrophes, etc.
Now responsibilities: The list after "Responsibilities Learn more about benefits at Google ." Actually there is a stray sentence: "Learn more about benefits at Google ." That seems like a placeholder. Should we include it? It's not a responsibility; it's a line that likely is a link. According to rule: Remove duplicated lines, and application instructions. This line is not a responsibility but maybe it's a link to benefits. It's not substantive. Probably we should drop it. The responsibilities start after that. So we will list the bullet points:
- Identify changes introduced by large scale business initiatives, drive business requirements and lead development/implementation with engineering teams to successfully land the programs.
- Partner with cross functional teams in deployments, supply chain planning, operations and engineering to identify, develop and lead large scale programs that improve our deployment velocity, inventory efficiency and supply resiliency.
- Develop and lead new forums, reports with key stakeholders and leaders to identify and flag risks, delivery challenges that need escalation, and highlight achievement of key milestones throughout the planning and execution cycles.
- Define, track and report on key performance metrics and raise issues proactively to ensure on-time follow-through.
- Define continuous improvement areas based upon metrics and work with engineering/systems team to establish program roadmaps to deliver the improvements.
We need to keep the exact phrasing.
Now qualifications: we need to combine minimum and preferred. Ensure we keep each bullet exactly as in text.
Minimum qualifications bullets:
- Bachelor's degree or equivalent practical experience.
- 5 years of experience in program or project management.
- Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).
- Experience working with data analytics tools and reporting platforms.
Preferred qualifications bullets:
- 5 years of experience managing cross-functional or cross-team projects.
- Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.
- Experience in managing technical programs with hardware teams.
- Ability to take accountability and ownership for end-to-end project lifecycle.
We'll list them all.
Now Pay: The line: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". We need to preserve all substantive information. Should we include the first sentence? It's about pay determination. That's substantive. So include both sentences.
Thus Pay section Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits
We need to format numbers with commas? The original has no commas: $159000 - $230000. We should keep as is.
Now ensure we don't include any boilerplate like EEO, etc.
Now output only HTML fragment.
Check for any duplicate lines: The responsibilities list includes "Learn more about benefits at Google ." We omitted. Good.
Now final HTML:
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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content.
We have content for About the role (About The Job). Responsibilities. Qualifications (minimum and preferred). Pay.
Thus we will output:
About the role
... paragraph ...
Responsibilities
- ... ...
Qualifications
- Bachelor's degree or equivalent practical experience.
- 5 years of experience in program or project management.
- Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.).
- Experience working with data analytics tools and reporting platforms.
- 5 years of experience managing cross-functional or cross-team projects.
- Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making.
- Experience in managing technical programs with hardware teams.
- Ability to take accountability and ownership for end-to-end project lifecycle.
Pay
US: $159,000 - $230,000 (USD) + 15% bonus target + equity + benefits
We need to preserve ALL substantive information; do not invent or summarize away detail. The About The Job paragraph: we need to copy exactly the text from "About The Job" heading to before responsibilities? Let's extract. The text after "About The Job" (note capitalization) is: "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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be responsible for enabling various data center networking deployments by working with cross functional teams to develop end to end strategies that connect our demand, supply, inventory, data center labor and deployment planning. Your role will directly enable improving effectiveness of network planning team and overall network domain. This role requires an individual to leverage strategic and end to end thinking. Successful individuals in this role have strong planning backgrounds with an engineering mindset, while being expert communicators and leaders. They are comfortable with ambiguity and complexity, yet strive to increase maturity in processes. They also have the ability to handle multiple programs at the same time while being highly customer focused. Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's product portfolio possible. We're proud to be our engineers' engineers and love voiding warranties by taking things apart so we can rebuild them. We keep our networks up and running, ensuring our users have the best and fastest experience possible." We need to preserve that exactly. Ensure we keep punctuation, apostrophes, etc. Now responsibilities: The list after "Responsibilities Learn more about benefits at Google ." Actually there is a stray sentence: "Learn more about benefits at Google ." That seems like a placeholder. Should we include it? It's not a responsibility; it's a line that likely is a link. According to rule: Remove duplicated lines, and application instructions. This line is not a responsibility but maybe it's a link to benefits. It's not substantive. Probably we should drop it. The responsibilities start after that. So we will list the bullet points: - Identify changes introduced by large scale business initiatives, drive business requirements and lead development/implementation with engineering teams to successfully land the programs. - Partner with cross functional teams in deployments, supply chain planning, operations and engineering to identify, develop and lead large scale programs that improve our deployment velocity, inventory efficiency and supply resiliency. - Develop and lead new forums, reports with key stakeholders and leaders to identify and flag risks, delivery challenges that need escalation, and highlight achievement of key milestones throughout the planning and execution cycles. - Define, track and report on key performance metrics and raise issues proactively to ensure on-time follow-through. - Define continuous improvement areas based upon metrics and work with engineering/systems team to establish program roadmaps to deliver the improvements. We need to keep the exact phrasing. Now qualifications: we need to combine minimum and preferred. Ensure we keep each bullet exactly as in text. Minimum qualifications bullets: - Bachelor's degree or equivalent practical experience. - 5 years of experience in program or project management. - Experience with supply or demand planning (e.g., demand forecasting, inventory management, resource allocation, etc.). - Experience working with data analytics tools and reporting platforms. Preferred qualifications bullets: - 5 years of experience managing cross-functional or cross-team projects. - Experience with supply/demand planning, material planning, data center infrastructure, or capital investment decision making. - Experience in managing technical programs with hardware teams. - Ability to take accountability and ownership for end-to-end project lifecycle. We'll list them all. Now Pay: The line: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". We need to preserve all substantive information. Should we include the first sentence? It's about pay determination. That's substantive. So include both sentences. Thus Pay sectionIndividual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits
We need to format numbers with commas? The original has no commas: $159000 - $230000. We should keep as is. Now ensure we don't include any boilerplate like EEO, etc. Now output only HTML fragment. Check for any duplicate lines: The responsibilities list includes "Learn more about benefits at Google ." We omitted. Good. Now final HTML: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 Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. As part of the Network Planning team, you will be