Technical Program Manager, Energy Risk

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 content. We need to parse the posting. First, remove boilerplate: The first line about San Francisco Fair Chance Ordinance etc. That's a note about qualified applications with arrest or conviction records. That's a legal statement; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is about Fair Chance Ordinance; likely considered legal boilerplate, remove. Next: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: San Francisco, CA, USA; New York, NY, USA." This is location info; maybe we keep as part of a short paragraph? It's not a heading; we can embed in a

maybe under a generic intro? But we have no heading for location. Could include as a paragraph before sections. Then "Minimum qualifications:" list. Then "Preferred qualifications:" list. Then "About The Job" paragraph. Then "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $192000 - $278000 (USD) + 20% bonus target + equity + benefits". This gives Pay and benefits info. So we need a Pay section (maybe also Benefits). The sentence includes benefits mention; we could have a Benefits section summarizing that benefits are included (but not detailed). However rule: never create Benefits section unless posting actually states them. It says "+ equity + benefits". That's a statement that benefits are included, but not specific. Might be considered vague; but it's still stating benefits exist. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (generic). So we could include a Benefits section with that statement? But we should avoid filler like "benefits" without detail? The rule says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "benefits" is not placeholder; it's a statement that benefits are included. Could be okay. Pay: we have a range and bonus target etc. So we can include Pay section. Responsibilities: we have a list after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google ." Then bullet points? The responsibilities are listed as sentences after that line. We need to extract them. Let's extract responsibilities: - Establish, manage, and refine frameworks to measure and mitigate complex risk exposures (e.g., price, shape and counterparty risks) across Google’s global, multi-gigawatt energy portfolio. - Translate risk analytics, quantitative metrics, and wholesale power market dynamics into actionable insights that shape Google's long-term energy strategy and infrastructure footprint. - Lead high-impact technical programs bridging Energy Origination, Procurement, Operations, Finance, and Data Science to embed robust risk frameworks into portfolio decision-making. - Provide strategic guidance to commercial transaction teams on optimal risk allocation, hedging, and mitigation strategies to ensure complex agreements fall within acceptable risk limits. - Collaborate with software and data engineers to build and scale automated, programmatic technical tools and analytics dashboards for portfolio and agreement evaluation. We need to put these in

