Community Development Manager, Data Center Strategic Partnerships

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading (not given). Do NOT put Job ID/requisition numbers as headings — none present. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Important: include a section ONLY when posting has real, specific content for it — never emit a 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. We need to parse the posting. Let's extract sections: - About the role? The posting includes "About The Job" paragraph. That's about the role. So we can have

  About the role

  with that paragraph. - Responsibilities: There's a "Responsibilities" heading then bullet points (list). We need to extract bullet points. - Requirements: Minimum qualifications: bullet list. - Qualifications: Preferred qualifications: bullet list. - Skills: Not explicitly listed; maybe we can infer from responsibilities? But we should only include if posting has real specific content. There's no explicit "Skills" section. So we should not create Skills heading. - Benefits: The posting mentions "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". It mentions benefits but not details. It says "+ benefits". That's not specific detail; it's just mention of benefits but not enumerated. The rule: never create Benefits section unless posting actually states them. It states "benefits" generically but not specifics. Should we include? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (just the word). However, we need to consider if that counts as stating them. It says "+ benefits" but no detail. It might be considered stating benefits exist, but not specifics. The rule about placeholder text: we should not create a section if content would be filler like "not specified". Since we have no detail, maybe we should not include Benefits section. However, we could include a short

  that says "Benefits: includes equity, bonus target, etc." But that would be adding detail not present? Actually we have "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". That gives pay range, bonus target, equity, and mentions benefits. So we have Pay info. So we should create Pay section with that sentence. Benefits we could maybe include as part of Pay? But we could also create Benefits section with the mention of benefits (but no detail). The rule says never create Benefits section unless posting actually states them. It does state "benefits". But it's vague. Might be okay to include a short

  that says "Benefits: includes equity, bonus target, etc." but that adds interpretation. Safer to not create Benefits section, but we could include a short note under Pay that mentions benefits. However, the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one Pay section that includes the pay and mention of benefits. But they said use headings for Benefits separate if present. Since we don't have detail, maybe we skip Benefits. - Schedule: The posting mentions hybrid work location policy, remote location: Ohio, USA. Also "This role is not remote, but supports a site that is not yet announced. Candidates must be able to adhere to our hybrid work location policy. Remote location: Ohio, USA." That gives some schedule/hybrid info. So we could create Schedule section with that info. It's specific: hybrid work location policy, remote location Ohio. So we can include Schedule. - Requirements: Minimum qualifications bullet list. - Qualifications: Preferred qualifications bullet list. - Skills: Not present. - About the role: we have the "About The Job" paragraph. - Responsibilities: bullet list. Now we need to strip boilerplate: EEO statements, accommodation, legal, etc. Also remove duplicated lines, application instructions like "Learn more about benefits at Google ." Actually that line appears under Responsibilities? The posting: "Responsibilities Learn more about benefits at Google . Engage with key opinion formers..." That seems like a stray line. We should remove "Learn more about benefits at Google ." as it's likely a link placeholder. Also remove "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits". That's pay info, we keep. Also remove "Google is proud to be an equal opportunity workplace..." etc. Now let's extract content. First, "About The Job" paragraph: "As a Program Manager at Google, you’ll lead complex, multi-disciplinary projects from start to finish — working with stakeholders to plan requirements, manage project schedules, identify risks, and communicate clearly with cross-functional partners across the company. Your projects will often span offices, time zones, and hemispheres. It's your job to coordinate the players and keep them up to date on progress and deadlines. The Community Development and Engagement team drives business value by: accelerating new technical infrastructure delivery and growth; protecting Google’s license to operate in markets around the world; and leveraging community partnerships and innovative expertise to deliver solutions for community development and engagement. You will support strategic community development goals by providing data-driven insights and programmatic engagement that are based on community assessments for existing and prospective data center markets. You will partner with cross-functional teams to drive measurable social impact, develop and maintain relationships with key opinion formers/stakeholders and government officials and engage with a portfolio of community leaders, associations, and nonprofit organizations. You will be responsible for further entrenching community development best practices within an organization experiencing rapid growth, serving as a subject matter expert on data center delivery and strategic community engagement and development. 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 team 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." That's a lot. We'll keep as prose under About the role. Now Responsibilities: after "Responsibilities Learn more about benefits at Google ." we have bullet points (actually sentences separated by periods? Let's see): "Engage with key opinion formers, community groups such as municipal leaders, industry partners, economic development organizations, schools, education institutions, and non-profits to ensure initiatives are centered around community needs and accelerating business objectives.Develop strategies to scale sub regional Community Affairs coverage in emerging markets, focusing on place-based frameworks and partnerships to produce location-specific development plans based on research data turned into actionable insights to prioritize community needs.Develop communication tools and processes to educate local communities about the role and impact of our data centers, and create locally focused investment plans that are self-sustaining. Localize and implement community development initiatives in each community.Build and maintain relationships with internal stakeholders, including Acquisition & Development, Energy, Government Affairs and Public Policy, Cloud Supply Chain and Operations, Marketing, and local Google data center teams." These appear as run-on sentences without bullet markers. We need to treat each as a list item. We'll split by sentences that start with a verb. Let's identify: 1. Engage with key opinion formers, community groups such as municipal leaders, industry partners, economic development organizations, schools, education institutions, and non-profits to ensure initiatives are centered around community needs and accelerating business objectives. 2. Develop strategies to scale sub regional Community Affairs coverage in emerging markets, focusing on place-based frameworks and partnerships to produce location-specific development plans based on research data turned into actionable insights to prioritize community needs. 3. Develop communication tools and processes to educate local communities about the role and impact of our data centers, and create locally focused investment plans that are self-sustaining. 4. Localize and implement community development initiatives in each community. 5. Build and maintain relationships with internal stakeholders, including Acquisition & Development, Energy, Government Affairs and Public Policy, Cloud Supply Chain and Operations, Marketing, and local Google data center teams. We'll put each as

