Technical Program Manager, Data and Analytics

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Job" which is a description. Also responsibilities list. Minimum qualifications list. Preferred qualifications list. Benefits list. Pay info. Also location note? The location note is about preferred working location list; that's maybe not a section but could be included as a paragraph. Also note about application window date etc. We need to preserve all substantive info, remove boilerplate like EEO, equal opportunity, accommodation instructions, legal, etc. Also remove duplicated lines. Also remove navigation/cookie etc. Also remove "Learn more about benefits at Google ." maybe that's a link but we can keep as part of responsibilities? It's a sentence inside responsibilities; we can keep it but it's not substantive? It's a reference; maybe keep as part of responsibilities sentence. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we need About the role (the "About The Job" paragraph). Responsibilities (list). Requirements? Could be minimum qualifications? Could treat as Requirements. Qualifications maybe preferred qualifications? Or we could combine. The instruction: Use headings for those specific names. We need to decide which sections to include. We have content: About The Job (description). Responsibilities (list). Minimum qualifications (list). Preferred qualifications (list). Benefits (list). Pay (salary range + bonus + equity). Schedule? Not mentioned. So we should not include Schedule heading because no specific content. Skills? Not explicitly listed; maybe we could treat qualifications as skills but better to follow instruction: only include sections when posting has real specific content. We have qualifications content, so we can include Qualifications heading (maybe split into Minimum and Preferred?). But we have only one Qualifications heading allowed; we could put both minimum and preferred under Qualifications with sublists? Or we could have Requirements for minimum qualifications and Qualifications for preferred. The instruction list includes Requirements and Qualifications separate. So we can use Requirements for minimum qualifications, Qualifications for preferred qualifications. That seems appropriate. Skills heading? Not present; we could omit. Benefits heading present. Pay heading present. Schedule heading omitted. Thus output:

About the role

... paragraph from About The Job ...

Responsibilities

• Improve, maintain (including debug) and run machine learning/optimization models and other advanced analytical tools to centralize energy and power delivery and support energy agreement due diligence.
• Collaborating on ETL data pipelines, building predictive and optimization models, implementing tooling visualization/application, configuration for deployment.
• Scale Minimum Viable Product (MVPs) into production systems and work with software engineers to harden prototypes into production-grade solutions — establishing the testing, monitoring, code quality, and deployment standards then manage execution through to launch.
• Rapid AI prototyping with domain experts directly with energy and data center domain experts to rapidly prototype AI-enabled solutions, using their expertise to shape the problem framing and validate outputs.
• Coordinate cross-functional stakeholder groups to make decisions about data, feature requests, model development and give updates on ongoing work stream and key milestones.

Note: The sentence "Learn more about benefits at Google ." appears after responsibilities heading? Actually in the text: "Responsibilities Learn more about benefits at Google . Improve, maintain..." So it's like a stray sentence. We should keep substantive info; that sentence is a link suggestion; maybe we can incorporate as part of responsibilities? It's not a duty. Probably we can drop it as it's not a responsibility. The instruction: preserve ALL substantive information; do not invent or summarize away detail. That sentence is not a responsibility but it's a note. Might be considered boilerplate? It's not legal/EEO; it's a internal link. Might be considered not substantive. Safer to keep it as a paragraph after responsibilities? But it's not a duty. Could be considered a note. I'd include it as a

after the

maybe. But the instruction: Use

for prose. So we can put that sentence in a

. Thus after responsibilities list, add

Learn more about benefits at Google .

Now Requirements (minimum qualifications): Minimum qualifications: Bachelor's degree in a technical field, or equivalent practical experience. 2 years of experience in program management. 2 years of experience in energy industry. 2 years of development experience in data engineering, data science, or application engineering. We need to output as list? Could be prose or list. Since it's a list of items, better as
• . Thus:

  Requirements

  • Bachelor's degree in a technical field, or equivalent practical experience.
  • 2 years of experience in program management.
  • 2 years of experience in energy industry.
  • 2 years of development experience in data engineering, data science, or application engineering.
  Qualifications (preferred): Preferred qualifications: Master's degree in Operations Research, Engineering, Economics, or a related quantitative field. Experience in the energy sector — wholesale power markets, PPA/ESA structures, nodal pricing, load or price forecasting, storage economics, or carbon-free energy accounting. Experience quickly building prototypes, and taking prototypes to production, including working with software engineers on testing, monitoring, and deployment standards. Experience building full-stack analytics tooling, including data pipelines, backend services, and visualization or application front ends. Ability to translate technical analysis into recommendations for executive and non-technical audiences. Passionate about AI solutions and ability to quickly prototype to solve business challenges. We can break into list items. Thus:

  Qualifications

  • Master's degree in Operations Research, Engineering, Economics, or a related quantitative field.
  • Experience in the energy sector — wholesale power markets, PPA/ESA structures, nodal pricing, load or price forecasting, storage economics, or carbon-free energy accounting.
  • Experience quickly building prototypes, and taking prototypes to production, including working with software engineers on testing, monitoring, and deployment standards.
  • Experience building full-stack analytics tooling, including data pipelines, backend services, and visualization or application front ends.
  • Ability to translate technical analysis into recommendations for executive and non-technical audiences.
  • Passionate about AI solutions and ability to quickly prototype to solve business challenges.
  Benefits: list as given. Benefits for this role include: Health, dental, vision, life, disability insuranceRetirement Benefits: 401(k) with company matchPaid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employmentSick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeksBaby Bonding Leave: 18 weeksHolidays: 13 paid days per year We need to parse into items. The text is jammed; we need to separate. Let's list: - Health, dental, vision, life, disability insurance - Retirement Benefits: 401(k) with company match - Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment - Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance - Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks - Baby Bonding Leave: 18 weeks - Holidays: 13 paid days per year Thus:

  Benefits

  • Health, dental, vision, life, disability insurance
  • Retirement Benefits: 401(k) with company match
  • Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
  • Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
  • Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
  • Baby Bonding Leave: 18 weeks
  • Holidays: 13 paid days per year
  Pay: 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 We need to output as

  Pay

  and then a

  with that info. Thus:

  Pay

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

  We might format numbers with commas for readability but preserve original? Original: $138000 - $197000. Could keep as is or add commas; but not invent. Better keep as given: $138000 - $197000. Thus: US: $138000 - $197000 (USD) + 15% bonus target + equity + benefits Now also there is location note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: New York, NY, USA; Atlanta, GA, USA; Austin, TX, USA; Kirkland, WA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA; Thornton, CO, USA." That's substantive info about locations. Should we include? There's no heading for Locations; we could put as a

  after Pay maybe. Not required to have a heading. So we can add a paragraph. Also there is info about application window: "The application window will be open until at least October 12, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." Also San Francisco Fair Chance Ordinance note, Washington state law note about benefits. Those are substantive? They are legal notices but maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Fair Chance Ordinance and Washington state law note might be considered legal boilerplate. However they are specific to location and benefits. Might be considered legal. I'd remove them as they are legal notices. The instruction: remove legal/EEO/equal-opportunity/scam-warning boilerplate. So drop those lines. Also remove duplicated lines. Thus final HTML fragment includes sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Plus paragraphs for location note and maybe application window? Application window is also maybe not boilerplate but it's about timing; could be considered substantive. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Application window is not application instructions; it's about timing. Might be considered substantive. However it's not a section heading; we could add a

  after Pay or before. But the instruction says "Prefer a few substantive sections over many thin ones." So we could incorporate that info into a paragraph under About the role or as a separate paragraph. I'll add a paragraph after Pay