• . Now Minimum qualifications: list: - Bachelor's degree in a technical or quantitative field (e.g., Engineering, Mathematics, Computer Science), or equivalent practical experience. - 8 years of experience in program management. - Experience in technical program management, bridging the gap between quantitative risk modeling, financial analysis, and software/data engineering. - Experience in the energy sector, with wholesale power markets, renewable energy transactions, or utility-scale portfolio management. - Experience of energy agreement structuring, energy risk management principles, and quantitative analysis. Preferred qualifications: - Master's degree in a quantitative field such as Mathematics, Statistics, Engineering, or a related discipline. - 8 years of experience managing cross-functional or cross-team projects. - Expertise in major wholesale electricity markets (e.g., PJM, ERCOT, CAISO) and experience structuring complex transactions in multiple regions globally. - Proficiency in programming or query languages (e.g., Python, SQL, C++) to build, review, or scale advanced financial mathematics models, including option pricing, stochastic modeling, and Monte Carlo simulations. Now About The Job: paragraph(s). We have: "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 AI and Infrastructure team is redefining what’s possible. We empower Google customers with breakthrough capabilities and insights by delivering AI and Infrastructure at unparalleled scale, efficiency, reliability and velocity. Our customers include Googlers, Google Cloud customers, and billions of Google users worldwide. We're the driving force behind Google's groundbreaking innovations, empowering the development of our cutting-edge AI models, delivering unparalleled computing power to global services, and providing the essential platforms that enable developers to build the future. From software to hardware our teams are shaping the future of world-leading hyperscale computing, with key teams working on the development of our TPUs, Vertex AI for Google Cloud, Google Global Networking, Data Center operations, systems research, and much more." We can put that in

  under heading About the role? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use "About the role" heading for the About The Job content. Now we need to decide sections: About the role, Responsibilities, Minimum qualifications (maybe Requirements), Preferred qualifications (maybe Qualifications or Skills). The instruction list includes Requirements, Qualifications, Skills. We have Minimum qualifications and Preferred qualifications. Could combine into Requirements (minimum) and Qualifications (preferred). Or we could have Requirements for minimum, Qualifications for preferred. Skills could be derived from preferred qualifications (proficiency in programming). But we should not invent sections; we should only include sections when posting has real specific content. We have content for both minimum and preferred qualifications. So we can have two sections: Requirements (minimum) and Qualifications (preferred). Or we could have Requirements and Qualifications. The instruction list includes both; we can use them. We also have Pay and Benefits sections. Schedule: not mentioned, so omit. Skills: we could extract from preferred qualifications: proficiency in programming or query languages (Python, SQL, C++). That's a skill. But we already have Qualifications section covering preferred qualifications; maybe we don't need separate Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits. Check if we need to include "Skills" separate? Not needed. Now we need to ensure we don't repeat job title as heading. Not needed. We need to strip boilerplate: The first line about Fair Chance Ordinance, the note about location (maybe we keep as a short paragraph before sections). The location note is not boilerplate; it's specific info about preferred working location. We could include it as a paragraph under a heading? There's no heading for location; maybe we just include it as a

  before sections. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can put location note in a short

  . Also the line "Learn more about benefits at Google ." appears in responsibilities line; we should remove that as it's a link instruction; it's boilerplate? It's part of responsibilities line but we can strip that phrase. The responsibilities line: "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google ." Then the bullet list. So we should remove "Learn more about benefits at Google ." as it's not a responsibility. So responsibilities start after that. Now we need to 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: San Francisco, CA, USA; New York, NY, USA.

  About the role

  [the about job paragraph]

  Responsibilities

  • Establish, manage, and refine frameworks to measure and mitigate complex risk exposures (e.g., price, shape and counterparty risks) across Google’s global, multi-gigawatt energy portfolio.
  • Translate risk analytics, quantitative metrics, and wholesale power market dynamics into actionable insights that shape Google's long-term energy strategy and infrastructure footprint.
  • Lead high-impact technical programs bridging Energy Origination, Procurement, Operations, Finance, and Data Science to embed robust risk frameworks into portfolio decision-making.
  • Provide strategic guidance to commercial transaction teams on optimal risk allocation, hedging, and mitigation strategies to ensure complex agreements fall within acceptable risk limits.
  • Collaborate with software and data engineers to build and scale automated, programmatic technical tools and analytics dashboards for portfolio and agreement evaluation.

  Requirements

  • Bachelor's degree in a technical or quantitative field (e.g., Engineering, Mathematics, Computer Science), or equivalent practical experience.
  • 8 years of experience in program management.
  • Experience in technical program management, bridging the gap between quantitative risk modeling, financial analysis, and software/data engineering.
  • Experience in the energy sector, with wholesale power markets, renewable energy transactions, or utility-scale portfolio management.
  • Experience of energy agreement structuring, energy risk management principles, and quantitative analysis.

  Qualifications

  • Master's degree in a quantitative field such as Mathematics, Statistics, Engineering, or a related discipline.
  • 8 years of experience managing cross-functional or cross-team projects.
  • Expertise in major wholesale electricity markets (e.g., PJM, ERCOT, CAISO) and experience structuring complex transactions in multiple regions globally.
  • Proficiency in programming or query languages (e.g., Python, SQL, C++) to build, review, or scale advanced financial mathematics models, including option pricing, stochastic modeling, and Monte Carlo simulations.

  Pay

  US: $192,000 - $278,000 (USD) + 20% bonus target + equity

  Benefits

  Benefits are included as part of the compensation package.

  We need to ensure we didn't include any filler like "commensurate with experience". Not present. Check that we preserved all substantive information: we kept location note, about job, responsibilities, minimum qualifications, preferred qualifications, pay, benefits. We omitted the line about "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." That's somewhat generic; we could incorporate into Pay section as a sentence. The rule: preserve ALL substantive information; do not invent or summarize away detail. That sentence is substantive; we should include it. We can add it to Pay section as a

  before the range. Thus Pay section:

  Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $19