Data Center Technician, Global Server Operations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: immigration sponsorship line, EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie/legal. Also remove "Learn more about benefits at Google ." maybe keep? It's a link but it's boilerplate; we can drop. Also remove "Google is proud to be an equal opportunity workplace..." etc. Also remove "If you have a disability..." etc. We need to preserve all substantive information: minimum qualifications, preferred qualifications, about the job description, responsibilities list, pay info, maybe schedule? The posting mentions "Must be available to work non-standard hours, including working weekends, night shifts, holidays and on shift-based schedules as required." That's schedule info. Also "Must be available to travel to support business priorities as operationally required." That's maybe part of requirements. Benefits: The posting mentions "US: $86000 - $118000 (USD) + 15% bonus target + equity + benefits". So we have pay and benefits mention. Benefits not detailed beyond "benefits". We can include a Benefits section with generic statement? But rule: only include section when posting has real, specific content for it. It says "+ benefits" but not specific. Might be considered not specific enough? It says "benefits" generic. Might be considered placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "+ benefits" is vague but still indicates benefits exist. Might be okay to include Benefits section with a short

  stating "Benefits include equity, bonus target, and other standard Google benefits." But that's adding detail not in posting. Better to just include a Benefits section with the phrase from posting: "+ benefits". But that is not a list; we could put

  Benefits: as indicated in the compensation package.

  . However that may be considered adding? It's directly from posting: they said "+ benefits". We can include that. Pay: we have salary range and bonus target and equity. So Pay section. Schedule: we have non-standard hours, weekends, night shifts, holidays, shift-based schedules. Also travel requirement. So Schedule section. Now structure: We need sections: About the role (maybe "About the job" heading). Use

  About the role

  then

  with the prose about Google Hardware Operations team, AI and Infrastructure team, etc. Responsibilities: list bullet points from responsibilities. Requirements/Qualifications: we have minimum qualifications and preferred qualifications. Could combine into Requirements section with two sublists? But we need to follow rule: Use

  • for any list of duties/requirements/benefits. So we can have a
    for minimum qualifications and another for preferred qualifications, maybe under same heading? Could separate into Minimum Qualifications and Preferred Qualifications headings, but those are not in the allowed headings list (they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Requirements or Qualifications. Probably better to have a single Requirements section with both minimum and preferred qualifications as lists, maybe with headings inside? But we cannot add extra headings beyond allowed? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

    for section headings (e.g. those). Likely we should stick to those headings. So we can have a Requirements section that includes both minimum and preferred qualifications, maybe with

    introducing. Skills: maybe we can extract skills from qualifications: ability to lift, troubleshoot, etc. Could create Skills section. But we should prefer few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Pay, Schedule, Benefits. That's six sections. We need to ensure we don't include empty sections. Let's extract content: About the job prose: "Google isn't just a software company. The Hardware Operations team is responsible for monitoring the state-of-the-art physical infrastructure behind Google's powerful search technology. As an Operations Technician, you'll install, configure, test, troubleshoot and maintain hardware (like servers and its components) and server software (like Google's Linux cluster). You'll also take on the configuration of more complex components such as networks, routers, hubs, bridges, switches and networking protocols. You'll participate in or lead small project teams on larger installations and develop project contingency plans. A typical day involves manual movement and installation of racks, and while it can sometimes be physically demanding, you are excited to work with infrastructure that is at the cutting-edge of computer technology. 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." That's the about section. Responsibilities list: - Deploy and operate new data center infrastructure across projects or functions. - Report issues and follow data center procedures to troubleshoot and diagnose straightforward issues with equipment or infrastructure as they arise, and applying the resources needed to resolve identified issues. - Maintain the security and integrity of data, track various forms of media to check for standard data security issues (e.g., data was not properly erased) handled in accordance with Google security standards. - Disassemble specific equipment that has reached its end-of-life via part replacement or maintenance, in a team setting. - Repair, fix, and perform preventative maintenance on equipment, servers, machines, or infrastructure based on identified issues with defined solutions and limited guidance. We could also include "Learn more about benefits at Google ." but that's boilerplate; drop. Minimum qualifications: - Experience with performing component-level repairs and troubleshooting on technical equipment. - Experience diagnosing and troubleshooting one of the following: operating systems, computer/server hardware, or networking protocols. - Ability to lift/move 50lb (23kg) of equipment and ability to exert yourself physically over extended periods of time, including frequent bending, kneeling, climbing, pushing/pulling and lifting. - Must have the ability to work non-standard hours, including working weekends, night shifts, holidays and on shift-based schedules as required. - Must be available to travel to support business priorities as operationally required. Preferred qualifications: - Bachelor's degree or equivalent practical experience. - Completion of the online Google IT Support Professional Certificate program. - 2 years of experience diagnosing and troubleshooting one of the following: operating systems and computer/server hardware or networking protocols. - Experience with performing component-level repairs and troubleshooting on IT equipment or in a similar role (e.g. Systems Administration, Network Deployment Engineer, Help Desk Technician, etc). - Experience working within a data center or network operation center environment. - Ability to collaborate and partner with teams to overcome challenges, and to adapt to changes in a dynamic work environment. Pay: - US: $86000 - $118000 (USD) + 15% bonus target + equity + benefits We could phrase as

    The base salary range is $86,000 – $118,000 USD, with a 15% bonus target, equity, and benefits.

    Schedule: - Must have the ability to work non-standard hours, including working weekends, night shifts, holidays and on shift-based schedules as required. - Must be available to travel to support business priorities as operationally required. We could combine travel under schedule or requirements; but schedule section can include non-standard hours and travel. Benefits: - Benefits are included as part of compensation package (as indicated). Could just say

    Benefits are included as part of the compensation package.

    but that's adding. Maybe we can just put

    Benefits: as indicated in the compensation package.

    but that's not a list. Better to have Benefits section with a

    stating "Benefits are included as part of the compensation package (equity, bonus target, etc.)". However that repeats pay info. Might be okay. But we could also omit Benefits section if we consider it not specific enough. The rule: never create Benefits section unless posting actually states them. It does state "+ benefits". That's a mention. So we can include Benefits section with a short

    indicating that benefits are part of the compensation package. Now produce HTML:

    About the role

    ... (the about paragraph)

    Responsibilities

    • ...
    ...

    Requirements

    Minimum qualifications:

    • ...
    ...

    Preferred qualifications:

    • ...
    ...
    But we used inside

    . That's allowed? Not prohibited. Could also just have headings inside? But we shouldn't add extra headings. Using

    with bold is okay. Alternatively we could have two separate

    with preceding

    explaining. Pay section:

    Pay

    The base salary range is $86,000 – $118,000 USD, with a 15% bonus target, equity, and benefits.

    Schedule section:

    Schedule

    • Ability to work non-standard hours, including weekends, night shifts, holidays, and shift-based schedules as required.
    • Must be available to travel to support business priorities as operationally required.
    Benefits section:

    Benefits

    Benefits are included as part of the compensation package.

    Check for any duplicated lines: we have "Ability to work non-standard hours..." appears both in minimum qualifications and schedule. We should avoid duplication? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication may be okay if it's in original. But we could keep it only once. However the schedule section is derived from that qualification; we could keep it in Requirements under minimum qualifications and not repeat in Schedule. But schedule also includes travel requirement. The travel requirement is also in minimum qualifications. So we could move travel to schedule as well. To avoid duplication, we could keep minimum qualifications as is, and schedule only include the non-standard hours and travel (which are already in minimum qualifications). That would duplicate. Perhaps better to keep schedule separate and not duplicate the qualifications; we could remove those lines from minimum qualifications and keep them only under schedule. But then we would lose the minimum qualification detail about ability to lift etc. The lifting requirement is not schedule. So we need to keep lifting etc under minimum qualifications. The non-standard hours and travel could be placed under schedule only, and we could remove them from minimum qualifications to avoid duplication. However the original posting lists them under minimum qualifications. Removing them would be omitting substantive information. The rule says preserve ALL substantive information. So we must keep them somewhere. Duplication is not prohibited; it's just repeating. It's okay to have them in both sections as long as