Regional Manager, Google Cloud, Government Affairs and Public Policy

We need to output HTML fragment with sections: About the role? Actually the posting includes "About the job" paragraph. Also "Responsibilities". Also "Minimum qualifications" and "Preferred qualifications". Also "Pay" (Individual pay is determined... US: $181000 - $247000 + 20% bonus target + equity + benefits). Also maybe "Benefits"? The posting mentions benefits but not details; we have "equity + benefits". The rule: include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Pay is stated: US: $181000 - $247000 + 20% bonus target + equity + benefits. So we can include Pay section with that content. Benefits: they mention "equity + benefits" but not specifics; we could include Benefits section only if specific benefits listed. The posting says "equity + benefits" but no detail. That might be considered filler? It says "benefits" but not specific. The rule: never create Benefits sections unless posting actually states them. It does state "benefits" but not specifics. Might be considered too vague? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (equity + benefits). That is a statement, albeit vague. I'd include Benefits section with that statement? But they said avoid filler like "varies", "TBD". "equity + benefits" is not filler but still vague. I'd include Benefits with that sentence. Also note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Remote locations: Utah, USA; Nevada, USA." That's location info; could be included maybe as a short paragraph under About the role? Not a heading. We can include a

for that note. Also "Minimum qualifications:" and "Preferred qualifications:" are headings? We'll use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has "Minimum qualifications" and "Preferred qualifications". Could combine into a Qualifications section with two subparts? But we must use

for section headings; we could have a Qualifications section and inside we can have

or

