Data Center Engineering Operations Technician

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to include Pay and Schedule sections only if posting actually states them. The posting includes Work Schedule details and Overtime & Pay details. So we should have a Pay section (including base salary range, overtime, night shift differential, max hours). Also a Schedule section (shift options). Benefits: posting mentions comprehensive benefits list (health insurance, 401(k) matching, paid time off, parental leave). So we can include Benefits section. Qualifications: Basic Qualifications and Preferred Qualifications. Could combine into Requirements? The instruction says use headings like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have responsibilities (Key job responsibilities). We have qualifications (Basic Qualifications, Preferred Qualifications). We have skills? Not explicit separate list; maybe we can embed skills within qualifications. We have About the role? The description starts with a paragraph about role; could be About the role. We have About The Team, Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those could be considered part of About the role or maybe separate sections like About the team, Culture, etc. But we only allowed headings from list; we could put those under About the role (maybe combine). However we must not create sections with filler. We need to include substantive content. Let's extract: - Intro paragraph: "How would you like to be a part of Earth’s most customer-centric company? ..." That's about the role and company. Could be About the role. - Key job responsibilities: list bullet points. - Work Schedule: details. - Overtime & Pay: details. - Physical Requirements: list. - A day in the life: more description of role. - About The Team: description. - Why AWS?: description. - Diverse Experiences: description. - Inclusive Team Culture: description. - Mentorship & Career Growth: description. - Work/Life Balance: description. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: mention comprehensive benefits. - EEO etc to remove. We need to output only HTML fragment, using

for headings,

• for lists,

  for prose. We must not include Job ID etc. We can maybe include location info? The posting includes location salary ranges for various VA locations. That's part of Pay? Could include location-specific salary ranges. The base salary range is listed for multiple locations. We could include that in Pay section. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the location salary ranges exactly as given? They are repeated for each location: "USA, VA, Ashburn - 37.64 - 65.91 USD hourly" etc. That's a lot of repetition. We could keep them as a list. It's substantive. We should not drop them. We need to remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://..." maybe we can keep mention of benefits but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to learn more; could be considered application instruction? Safer to remove the link but keep the description of benefits. Also remove "Company - Amazon Data Services, Inc." maybe not needed but it's substantive? It's metadata about company; could be considered minor metadata; we could drop or keep as short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p for Company and Job ID? But they said drop minor metadata. Safer to drop them. Thus final HTML:

  About the role

  How would you like to be a part of Earth’s most customer-centric company? You would work with teams of front-line responders who support the operations of some of the world’s most powerful data centers. Our Data Center Engineering Operations team maintain and operate our critical infrastructure systems so that they are prepared to stand up against any situation. AWS has the world’s largest cloud computing portfolio. As an Amazonian you will work in some of the most sophisticated, safe, and secure data centers in the world. Our Engineering Operations Technicians (EOT’s) help keep them that way by working with the brightest minds from around the globe to help test and implement the newest technology and work practices to meet the demands of a changing market. We have a passion for learning and evolving, it’s how we have helped define ourselves as leaders in the industry. Let’s work hard, have fun, and make history!

  Maybe also include "A day in the life" as part of About the role? Could be separate but we only have allowed headings; we could incorporate into About the role paragraph. But we have a lot of other sections: About The Team, Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These could be considered part of About the role or maybe we could create additional sections like About the team, Culture, etc. But the instruction only gave examples; not strict that we must only use those headings. It says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings, but not limited to them? It says "e.g." So we could also use other headings if needed, but better to stick to those. We could combine all those descriptive paragraphs under About the role. Thus About the role will include intro, A day in the life, About The Team, Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Then Responsibilities section with list. Then Requirements/Qualifications: we could have Requirements (maybe Basic Qualifications) and Qualifications (Preferred Qualifications) or combine. But we have both Basic and Preferred. Could make Requirements for Basic Qualifications and Qualifications for Preferred Qualifications. Skills: maybe not separate; we could omit. Benefits: list. Pay: include salary ranges, overtime, night shift differential, max hours. Schedule: include shift options. We need to ensure we don't create sections with filler. All have content. Now craft HTML. We need to use

  • for any list of duties/requirements/benefits. For prose use

    . Let's extract responsibilities list: - Daily building rounds to monitor and record information from electrical, mechanical, and fire/life safety equipment to ensure 24/7 reliability and availability - Monitor Building Management Systems (BMS) and Electrical Power Management System (EPMS) - Assist in troubleshooting of facility and rack-level events within internal Service Level Agreements (SLA) - Perform rack installs and rack decommissioning within internal SLA - Perform PM, troubleshooting, root cause analysis, and repair of electrical and mechanical equipment - Technical writing to support change management program - Monitor daily work requests and manage to resolution, and execute projects from conception to completion - On-site support of contractors, sub-contractors and vendors, ensuring that all work performed is in accordance with established practices, procedures & local legislation That's it. Physical Requirements list (maybe under Requirements? Could be part of Requirements). We'll include under Requirements (Basic Qualifications) maybe separate? But we have Basic Qualifications list: - Work shifts longer than eight hours in duration - 2+ years of practical experience in electrical systems, mechanical systems, HVAC, and/or fire suppression systems - Can bend or twist the body into unusual positions while working, use hands to manipulate small wires and objects, walk on job sites in uneven terrain, and work at heights and from ladders Physical Requirements list is separate but could be part of Requirements as well. We'll include them under Requirements (maybe as a sublist). But we need to follow instruction: use

    • for any list of duties/requirements/benefits. So we can have multiple lists. We'll create:

      Responsibilities

      • ...
      ...

      Requirements

      Basic Qualifications:

      • Work shifts longer than eight hours in duration
      • 2+ years of practical experience in electrical systems, mechanical systems, HVAC, and/or fire suppression systems
      • Can bend or twist the body into unusual positions while working, use hands to manipulate small wires and objects, walk on job sites in uneven terrain, and work at heights and from ladders

      Physical Requirements:

      • Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations:
      ... but we need to break down each bullet. The physical requirements paragraph includes a lead sentence then a list of actions. We could keep as a single
      • containing the sentence and then a nested list? But instruction: use
        • for any list. Could treat each item as a
        • . Let's extract each item: - Regularly lift and/or move up to 39 pounds independently - Participate in group lifts for 40+ pounds - Maintain balance and perform construction tasks while on a ladder - Regularly walk, use hands and fingers, handle or feel, reach with hands and arms, stoop, kneel, crouch or crawl, climb stairs, twist, bend, work above shoulders, grasp, carry, push and pull objects into position - Work in an environment requiring provided ear protection We'll include those as
        • under Physical Requirements. Now Preferred Qualifications: - Knowledge of network design and layout as well as low voltage (copper/ fiber) cabling - Experience in data center engineering We'll put under

          Qualifications

          (Preferred). Now Benefits: The posting says: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." We'll put that as a
          • maybe each benefit as separate items? Could be one
          • with the whole sentence. But better to split: health insurance (with subitems), 401(k) matching, paid time off, parental leave. However we must not invent detail; we can keep as one
          • with the full sentence. That's fine. Pay: includes base salary range for multiple locations, overtime, night shift differential, maximum hours. We'll create a
            • for each location salary range, then separate items for overtime, night shift differential, max hours. Schedule: includes two shift options with details. We'll create a
              • for each option. Now About the role: we need to include all descriptive paragraphs: intro, A day in the life, About The Team, Why AWS?, Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. We'll combine into a few

                elements. Let's extract each: Intro paragraph: "How would you like to be a part of Earth