Jobs · Project Management · California

Technical Program Manager, Data and Analytics

Google · San Francisco, CA · 3 wk ago
On-siteProject ManagementFull-time
We need to output only HTML fragment, using

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also we must include a section only when posting has real specific content; never emit heading with filler placeholder like "commensurate with experience". So we need to extract sections. Let's parse the posting: - Opening lines: "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. Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's some legal/EEO boilerplate? It's about fair chance, etc. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This includes legal statements about fair chance, etc. So we should remove those lines. - Benefits list: "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 format as a Benefits section with
  • . Also note there is a line: "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 location info, maybe not a section heading; could be part of About the role? Not sure. The instruction: we can include a section only when posting has real specific content. Could we include a "Locations" section? Not among allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So location info maybe goes under About the role? Or we could drop it if not fitting. But we must preserve ALL substantive information; we cannot drop location info if it's substantive. However we can embed it in a paragraph under About the role or maybe under Requirements? The location is not a requirement but a detail about where you can work. Could be part of About the role. We'll include it in About the role paragraph. - Minimum qualifications: list. - Preferred qualifications: list. - About The Job: paragraph describing role. - Responsibilities: bullet list. - 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". That's pay info; we need a Pay section. - Schedule: Not mentioned. So we should not create a Schedule section. - Skills: Not explicitly listed; maybe we can infer from qualifications? But we should not create a Skills section unless there is explicit content. The posting mentions abilities: "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." Those could be skills. But we have a Skills heading allowed. Should we create a Skills section? The instruction: Prefer a few substantive sections over many thin ones. We could combine skills into Qualifications or Requirements. But we have separate headings for Requirements and Qualifications. Usually Requirements = minimum qualifications, Qualifications = preferred qualifications. Skills could be separate but we might not need it if we can incorporate into Qualifications. However we have both Minimum qualifications and Preferred qualifications; we could treat Minimum as Requirements, Preferred as Qualifications. Then Skills maybe not needed. But we have ability statements that could be considered skills; we could put them under Qualifications as bullet points. Let's see. We need to avoid duplication. Let's extract substantive content: - About the role: The paragraph starting "About The Job A problem isn’t truly solved..." plus location note maybe. - Responsibilities: bullet list after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google . 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." We need to split into bullet points. The text seems to be a run-on; we can separate by sentences. - Requirements (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." - Qualifications (preferred): "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: as extracted. - 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 should not include the boilerplate lines about application window, fair chance, etc. Also remove "Learn more about benefits at Google ." (that's a link instruction). Also remove EEO statements. Also remove duplicated lines? Not seeing duplicates. Now produce HTML fragment with headings

    for each section we include. We need to decide order: Typically About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Could also include Skills but we can skip. We must not include empty sections. Let's craft:

    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. 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. 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.

    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.
    • Collaborate on ETL data pipelines, build predictive and optimization models, implement tooling visualization/application, and configure 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.

    Requirements

    • Bachelor's degree in a technical field, or equivalent practical experience.
    • 2 years of experience in program management.
    • 2 years of experience in the energy industry.
    • 2 years of development experience in data engineering, data science, or application engineering.

    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

    • 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 (

Similar jobs