Jobs · Engineering · Georgia

AI Infrastructure Customer Office Lead

Google · Atlanta, GA · 3 wk ago
On-siteEngineeringFull-time
We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Also remove navigation/cookie etc. Must preserve all substantive info. We need to parse the posting. Content: - Application window open until at least November 9, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Chicago, IL, USA; Boulder, CO, USA; Austin, TX, USA; Atlanta, GA, USA. - Minimum qualifications: Bachelor's degree or equivalent practical experience. 10 years of experience in program management, project management, business operations, or partner management within an enterprise technology environment. Experience working with leadership and cross-functional teams to deliver executive-level communications and briefing materials. - Preferred qualifications: Experience working within cloud infrastructure, enterprise software, or complex B2B strategic partnership models. Exceptional written and verbal communication skills with the ability to synthesize technical and business topics into clear executive summaries. Strong organizational skills and a demonstrated track record of rapid execution under tight timelines. Proven ability to build effective cross-functional networks and drive alignment without direct authority. - About The Job: paragraph describing Google Cloud, role as Customer Office Lead, supporting AI Infrastructure leadership team, etc. - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits - Responsibilities: list bullet points (starting with "Learn more about benefits at Google ." Actually that line seems like a stray; but we need to preserve responsibilities bullet points. The bullet points after "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google . Coordinate the creation, review, and distribution of executive briefing documents, status reports, and presentation decks for leadership meetings and customer engagements.Collaborate closely with Product, Engineering, Sales, Legal, and Strategic Pursuits teams to assess operational readiness, track deliverables, and maintain alignment across stakeholders.Manage day-to-day coordination, logistics, meeting notes, and follow-up communications for C-level customer meetings, roundtables, and executive visits.Define, build, and maintain lightweight operational processes for tracking agreement milestones, action items, and follow-ups across high-stakes customer pursuits and strategic initiatives.Identify opportunities to streamline communication channels, standard operating procedures, and reporting frameworks across the Customer Office, the AI Infra Specialist team and key cross functional stakeholders." So responsibilities bullet points: coordinate creation...; collaborate closely...; manage day-to-day...; define, build...; identify opportunities... - Benefits: Not explicitly listed besides "equity + benefits" in pay line. There's no separate benefits description. So we should not create a Benefits section unless posting actually states them. It only mentions "+ equity + benefits" but no detail. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range and bonus target etc. So we can include Pay section with that detail. Benefits: we have only mention of benefits generically; no specifics. Should we include Benefits section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "+ equity + benefits" but that's not specific benefits description. Likely we should not create a Benefits section because no specific benefits are listed. However we could include a short sentence? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not details. I'd interpret that as we should not create a Benefits section because no specific benefits are listed. So we omit Benefits. - Schedule: not mentioned. So omit. - Skills: Could be derived from preferred qualifications etc. But we need a section only if posting has real specific content for it. There's no explicit "Skills" heading, but we could treat "Preferred qualifications" as skills. However we have separate sections for Requirements, Qualifications, Skills. The posting includes Minimum qualifications and Preferred qualifications. We could map Minimum qualifications to Requirements (or Qualifications). Preferred qualifications could be Skills or Qualifications. We need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include About the role (the "About The Job" paragraph). Responsibilities (list). Requirements (minimum qualifications). Qualifications (maybe preferred qualifications). Skills (maybe the communication, organizational, etc). But we must not create sections with filler. We have content for each. Let's extract: About the role: The paragraph starting "About The Job Google Cloud accelerates organizations’ ability..." etc. We'll put that in

