Data Center Controls Tech, Deployment

We need to produce HTML fragment with sections: About the role? Actually the posting includes description, responsibilities, etc. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key parts: - Description (intro) about role: "As a member of the Global Controls Team, you will collaborate..." This is prose. - Key job responsibilities: list of bullet points. - A day in the life: prose. - About The Team: prose (some duplication). We need to include maybe "About the team" as a section? The allowed headings include "About the role". Not "About the team". But we could use "About the role" for description. The team description could be part of "About the role" or maybe we create a separate section "About the team"? Not in allowed list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should likely stick to those headings. It says "include a section ONLY when the posting has real, specific content for it". So we can use those headings if content matches. For "About the role" we have description. For "Responsibilities" we have key job responsibilities list. For "Requirements" we have basic qualifications. For "Qualifications" we have preferred qualifications. For "Skills" maybe we can extract skills from qualifications? Could combine. But we could also not include Skills if not explicit. However we have "Basic understanding of Industrial controls system, knowledge of meters, devices, sensors, relays and troubleshooting utilizing standard hand tools, digital metering, or calibration/diagnostic equipment..." That's skills. Could put under Skills. But we already have Requirements and Qualifications sections. Might be okay to have both Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they are distinct: Basic Qualifications and Preferred Qualifications. Could have "Requirements" for basic qualifications, and "Qualifications" for preferred. That seems fine. Skills: maybe not needed separately if covered. Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have benefits content. Pay: The posting includes "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." Then later: "USA, VA, Louisa - 32.93 - 57.64 USD hourly". So we have pay range. So we should include Pay section with that info. Schedule: Not mentioned explicitly. There's "Ability to work non-standard hours and differing work rotations/shifts and overtime as required." That's about schedule but not explicit schedule details. Could we create Schedule section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state ability to work non-standard hours, but not a specific schedule. Might be considered schedule info. However it's vague. Might be better to omit Schedule section because not explicit schedule like "Monday-Friday, 8am-5pm". So we omit Schedule. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove repeated "About The Team" duplication (the paragraph appears twice). We'll keep one copy. We need to preserve all substantive info. Let's extract: Description (About the role): "As a member of the Global Controls Team, you will collaborate with highly motivated operators, engineers and technicians in the data center industry to maintain and optimize critical infrastructure systems. You will be responsible for troubleshooting and maintaining the Building Management System (BMS) and Electrical Power Monitoring System (EPMS) while developing new processes and standards that drive innovation in the controls space. AWS data centers utilize sophisticated industrial control systems to automatically operate mechanical equipment, maintaining optimal temperature and pressure conditions throughout the facilities. These systems integrate and monitor multiple critical components, including generators, uninterruptible power sources, diesel generators, electrical switchgear, power distribution units, variable frequency drives, automatic and static transfer switches, air-cooled and water-cooled chillers, pumps, cooling towers, heat exchangers, Computer Room Air Handlers (CRAHs), and air economizers. Within this industrial control system infrastructure, the BMS serves as the primary control platform for all mechanical systems within the data center, while the EPMS functions as the primary monitoring platform for all electrical systems. This position offers the opportunity to work with technology in mission-critical environments while contributing to the reliability and efficiency of AWS's global infrastructure." Responsibilities (Key job responsibilities): List bullet points: - Primarily work in and support multiple data centers by deploying, servicing, and upgrading BMS and EPMS systems. - Mentor and train Facilities team members on the operation and control of BMS and EPMS systems. - Manage small to medium-sized projects and programs. - Perform point-to-point checkouts between field devices and controllers. - Perform first-line diagnostics, troubleshooting, and maintenance of programming code and hardware associated with BMS and EPMS in data centers. - Execute provisioning processes for servers, controllers, industrial PCs, and network configurations, including communication testing between third-party devices and controllers or servers. - Install, replace, configure, and calibrate sensors. - Read and interpret electrical schematics and control panel drawings with a basic understanding of closed-loop controls, field sensor scaling, and functions typically performed by industrial controllers. - Supervise low-voltage electrical contractors performing wiring and installation of field devices in compliance with AWS requirements. - Provide commissioning and systems-level testing support. - Create red-lined drawings and documentation of systems. - Follow change management processes to generate work requests and methods of procedures. - Participate in factory witness tests at vendor or panel builder facilities. - Perform root cause analysis during testing and commissioning. - Ensure personnel on site utilize proper safety methodology. - Perform service activities including monitoring and reviewing ticketing systems, conducting root cause analysis, and prioritizing tasks. - Actively manage service agreements including vendor labor scheduling, quality assurance, and financial invoice review. - Participate in material handling tasks such as lifting, carrying, or moving up to 50 lbs of equipment, and utilize OSHA-standard safety equipment including limited weight-bearing work platforms, ladders, step stools, and personal protective equipment (PPE) such as safety harnesses. - Perform other tasks as assigned by manager. A day in the life (could be part of responsibilities or separate section? Could be included under "About the role" or maybe a separate "Day in the life" but not in allowed headings. Could incorporate into description. But we have to preserve all substantive info. We could add a paragraph under About the role after the description. Or we could create a separate section "About the role" that includes both description and day in the life. That's fine. About The Team: we have paragraph about AWS Infrastructure Services. We'll include maybe as part of About the role or separate? Could be "About the team" but not allowed. Could incorporate into About the role as well. But we have to avoid duplication. We'll include a paragraph after description. Why AWS etc: includes sections like Diverse Experiences, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are boilerplate? They are part of the posting but maybe considered generic AWS culture. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not legal boilerplate but are generic AWS culture. Might be considered part of the posting but not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them if they are substantive. However they are generic but still part of posting. The allowed headings don't include a section for culture, but we could put them under "About the role" or maybe a separate section "About AWS"? Not in list. Could we create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. But to be safe, we could stick to those headings and put culture info under "About the role" or maybe under "Benefits"? Not appropriate. Could create a section "About AWS" but not in list; risk of being considered not following instruction. Safer to incorporate into "About the role" as a paragraph. Basic Qualifications: list. Preferred Qualifications: list. Benefits: list. Pay: hourly range and note about sign-on payments and RSUs. Now we need to output HTML fragment only, no markdown. We'll structure:

About the role

... (description + day in the life + team + culture maybe)

Responsibilities

• ...
...

Requirements

... basic qualifications ...

Qualifications

... preferred qualifications ...

Benefits

... benefits ...

Pay

... pay range ...

We should not include Schedule. Now we need to ensure we don't repeat any info unnecessarily. We'll combine description, day in the life, team, culture into one paragraph? Might be long but okay. Let's craft the About the role paragraph: Start with description: "As a member of the Global Controls Team, you will collaborate with highly motivated operators, engineers and technicians in the data center industry to maintain and optimize critical infrastructure systems. You will be responsible for troubleshooting and maintaining the Building Management System (BMS) and Electrical Power Monitoring System (EPMS) while developing new processes and standards that drive innovation in the controls space. AWS data centers utilize sophisticated industrial control systems to automatically operate mechanical equipment, maintaining optimal temperature and pressure conditions throughout the facilities. These systems integrate and monitor multiple critical components, including generators, uninterruptible power sources, diesel generators, electrical switchgear, power distribution units, variable frequency drives, automatic and static transfer switches, air-cooled and water-cooled chillers, pumps, cooling towers, heat exchangers, Computer Room Air Handlers (CRAHs), and air economizers. Within this industrial control system infrastructure, the BMS serves as the primary control platform for all mechanical systems within the data center, while the EPMS functions as the primary monitoring platform for all electrical systems. This position offers the opportunity to work with technology in mission-critical environments while contributing to the reliability and efficiency of AWS's global infrastructure." Add day in the life: "As a Data Center Controls Technician, your primary customers are Data Center Engineering Operations (DCEO), who rely on you to keep Building Management Systems (BMS) and Electrical Power Monitoring Systems (EPMS) healthy and operational. On a given day, you are the boots on the ground solving problems that directly impact data center availability. You might diagnose a controller communication loss, calibrate instruments feeding inaccurate data to operators, or supervise vendors performing quarterly maintenance. For new builds, you perform point to point testing and support commissioning alongside construction teams. Your internal stakeholders include your Controls Engineer, Controls Manager, partner teams (Field Engineering, Critical Project Implementation, DCEO), and the vendors you oversee." Add About The Team: "AWS Infrastructure Services owns the design, planning, delivery