Energy Commercial Structuring Analytics Associate

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines about Fair Chance Ordinance? That's legal boilerplate; we should remove. Also remove "In accordance with Washington state law, we are highlighting our comprehensive benefits package..."? That's part of benefits description; but it's a statement about benefits being available; we can keep benefits details. However the sentence "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." is somewhat boilerplate but it's referencing benefits; we could keep it as part of benefits intro? Might be considered legal boilerplate; but it's not EEO. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This sentence is legal (Washington state law) but it's about benefits. Might be considered legal boilerplate; but it's not EEO. Safer to keep benefits details but maybe drop that sentence. We'll keep the benefits list. We need to extract sections: - About the role: The posting includes "About The Job" paragraph: "In this role, you will support the financial analytics engine..." etc. Also earlier there is "About The Job" heading. So we can put that content under

About the role

with

. - Responsibilities: There's a "Responsibilities" heading then bullet list items. We'll capture those. - Requirements: There's "Minimum qualifications:" and "Preferred qualifications:" maybe combine into Requirements? The instruction: Use sections Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = minimum qualifications, Qualifications = preferred qualifications, Skills = specific skills/experience. We have: Minimum qualifications: - Bachelor's degree in Finance, Economics, Engineering, Mathematics, Business, or equivalent practical experience. - 5 years of experience in financial modeling, valuation, or financial analysis within the energy, utilities, or infrastructure sectors. Preferred qualifications: - 5 years of experience in energy projects or infrastructure project financial analytics and financial structuring and strategic analysis. - Experience with financial analysis for energy transactions, including project financial modeling across various energy agreement types ranging from utility supply to PPAs, etc. - Ability to build strong relationships with both internal and with external partners. - Excellent communication and influencing skills. - Ideally you have led, worked on or supported agreement negotiations and drafting in the infrastructure field, preferably power generation or power infrastructure. We could also extract Skills: maybe the bullet points about ability to build relationships, communication, influencing, negotiations, etc. But we already have them in preferred qualifications. Could split: Requirements = minimum qualifications; Qualifications = preferred qualifications; Skills = maybe the specific abilities like "Ability to build strong relationships...", "Excellent communication and influencing skills.", "Ideally you have led...". But that seems overlapping. Better to follow instruction: Use sections only when posting has real specific content. We have content for Requirements (minimum qualifications). We have content for Qualifications (preferred qualifications). We have content for Skills? Could treat the bullet points about ability, communication, influencing, negotiations as Skills. But they are already in preferred qualifications. To avoid duplication, we could put them under Skills and keep Qualifications maybe empty? But we must not emit a heading followed by filler/placeholder text. So if we put Qualifications heading, we need real specific content. We could move the preferred qualifications to Qualifications section, and then Skills could be something else like maybe "Experience with financial analysis for energy transactions..." but that's also in preferred. Hmm. Alternative: Use Requirements for minimum qualifications, Qualifications for preferred qualifications, and Skills for the specific skill bullets (ability to build relationships, communication, influencing, negotiations). But then we would duplicate some content if we also list them under Qualifications. Better to not duplicate. So we could assign: - Requirements: Minimum qualifications (degree + 5 years experience) - Qualifications: Preferred qualifications (5 years experience in energy projects, experience with financial analysis for energy transactions, ability to build relationships, excellent communication/influencing, ideally led negotiations) - Skills: maybe we could extract specific technical skills: financial modeling, valuation, financial analysis, project financial modeling, etc. But those are already in requirements/qualifications. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But headings are prescribed; we must use them if we have content. We could have only Requirements and Qualifications sections, and skip Skills if no distinct content. But we have some skill-like content that could go under Skills. However we could also incorporate them into Qualifications (makes Qualifications richer). Then we would not need Skills section. That seems acceptable: we have content for Requirements and Qualifications; we can omit Skills, Benefits, Pay, Schedule if they have content. Benefits we have content. Pay we have content: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $163000 - $236000 (USD) + 15% bonus target + equity + benefits". That's specific pay range. So we should include Pay section. Schedule: No mention of schedule (hours, remote, etc). There's a note about preferred working location but not schedule. So we omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to extract content precisely, preserving all substantive info, no invention, no boilerplate. Let's gather each section's content. About the role: The paragraph after "About The Job": "In this role, you will support the financial analytics engine behind frameworks, partnerships, energy supply agreements, and generation strategy that underpin Google's Americas data center energy team. You will assist in financial and structuring analytics related to the negotiations and execution of energy agreements retail, wholesale, deregulated and regulated energy markets. You will track industry financial trends, maintain financial structuring benchmarks, support agreement teams in financial analysis and modeling through transactions and strategic planning. As part of agreement teams, you will help prepare and present agreements for approval while ensuring alignment across accounting and finance partner teams. 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 should keep that as a single

