Construction Manager , Data Center Construction

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Pay: we have salary ranges listed multiple locations. That is specific content: base salary range listed. So we should include Pay section with that info. Benefits: there is description of benefits (health insurance, 401k matching, PTO, parental leave). So include Benefits. Schedule: not mentioned; no schedule info. So omit Schedule. Skills: maybe we can extract from qualifications? There's a Skills section maybe combine with Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content. About the role: we have description at start: "AWS Infrastructure Services owns the design..." That's about the role? Could be About the role. Responsibilities: we have "Key job responsibilities" and bullet list. So include Responsibilities. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe we could extract from qualifications? But we already have Requirements and Qualifications; Skills could be separate but maybe not needed if no specific skills beyond those. Could combine skills into Qualifications? But instruction says prefer few substantive sections over many thin ones. We could merge Requirements and Qualifications into one "Requirements" section? But they ask to use those headings if content exists. We have both Basic and Preferred qualifications; we could put Basic under Requirements, Preferred under Qualifications. Skills maybe not needed. About the role: we have introductory paragraphs. Could also include "About The Team" which is similar. Might combine into About the role. We must not repeat job title. Must not include Job ID etc. Must not include accommodation link, EEO, etc. Must not include duplicated lines. We need to preserve all substantive information: that includes description of AWS Infrastructure Services, role description, responsibilities list, basic qualifications, preferred qualifications, benefits description, pay ranges (multiple locations). Also maybe mention "You'll join a diverse team..." etc. That's part of About the role. We need to format using

for headings,

• for lists,

  for prose. We must output only HTML fragment, no /, no markdown. Let's extract content. First, About the role: combine initial paragraph and maybe "About The Team" (which is similar). Let's capture: "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we're the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we're looking for talented people who want to help. You'll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You'll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you'll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion." That's substantive. Responsibilities: list from "Key job responsibilities" and bullet list. Let's capture each responsibility as list items. Responsibilities list: - construction project management and oversight of construction-related activities as they relate to new builds or general capital projects. This includes ownership of the project scope, quality, schedule, and budget. - Direct interface with construction general contractors during the bidding, award, execution, and project closeout/punch list phases. - Conduct negotiations with general contractors and evaluate bids/proposals with detail and accuracy. - Create construction project scope and requests for proposals. - Perform financial analysis of construction. - Manage construction projects for specific initiatives aimed at increasing the resiliency of our data centers. - Conduct constructability reviews of electrical and mechanical designs associated with the construction of new data centers or optimization of existing data centers. - Manage construction documents including submittal review, RFIs, change orders, and invoicing. - Ensure construction project quality control. - Record and report key construction metrics to team members and management. - Drive teams to perform troubleshooting and root-cause failure analysis associated with equipment failures. - Be a leader within the group as well as within internal and external teams that support the data center. Also "A day in the life" heading but no content? Actually after that there is "**Why AWS**" etc. That's more about company culture, maybe belongs to About the role or Benefits? But we already have About the role covering culture. The "Why AWS" section includes subpoints: Diverse Experiences, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are also substantive but could be part of About the role or maybe a separate section like "About AWS". However instruction only allows those headings; we could incorporate into About the role or maybe Benefits? But Benefits is separate for compensation/benefits. The "Why AWS" is more about culture; we could add to About the role as additional prose. We must preserve all substantive info, so we need to include that content somewhere. Could add a paragraph after About the role describing those points. Let's extract: "Why AWS" bullet points: - Diverse Experiences: Amazon values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying. - Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud. - Inclusive Team Culture: Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences, inspire us to never stop embracing our uniqueness. - Mentorship and Career Growth: We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional. Also "About The Team" repeats earlier content; we can ignore duplicate. Basic Qualifications: list: - Bachelor's degree in Electrical Engineering, Mechanical Engineering, or a related field - Experience carrying new design concepts through exploration, development, and into deployment or mass production - Experience in MS Excel, Word, and Windows Operating Systems - Experience with power management and power monitoring systems Preferred Qualifications: - 5+ years of project management in data centers or comparable critical infrastructure experience - Knowledge of critical data center equipment - Knowledge of engineering documentation, electrical diagrams and standard operating procedures - Knowledge of building codes and regulations including Life Safety, BOCA, NFPA, NEC, or OSHA - Experience in project management in data centers or comparable critical infrastructure (duplicate? but keep) - Experience in Data Center Engineering Operations, with a deep understanding of electrical and mechanical data center infrastructure - Experience reading and interpreting construction specifications and drawings for all domains We should deduplicate duplicates: "Experience in project management in data centers or comparable critical infrastructure experience" appears twice; we can keep one. Benefits: description: - 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. - Learn more about our benefits at https://amazon.jobs/en/benefits. (But we should remove application instructions? The link is maybe okay as it's informational; but instruction says remove application instructions. This is a benefits link, not application. Might keep? Safer to keep as it's part of benefits description. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not application instruction; it's a link to learn more about benefits. I'd keep it. Pay: 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 list multiple locations with same range: USA, OR, Boardman - 111,300.00 - 186,100.00 USD annually etc. Many duplicates for VA locations. We should preserve all substantive info; we could list unique locations with the range. Since all have same range, we could summarize: "The base salary range for this position is $111,300 - $186,100 USD annually (varies by location)." But that would be summarizing; we must not invent or summarize away detail. We need to preserve ALL substantive information; we could keep the list but it's repetitive. However we could keep the statement that the base salary range is listed below and then list the ranges; but that is repetitive. The instruction says preserve ALL substantive information; does not forbid removing duplicate lines? It says remove duplicated lines. So we can deduplicate identical lines. So we can keep one line for each unique location? But they are duplicated lines with different location names; they are not identical because location differs. So we need to keep each location line? They are not duplicated lines; they differ by location. So we should keep each location line. However there are duplicates like "USA, VA, Louisa - 111,300.00 - 186,100.00 USD annually" appears twice? Actually we see "USA, VA, LOUISA - 111,300.00 - 186,100.00 USD annually" and "USA, VA, Louisa - 111,300.00 - 186,100.00 USD annually" (case difference). That's essentially duplicate but case variation; we could treat as duplicate and keep one. Similarly Stafford, Sterling appear twice with case differences. We'll deduplicate case-insensitively. Let's list unique locations: - USA, OR, Boardman - 111,300.00 - 186,100.00 USD annually - USA, VA, Herndon - 111,300.00 - 186,100.00 USD annually - USA, VA, Louisa - 111,300.00 - 186,100.00 USD annually - USA, VA, Stafford - 111,300.00 - 186,100.00 USD annually - USA, VA, Sterling - 111,300.00 - 186,100.00 USD annually - USA, VA, Woodford - 111,300.00 - 186,100.00 USD annually We also saw "USA, VA, STAFFORD" and "USA, VA, STERLING" and "USA, VA, WOODFORD". So we have those. Thus Pay