• . Now Minimum qualifications: "Minimum qualifications: Bachelor's degree or equivalent practical experience.5 years of experience in program or project management. 5 years of experience in one or more of the following fields: Data Centers, Utilities, Government, Advanced Manufacturing or capital intensive industries.5 years of experience developing and launching local, state, national or global public-private partnerships." We need to split into list items. Note there is missing space after periods but we can parse. Items: - Bachelor's degree or equivalent practical experience. - 5 years of experience in program or project management. - 5 years of experience in one or more of the following fields: Data Centers, Utilities, Government, Advanced Manufacturing or capital intensive industries. - 5 years of experience developing and launching local, state, national or global public-private partnerships. Now Preferred qualifications: "Preferred qualifications: MBA or Master’s degree in Education, Public Relations/Policy or a related field, or equivalent experience.5 years of experience managing cross-functional or cross-team projects." Items: - MBA or Master’s degree in Education, Public Relations/Policy or a related field, or equivalent experience. - 5 years of experience managing cross-functional or cross-team projects. Now Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $159000 - $230000 (USD) + 15% bonus target + equity + benefits" We'll keep as paragraph. Now Schedule/Hybrid: "This role is not remote, but supports a site that is not yet announced. Candidates must be able to adhere to our hybrid work location policy. Remote location: Ohio, USA." We'll put as paragraph under Schedule. Now we need to ensure we don't include any boilerplate like EEO, accommodation, etc. Also remove duplicated lines: there is "Learn more about benefits at Google ." we removed. Now we need to output HTML fragment with headings

  and appropriate content. We should not include or . Just the fragment. We need to decide order of sections. Typically: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Pay, Schedule. Possibly also Benefits? We'll skip Benefits. We need to use

  • for any list of duties/requirements/benefits. For Requirements and Qualifications we have lists. For Responsibilities we have list. For About the role we use

    . For Pay we use

    . For Schedule we use

    . Now check if any content is placeholder like "not specified". No. Now ensure we preserve all substantive information. Did we miss any? Let's re-read original for any other details. Original text: "This role is not remote, but supports a site that is not yet announced. Candidates must be able to adhere to our hybrid work location policy. Remote location: Ohio, USA.Min