(maybe multiple sentences). No need to split. Responsibilities: Under "Responsibilities" heading we have bullet points (starting with "Learn more about benefits at Google ." Actually that line seems like a stray link; we should remove boilerplate like "Learn more about benefits at Google ." That's likely a link; we should remove as it's not a responsibility. The bullet points after that: - Support the commercial structuring analytics program, helping to build energy strategy, structure and evaluate energy agreements in support of the Americas data center portfolio. - Be responsible for assisting in the evaluation of transactions across partnerships, portfolio frameworks, utility energy supply, Independent Power Producer (IPP) energy supply, Power Purchase Agreements (PPAs), and other types of energy agreements. - Assist in maintaining up-to-date benchmarks for industry standard financial metrics, project capex/opex benchmarks. - Play a role in transactions, helping to shape agreement teams' approach to negotiations and structured solutions. - Help prepare and present agreement approval materials and work with cross-functional partners in Accounting, Finance, etc., to align on a common set of agreement analytics and metrics. - Help develop a standard set of modeling tools and focus on automation. We should keep each as

inside

. Requirements: Minimum qualifications: - Bachelor's degree in Finance, Economics, Engineering, Mathematics, Business, or equivalent practical experience. - 5 years of experience in financial modeling, valuation, or financial analysis within the energy, utilities, or infrastructure sectors. We'll put as
• . Qualifications: Preferred qualifications (including ability, communication, etc.): - 5 years of experience in energy projects or infrastructure project financial analytics and financial structuring and strategic analysis. - Experience with financial analysis for energy transactions, including project financial modeling across various energy agreement types ranging from utility supply to PPAs, etc. - Ability to build strong relationships with both internal and with external partners. - Excellent communication and influencing skills. - Ideally you have led, worked on or supported agreement negotiations and drafting in the infrastructure field, preferably power generation or power infrastructure. We'll put as
  • . Benefits: The benefits list after "Benefits for this role include:" includes: 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 We should format as
    • each. Note: The line "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." is maybe boilerplate; we can drop it. Pay: The pay info: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $163000 - $236000 (USD) + 15% bonus target + equity + benefits" We should keep as

      maybe two sentences. Could split into

      for first sentence and

      for second? But we can combine into one

      . It's fine. We must not include any other boilerplate like EEO, accommodation, etc. Now produce HTML fragment:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Qualifications

      • ...
      ...

      Benefits

      • ...
      ...

      Pay

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

      Make sure no extra whitespace issues. Output only HTML. Check for any leftover boilerplate: We removed Fair Chance Ordinance lines, EEO lines, accommodation lines, "Learn more about benefits at Google ." Also removed "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: San Francisco, CA, USA; Kirkland, WA, USA; New York, NY, USA." That's location info, not required; we can drop as it's not a section heading. Also removed "Google is proud to be an equal opportunity workplace..." etc. Now ensure we preserved all substantive info: Did we miss any? The "About The Job" also includes "Google Cloud accelerates every organization’s ability..." we kept. Good. Responsibilities: we kept all six bullets. Requirements: two bullets. Qualifications: five bullets. Benefits: seven items. Pay: one paragraph. Check that we didn't miss any responsibility like "Learn more about benefits at Google ." we removed.