. The rule: Use
• for any list of duties/requirements/benefits, and

  for prose. So for qualifications we can make a

  list. Similarly responsibilities list. Also "About the job" paragraph: we can put under About the role heading. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO etc. Remove duplicated lines, application instructions. We need to preserve all substantive information. Let's extract substantive content: - Note about preferred working location: Remote locations: Utah, USA; Nevada, USA. - Minimum qualifications: * Bachelor's degree or equivalent practical experience. * 10 years of experience working on technology policy issues within government, industry, think tanks, public interest groups, law, or relevant industry associations. * Experience within state and local government. - Preferred qualifications: * Experience leading or supporting cross-functional teams to deliver economic development projects, including navigating site selection, permitting and community engagement in heavy industrial sectors. * Experience with government procurement processes. * Ability to travel up to 50% as needed. - About the job (prose): * In this role, you will be involved in collaborating with Google Cloud and other internal teams to advance Google’s Cloud business and technical infrastructure needs, leading government affairs and public policy matters within key state and local markets. You will serve as Google Cloud's representative to state policymakers, government executives, IT decision makers, and key third-party groups in your markets. A crucial aspect of this position is working with Google Cloud stakeholders to support business growth and public policy objectives at the state and local levels, proactively addressing both risks and opportunities. You will also engage with key trade associations vital for advancing Google Cloud’s public policy, infrastructure and business goals. * Google takes its responsibilities seriously, including engaging with government and other stakeholders on important public policy challenges. The Government Affairs and Public Policy (GAPP) team leads the company’s engagement with executive branch officials, legislators, regulators and third-parties in the formation of public policy. Working closely with Google leaders, GAPP seeks to identify key policy issues, listen carefully to others’ views and opinions, and distill and share the company’s perspective on those issues with external stakeholders. While we focus on challenges affecting the internet, our issue areas are increasingly broad and encompass many areas where public policy, business, and technology intersect. - Responsibilities (list): * Develop and lead Google Cloud's policy and government affairs strategy for assigned regional states. * Manage and coordinate a network of agreement lobbyists and public affairs firms to advance proactive policy engagement. * Build and maintain trusted relationships with governors’ offices, state legislators, local elected officials, state agencies, local permitting authorities, and trade associations. * Shape and advance the company’s positions on key issues, including government procurement, energy, tax policy, permitting, and infrastructure development. * Track and analyze legislation, regulation, and local policy trends that could affect the company’s operations, investment, or growth. * Partner with internal technical teams and external upstream and downstream stakeholder groups to advance technical infrastructure needs for our users and customers, ensuring a unified approach regarding economic, social and environmental benefits of Google Cloud investments in new and existing markets. - Pay: Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $181000 - $247000 (USD) + 20% bonus target + equity + benefits - Benefits: maybe we can include the "equity + benefits" part under Pay? But we could also make a Benefits section with that phrase. However the Pay section already includes equity + benefits. To avoid duplication, maybe we just include Pay section with that sentence, and not a separate Benefits section. The rule: never create Benefits sections unless posting actually states them. It does state benefits but it's within Pay line. Could still create Benefits but would duplicate. Safer to omit Benefits section. - Schedule: not mentioned. - Skills: not explicitly listed; we could infer but not create. Thus sections: About the role, Responsibilities, Qualifications (maybe combine Minimum and Preferred), Pay. We need to use

  for each section heading. Inside each section, use

  for prose,

  • for lists. For Qualifications, we could have two subheadings? Not allowed; only

    for section headings. Could we have

    Minimum qualifications and

    Preferred qualifications? Those are headings but not in the allowed list? The allowed list includes Requirements, Qualifications, Skills, etc. But we can still use

    for any section heading; the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. So we can use

    for Minimum qualifications and Preferred qualifications as separate sections. That would be fine. But we need to avoid too many thin sections. However we have distinct content; maybe better to have a Qualifications section with two

    paragraphs: one for Minimum, one for Preferred. Or we could use

    with items and maybe a preceding

    label. But the rule: Use

    • for any list of duties/requirements/benefits. So we can make a
      for Minimum qualifications and another for Preferred qualifications. Could wrap each in a but we only output HTML fragment; we can just have

      Minimum qualifications

      ... then

      Preferred qualifications

      ... That seems okay. Now About the role: we have the note about location plus the About the job prose. Could combine into a

      that includes both sentences. The note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Remote locations: Utah, USA; Nevada, USA." That's a sentence. Then the About the job prose (multiple sentences). We'll put them in one

      or two? Probably one

      containing both. Responsibilities:

      Responsibilities

      with each duty as
      • . Pay:

        Pay

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

        Now ensure we removed boilerplate: EEO, accommodation, etc. Check for duplicated lines: none. Now output only HTML fragment, no /, no markdown. Let's craft:

        About the role

        Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Remote locations: Utah, USA; Nevada, USA. In this role, you will be involved in collaborating with Google Cloud and other internal teams to advance Google’s Cloud business and technical infrastructure needs, leading government affairs and public policy matters within key state and local markets. You will serve as Google Cloud's representative to state policymakers, government executives, IT decision makers, and key third-party groups in your markets. A crucial aspect of this position is working with Google Cloud stakeholders to support business growth and public policy objectives at the state and local levels, proactively addressing both risks and opportunities. You will also engage with key trade associations vital for advancing Google Cloud’s public policy, infrastructure and business goals. Google takes its responsibilities seriously, including engaging with government and other stakeholders on important public policy challenges. The Government Affairs and Public Policy (GAPP) team leads the company’s engagement with executive branch officials, legislators, regulators and third-parties in the formation of public policy. Working closely with Google leaders, GAPP seeks to identify key policy issues, listen carefully to others’ views and opinions, and distill and share the company’s perspective on those issues with external stakeholders. While we focus on challenges affecting the internet, our issue areas are increasingly broad and encompass many areas where public policy, business, and technology intersect.

        Minimum qualifications

        • Bachelor's degree or equivalent practical experience.
        • 10 years of experience working on technology policy issues within government, industry, think tanks, public interest groups, law, or relevant industry associations.
        • Experience within state and local government.

        Preferred qualifications

        • Experience leading or supporting cross-functional teams to deliver economic development projects, including navigating site selection, permitting and community engagement in heavy industrial sectors.
        • Experience with government procurement processes.
        • Ability to travel up to 50% as needed.

        Responsibilities

        • Develop and lead Google Cloud's policy and government affairs strategy for assigned regional states.
        • Manage and coordinate a network of agreement lobbyists and public affairs firms to advance proactive policy engagement.
        • Build and maintain trusted relationships with governors’ offices, state legislators, local elected officials, state agencies, local permitting authorities, and trade associations.
        • Shape and advance the company’s positions on key issues, including government procurement, energy, tax policy, permitting, and infrastructure development.
        • Track and analyze legislation, regulation, and local policy trends that could affect the company’s operations, investment, or growth.
        • Partner with internal technical teams and external upstream and downstream stakeholder groups to advance technical infrastructure needs for our users and