Business Strategy and Operations Program Manager, Data Center Operations

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate: EEO, legal, accommodation, etc. Also remove duplicated lines, navigation, cookie, etc. Preserve all substantive info. We need to parse the posting. First part: "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. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Atlanta, GA, USA; Council Bluffs, IA, USA; Midlothian, TX, USA; The Dalles, OR, USA; Leesburg, VA, USA; Lenoir, NC, USA; Sparks, NV, USA; San Francisco, CA, USA." That's location info. Could be part of "About the role"? Not exactly. Might be considered as "Location" but we don't have a heading for location. Could embed in a paragraph under "About the role" or maybe not needed. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So location info is minor metadata; we can put in a short

. Then "Minimum qualifications: ..." list of qualifications. Then "Preferred qualifications: ..." Then "About The Job" paragraph. Then "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $188000 - $274000 (USD) + 20% bonus target + equity + benefits". That's pay and benefits info. Then "Responsibilities" list. Then after responsibilities there is "Learn more about benefits at Google ." That's a link but we can ignore? It's part of responsibilities? Actually it's after responsibilities heading? The snippet: "Responsibilities Learn more about benefits at Google . Act as a team multiplier..." So "Learn more about benefits at Google." is likely a link but we can drop as it's navigation/boilerplate? Might be considered a link to benefits page; but we have benefits info already. Could drop. Then after responsibilities list there is EEO boilerplate etc. Remove. Thus sections we have: - About the role (maybe "About The Job"): we have a paragraph describing the job. Could be under

About the role

with that paragraph. - Responsibilities: list of bullet points. - Requirements / Qualifications: we have minimum qualifications and preferred qualifications. Could combine into Requirements section? The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have both minimum and preferred qualifications. Could put under

Qualifications

with two sub-sections? But we cannot create subheadings besides h3? We could just list them as paragraphs. Probably better to have

Qualifications

containing both minimum and preferred as paragraphs or lists. - Pay: we have salary range and bonus etc. So

Pay

with paragraph. - Benefits: we have mention of equity + benefits, but not detailed. The posting says "+ equity + benefits". That's not specific benefits detail. According to rule: never create Benefits section unless posting actually states them. It does state "+ equity + benefits" but that's vague. Might be considered stating benefits exist but not details. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (equity + benefits). So we could include Benefits section with that statement. However we also have Pay section. Could combine? Better separate. - Schedule: not mentioned, so omit. - Skills: not explicitly listed; we could infer from qualifications but better not create unless explicit. Thus sections: About the role, Qualifications, Pay, Benefits, Responsibilities. But order? Not required but typical: About the role, Responsibilities, Qualifications, Pay, Benefits. We'll follow that. Now need to preserve all substantive information. Let's extract. Location note: "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. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Atlanta, GA, USA; Council Bluffs, IA, USA; Midlothian, TX, USA; The Dalles, OR, USA; Leesburg, VA, USA; Lenoir, NC, USA; Sparks, NV, USA; San Francisco, CA, USA." We can put that as a paragraph under About the role maybe before job description. Or separate short p. Now About The Job paragraph: "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 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. As a Business Strategy and Operations Program Manager, you will be a pivotal member of our enablement team, dedicated to removing friction and minimizing administrative burden for our Data Center Operations (DCOps) field teams. Your mission is to provide the operational clarity and process support necessary for our field teams to maintain focus on delivering operational excellence. Your responsibilities will include streamlining the OKR process, simplifying the Rhythm of Business (RoB), and executing a two-way communication strategy that ensures field challenges are heard and addressed by leadership. You will require a service-oriented mindset, focused on empowering our technical teams to work effectively by reducing the complexity and confusion that often accompany large-scale operations. Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's product portfolio possible. We're proud to be our engineers' engineers and love voiding warranties by taking things apart so we can rebuild them. We keep our networks up and running, ensuring our users have the best and fastest experience possible." That's the About The Job. Now Responsibilities bullet points: - Act as a team multiplier for our field teams by proactively identifying and eliminating operational bottlenecks and administrative friction that impede their daily work. - Own the end-to-end OKR process for the organization, leading the setup, tracking, and alignment of OKRs while ensuring that objectives are clear, relevant to field needs, and designed to minimize reporting overhead. - Organize and facilitate the regular meetings that keep the organization aligned, ensuring discussions are productive, and that critical blockers are identified and cleared. - Build trusted partnerships across cross-functional groups to drive operational improvements and ensure that initiatives are designed with business needs in mind. - Look for ways to simplify how we work. Also there is "Learn more about benefits at Google ." which we can drop. Now Minimum qualifications list: - Bachelor's degree or equivalent practical experience. - 8 years of experience in program or project management. - 8 years of experience in business strategy, operations, or program management, with a focus on designing and driving organizational processes. - 8 years of experience managing organizational rhythms (e.g., monthly/quarterly business reviews, OKR tracking, leadership summits) or executing internal communication strategies for operations. - 8 years of experience managing cross-functional programs. Preferred qualifications: - 5 years of experience in business operations or operational program management in a data center environment. - 5 years of experience establishing business-centric metrics, KPIs, and evaluation frameworks for complex organizations. - Experience with designing and implementing process improvements or change management initiatives that resulted in measurable organizational efficiency gains. - Demonstrated ability to influence cross-functional partners and leadership across a global team to drive operational improvements, particularly in ambiguous environments where engaged priorities exist. - Strong executive leadership presentation skills with the ability to communicate effectively to executive stakeholders. Now Pay/Benefits: - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. - US: $188000 - $274000 (USD) + 20% bonus target + equity + benefits Thus Pay section: paragraph with that info. Benefits section: maybe just mention equity + benefits? But we already included benefits in Pay line. Could still have Benefits section with "Equity and benefits package" but that's redundant. The rule: prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But we have headings Pay and Benefits separate. Could we omit Benefits section because the info is already in Pay line? The line includes "+ equity + benefits". That is mention of benefits. Could we just keep Pay section and not create Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, but we could incorporate that into Pay section. However we need to decide. I'd create Pay section with the compensation details, and maybe not create a separate Benefits section because the benefit detail is minimal and could be considered part of Pay. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Benefits section. Thus sections: About the role, Responsibilities, Qualifications, Pay. Now we need to format. Use

for section headings. Inside each section, use

for prose,

• for lists. We need to ensure we don't repeat job title. Now produce HTML fragment. Let's craft:

  About the role

  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. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Atlanta, GA, USA; Council Bluffs, IA, USA; Midlothian, TX, USA; The Dalles, OR, USA; Leesburg, VA, USA; Lenoir, NC, USA; Sparks, NV, USA; San Francisco, CA, USA.

  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 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. As a Business Strategy and Operations Program Manager, you will be a pivotal member of our enablement team, dedicated to removing friction and minimizing administrative burden for our Data Center Operations (DCOps) field teams. Your mission is to provide the operational clarity and process support necessary for our field teams to maintain focus on delivering operational excellence. Your responsibilities will include streamlining the OKR process, simplifying the Rhythm of Business (RoB), and executing a two-way communication strategy that ensures field challenges are heard and addressed by leadership. You will require a service-oriented mindset, focused on empowering our technical teams to work effectively by reducing the complexity and confusion that often accompany large-scale operations. Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's