. Responsibilities: list items as

  • . Requirements: Minimum qualifications: Bachelor's degree or equivalent practical experience. 10 years of experience in program management, project management, business operations, or partner management within an enterprise technology environment. Experience working with leadership and cross-functional teams to deliver executive-level communications and briefing materials. We could format as
    • each. Qualifications: Preferred qualifications: Experience working within cloud infrastructure, enterprise software, or complex B2B strategic partnership models. Exceptional written and verbal communication skills with the ability to synthesize technical and business topics into clear executive summaries. Strong organizational skills and a demonstrated track record of rapid execution under tight timelines. Proven ability to build effective cross-functional networks and drive alignment without direct authority. We could also put these as
      • . Skills: Could be overlapping with qualifications; but we already used qualifications for preferred qualifications. Maybe we could treat Skills as the communication, organizational, etc. But we already have them in qualifications. To avoid duplication, maybe we put Skills as the communication, organizational, etc. But we need to avoid repeating content. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not duplicate content? It didn't forbid duplication but we should not invent. Duplication might be okay but better to avoid redundancy. However we need to decide which sections to include. Perhaps we can combine Minimum qualifications into Requirements, Preferred qualifications into Qualifications, and then we could omit Skills because its content is already covered. But the rule says include a section ONLY when the posting has real, specific content for it. If we omit Skills, that's fine because we are not creating a section with filler. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check Pay: we have specific pay range and bonus target etc. So include Pay. Now we need to format. We must not include any boilerplate like EEO, application instructions, etc. Also remove the line "Learn more about benefits at Google ." That's part of responsibilities? Actually it's a stray sentence before responsibilities list. It says "Learn more about benefits at Google ." That's not a responsibility; it's a link. We should remove it as it's likely boilerplate/application instruction. The responsibilities start after that. So we should omit that sentence. Thus responsibilities list items: - Coordinate the creation, review, and distribution of executive briefing documents, status reports, and presentation decks for leadership meetings and customer engagements. - Collaborate closely with Product, Engineering, Sales, Legal, and Strategic Pursuits teams to assess operational readiness, track deliverables, and maintain alignment across stakeholders. - Manage day-to-day coordination, logistics, meeting notes, and follow-up communications for C-level customer meetings, roundtables, and executive visits. - Define, build, and maintain lightweight operational processes for tracking agreement milestones, action items, and follow-ups across high-stakes customer pursuits and strategic initiatives. - Identify opportunities to streamline communication channels, standard operating procedures, and reporting frameworks across the Customer Office, the AI Infra Specialist team and key cross functional stakeholders. Now About the role paragraph: Let's extract exactly: "About The Job Google Cloud accelerates organizations’ ability to digitally transform their business with the best infrastructure, platform, industry solutions, and expertise. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology to help our customers solve their most critical business problems. In this role as Customer Office Lead, you will support the AI Infrastructure leadership team in driving program execution and operational expertise across top-priority accounts. You will serve as the primary operational coordinator managing engagement workflows, briefing preparation, cross-functional tracking, and status reporting required to execute non-standard customer partnerships and senior executive reviews. 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 force 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." We need to ensure we keep the content exactly, but we can format as

        . Ensure we preserve punctuation. Now Requirements (minimum qualifications): - Bachelor's degree or equivalent practical experience. - 10 years of experience in program management, project management, business operations, or partner management within an enterprise technology environment. - Experience working with leadership and cross-functional teams to deliver executive-level communications and briefing materials. Now Qualifications (preferred qualifications): - Experience working within cloud infrastructure, enterprise software, or complex B2B strategic partnership models. - Exceptional written and verbal communication skills with the ability to synthesize technical and business topics into clear executive summaries. - Strong organizational skills and a demonstrated track record of rapid execution under tight timelines. - Proven ability to build effective cross-functional networks and drive alignment without direct authority. Now Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits" We should keep as

        . Possibly we could split into two sentences but keep as is. Now we must not include any other sections like Benefits, Schedule. Now output HTML fragment only. We'll wrap sections in appropriate headings

        . For each section we need heading then content. Thus:

        About the role

        About The Job Google Cloud accelerates organizations’ ability to digitally transform their business with the best infrastructure, platform, industry solutions, and expertise. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology to help our customers solve their most critical business problems. In this role as Customer Office Lead, you will support the AI Infrastructure leadership team in driving program execution and operational expertise across top-priority accounts. You will serve as the primary operational coordinator managing engagement workflows, briefing preparation, cross-functional tracking, and status reporting required to execute non-standard customer partnerships and senior executive reviews. 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 force 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.

        Responsibilities

Similar jobs