Principal Development Manager, AWS Data Center Supply Solutions
Responsibilities
with- each bullet.
Then "About The Team" heading? Actually "About The Team" then "BASIC QUALIFICATIONS" etc. That's qualifications. So we can have
Requirements
orQualifications
. The instruction says we can use Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have BASIC QUALIFICATIONS: Bachelor's degree..., Experience directly related..., 15+ years... Preferred Qualifications: Experience understanding electrical..., Experience managing concurrent..., Experience codifying best practices... Thus we have qualifications (basic and preferred). Could put underQualifications
with two lists: Basic Qualifications and Preferred Qualifications? But we need to use- for any list of duties/requirements/benefits. So we can have a
- for Basic Qualifications and another for Preferred Qualifications, maybe with headings inside? But we cannot add extra headings beyond the allowed? The instruction only says use
- Bachelor's degree in Business Administration, Finance, Economics, Computer Science, Engineering, or related field etc. Then separate
- Preferred Qualifications: ... but that mixes. Better: Use two sections: Requirements (for basic) and Qualifications (for preferred). But the instruction says we can use both Requirements and Qualifications sections. So we can put basic qualifications under Requirements, preferred under Qualifications. That seems reasonable. Then Skills: Not explicitly listed; maybe we can infer from responsibilities: deep data center technical knowledge, ability to balance speed, quality, cost, mentoring, process standardization, stakeholder engagement, change management. But we should not invent details. If not explicitly stated as a separate "Skills" section, we should not create a Skills section unless the posting actually states them. The posting does not have a explicit "Skills" heading. So we should omit Skills section. 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. So we can include a Benefits section. Pay: The posting includes base salary range for location: "USA, TX, Austin - 192,200.00 - 260,000.00 USD annually" etc. Also mentions sign-on payments and RSUs. So we have pay info. So we can include Pay section. Schedule: Not mentioned. So omit Schedule. We also need to include About the Team? Actually we have "About The Team" heading then BASIC QUALIFICATIONS etc. But we already used Requirements and Qualifications sections for that. The "About The Team" heading could be considered part of About the role? But we already have About the role section. The "About The Team" is more about team description; but we have no separate content besides the qualifications. Could treat "About The Team" as part of About the role? But we already used About the role for the initial description. Might be okay to not have a separate About The Team section; we can incorporate its content into Requirements/Qualifications. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate: EEO, accommodation links, etc. Also remove "Company - Amazon Data Services, Inc." maybe minor metadata; we can drop. We need to preserve all substantive information: So we need to keep the salary ranges per location, the benefits description, the responsibilities bullets, the qualifications. Let's craft HTML:
- Project Ownership & Development Execution: Own and manage colocation and leased data center development projects, from post‑lease execution through facility turnover and commissioning; manage a portfolio of concurrent, high‑complexity development projects across a broad geographic area, ensuring consistent execution and on‑time delivery at scale; drive developer/vendor accountability to AWS standards, specifications, and delivery timelines within the assigned portfolio; leverage deep knowledge of data center power and cooling infrastructure to evaluate facility designs, identify risks, and ensure deliverables meet AWS’s technical requirements.
- Repeatable Delivery Process Development: Partner with cross‑functional teams to develop, document, and implement a repeatable, scalable delivery process for colocation and lease development projects; codify best practices, playbooks, templates, and standard operating procedures that enable consistent, high‑quality delivery across the Development Management team; identify process gaps and inefficiencies through lessons learned and translate them into standardized improvements for the broader team; drive adoption of standardized workflows, reporting frameworks, and delivery milestones across all Development Managers and partner teams.
- Change Management: Develop and implement standardized change management protocols across the portfolio to minimize disruption and maintain delivery commitments.
- Stakeholder Engagement: Partner with internal teams across legal, finance, construction, and operations to align development execution with AWS’s long‑term growth objectives; build and maintain relationships with colocation providers, developers, and other third‑party partners to ensure high‑quality, on‑time delivery.
- Bachelor's degree in Business Administration, Finance, Economics, Computer Science, Engineering, or related field
- Experience directly related to the design or construction of large data center facilities, either colocation or client owned/operated
- 15+ years of Real Estate Development, Construction, Engineering, or Data Center Management experience
- Experience understanding electrical and mechanical systems involved in critical data center operations including systems such as feeders, transformers, generators, switch gear, UPS systems, ATS units, PDU units, chillers, pumps, or air handling units
- Experience managing the concurrent delivery of multiple data center projects across diverse markets and regions
- Experience codifying best practices into playbooks, SOPs, and standardized delivery frameworks
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside sections? It says use
for section headings (list). Likely they expect only those headings as top-level sections. Inside we can have
or
- . For qualifications we could have a
summarizing? But we need to preserve all substantive info. So we need to list each qualification item. Could do
- for Preferred Qualifications maybe with a preceding
indicating "Preferred Qualifications:"? But that would be extra text not in a list. Could embed as
About the role
Amazon Web Services (AWS) is seeking an experienced Principal to lead the development management of the most complex colocation and leased data center projects in AWS’s expanding AMER portfolio. This individual will serve as the team’s senior subject matter expert (SME), owning the highest‑complexity projects while partnering with cross‑functional teams to build repeatable, scalable delivery processes and mentoring other Development Managers on the team. At AWS, the Principal Development Manager will serve as the primary owner of the portfolio’s most complex development projects while simultaneously working with partner teams to develop and codify a repeatable delivery process that raises the bar across the entire organization. This role offers the unique opportunity to shape how AWS delivers colocation and leased capacity—not only through direct execution of high‑stakes projects, but by establishing the standards, playbooks, and best practices that other Development Managers follow. You will work at the intersection of development management, data center engineering, and operational excellence, helping AWS meet the ever‑increasing demand for cloud services globally. In addition to managing active development projects, the Principal will serve as a technical and process SME to other Development Managers on the team, providing guidance on complex technical challenges, change management decisions, and project controls best practices. The ideal candidate is a results‑driven leader who combines deep data center technical knowledge, the ability to balance speed, quality, and cost while mentoring others and driving process standardization across a geographically dispersed portfolio.
Responsibilities
Requirements
Qualifications
Benefits
Amazon 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. The package also includes sign‑on payments and restricted stock units (RSUs).
Pay
Base salary range: USA, TX, Austin – $192,200.00 – $260,000.00 USD annually; USA, VA, Herndon – $192,200.00 – $260,000.00 USD annually; USA, WA, Seattle – $192,200.00 – $260,000.00 USD annually. Final compensation will be determined based on experience, qualifications, and location, and includes sign‑on payments and RSUs.
We must ensure no extra sections like Schedule. Also ensure we didn't include any boilerplate like EEO, accommodation links, etc. We removed them. Check that we didn't repeat job title as heading. Good. Check that we didn't include any placeholder like "commensurate with experience". Not present. Check that we preserved all substantive info: The description paragraphs, responsibilities bullets, qualifications, benefits, pay. We omitted "About The Team" heading but its content is covered in qualifications. The "About The Team" line itself is just a heading; we can drop as it's not substantive beyond that. The "Company - Amazon Data Services, Inc." and Job
- for any list of duties/requirements/benefits. So we can have a