Data Center Project Architect

We need to output HTML fragment with sections: headings

for sections like 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. Remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the description. Key parts: - Description: Amazon Web Services (AWS) is seeking a Data Center Project Architect to join its design team in Herndon, VA. (We can include location maybe in a short paragraph.) - AWS Infrastructure Services ... (description of team). This is about the role. - As a DC Project Architect at AWS, you will lead designs for Amazon DCs in our Americas Region and impact other projects around the world. As a DC Project Architect, you will be part of a highly creative and efficient design team comprised of Architects, Engineers, and Designers tasked with solving problems and challenging the status quo. As a subject matter expert, you will have a direct impact on the design of prototypical DC facilities, provide technical guidance, solve large scale implementation issues, and be responsible for architectural design requirements. - Key job responsibilities (list). Then bullet list. - About The Team (section). Contains subsections: Diverse Experiences, Why AWS? (with subpoints: Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). Might treat as part of About the role? Could be separate sections: About the team, Why AWS? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. - Basic Qualifications (list). Preferred Qualifications (list). Could be under Requirements or Qualifications. - Benefits: described: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also mention sign-on payments and RSUs. Also mention base salary range. - Pay: base salary range: "USA, VA, Herndon - 96,600.00 - 160,000.00 USD annually". Also mention sign-on payments and RSUs. - Schedule: Not mentioned explicitly. Travel anticipated not to exceed 25% (that's travel). Could be considered schedule? Not exactly. There's no explicit schedule like full-time, etc. Might omit Schedule section if no specific content. - Skills: maybe from qualifications: proficiency in building codes, etc. Could be under Skills. We need to avoid filler like "commensurate with experience". Not present. We must not include duplicated lines. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove lines about Amazon is an equal opportunity employer, accommodation link, etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe keep benefits description but not the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive? It's a reference; could be considered boilerplate? Might be okay to keep but it's a link. Probably safe to keep as part of benefits description? Might be considered navigation? I'd drop the link to be safe. Also remove "Company - Amazon Data Services, Inc." maybe not needed but it's substantive? It's metadata about employer. Could be included in a short paragraph about the role? Might be considered minor metadata; we can fold into a short

or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include company name in a short paragraph. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Amazon Web Services (AWS) is seeking a Data Center Project Architect to join its design team in Herndon, VA. AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure, supporting data centers and the servers, storage, networking, power, and cooling equipment that ensure continual customer access. The team works on challenging problems with thousands of variables impacting the supply chain, collaborating with software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles to deliver high standards for safety and security while providing seemingly infinite capacity at the lowest possible cost. As a Data Center Project Architect, you will lead designs for Amazon data centers in the Americas Region, impact global projects, serve as a subject matter expert on prototypical DC facilities, provide technical guidance, solve large‑scale implementation issues, and be responsible for architectural design requirements.

Responsibilities

• Communicate conceptual designs and create/maintain project documentation before, during, and after construction.
• Maintain Basis of Design, prototype design, and template specifications for architectural elements.
• Review and inform design RFPs.
• Manage external design consultants through the design and construction process.
• Coordinate with internal and external Civil, Structural, Mechanical, Electrical, Controls, and Cabling design engineers.
• Effectively communicate design standards to internal and external project partners.
• Manage multiple fast‑paced projects simultaneously.
• Think outside the box to find innovative solutions prior to and during construction to reduce costs without negative impacts on quality or reliability.
• Travel for site assessments, internal design meetings, construction review, and interfacing with design consultants (anticipated travel not to exceed 25%).

About the team

AWS values diverse experiences and encourages candidates from non‑traditional backgrounds to apply. The team fosters an inclusive culture through employee‑led affinity groups, events such as Conversations on Race and Ethnicity (CORE) and AmazeCon, and ongoing learning experiences. Mentorship and career‑growth resources are available to help you develop into a better‑rounded professional, and the company promotes work‑life harmony by striving for flexibility in the working culture.

Basic qualifications

• Knowledge of Microsoft Office including Outlook, Word, and Excel
• Experience with the design, construction, operation, or maintenance of mission critical facilities, especially data centers
• 4+ years of technical specialist, design and architecture experience
• NCARB‑recognized architecture license
• 1+ years leading sub‑consultants and project teams
• Proficiency in building codes, regulations, and standards including IBC or equivalent

Preferred qualifications

• Knowledge of building codes and regulations for your region
• Experience carrying design concepts through exploration, development, and into deployment or mass production
• Ability to travel internationally

Benefits

• Sign‑on payments and restricted stock units (RSUs)
• Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D, option for supplemental life plans)
• Employee Assistance Program (EAP), mental health support, medical advice line
• Flexible Spending Accounts
• Adoption and surrogacy reimbursement coverage
• 401(k) matching
• Paid time off
• Parental leave

Pay

Base salary range: $96,600.00 – $160,000.00 USD annually (Herndon, VA). Total compensation includes sign‑on payments and RSUs, with final amount based on experience, qualifications, and location.

We omitted Schedule as no specific content. Check for any duplicated lines: we have not repeated. Check for any boilerplate: we removed EEO, accommodation link, "Learn more about our benefits at ...", "Company - Amazon Data Services, Inc.", Job ID. We kept location in About the role and Pay. We kept travel note in Responsibilities. We kept "About the team" section; not exactly in the prescribed headings list but we used "About the team". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But they also say "include a section ONLY when the posting has real, specific content for it". They gave examples but not strict list. However safer to stick to those headings. We could map "About the team" content under "About the role" or "Requirements"? But we have a lot of team/culture info. Could fit under "About the role" as part of description. But we already have a long paragraph. Could incorporate team/culture into About the role paragraph. However we already have a separate About the team section. Might be okay but risk deviating from expected headings. Let's see if we can incorporate team/culture into About the role paragraph, making About the role longer but still okay. Then we can drop About the team section. We need to keep all substantive info: diverse experiences, inclusive culture, affinity groups, CORE, AmazeCon, mentorship, career growth, work-life balance. We'll embed those. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine Basic and Preferred qualifications?), Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Could combine Basic and Preferred qualifications into Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Qualifications (covering both basic and preferred), Benefits, Pay. Skills could be part of Qualifications. Let's decide. We have basic qualifications list and preferred qualifications list. Could combine into a single Qualifications section with two subheadings? But we cannot use subheadings other than

. Could just list all qualifications together, maybe separate basic vs preferred with plain text. But we need to preserve all info. Could do:

Qualifications

Basic qualifications:

...

Preferred qualifications:

...

That's acceptable. Skills: we could embed within qualifications (proficiency in building codes etc.) So we may not need separate Skills. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if we need Requirements separate? Not needed. Let's craft About the role paragraph to include location, team description, culture, etc. We'll write:

About the role

Amazon Web Services (AWS) is seeking a Data Center Project Architect to join its design team in Herndon, VA. AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure, supporting data centers and the servers, storage, networking, power, and cooling equipment that ensure continual customer access. The team works on challenging problems with thousands of variables impacting the supply chain, collaborating with software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles to deliver high standards for safety and security while providing seemingly infinite capacity at the lowest possible cost. As a Data Center Project Architect, you will lead designs for Amazon data centers in the Americas Region, impact global projects, serve as a subject matter expert on prototypical DC facilities, provide technical guidance, solve large‑scale implementation issues, and be responsible for architectural design requirements. AWS values diverse experiences and encourages candidates from non‑traditional backgrounds to apply. The team fosters an