TIPM, AI Data Center Network Build, MLZ BaND
for each. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. Do not invent or summarize away detail. Include a section only when posting has real specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to extract content.
Let's parse the description.
First paragraph: "Description The infrastructure powering AWS's next-generation AI services does not build itself..." This is description. Could be "About the role" maybe.
Then "What You Will Own" bullet list (actually sentences). Then "What You Bring" bullet list. Then "Why This Role Stands Out". Then "Key job responsibilities" bullet list. Then "A day in the life". Then "About The Team". Then "Basic Qualifications". Then "Preferred Qualifications". Then EEO etc. Then benefits and salary info.
We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
- About the role: likely the initial description and maybe "What You Will Own" and "Why This Role Stands Out" and "About The Team". Could be combined.
- Responsibilities: "What You Will Own" and "Key job responsibilities" and "A day in the life".
- Requirements: maybe "Basic Qualifications" and "Preferred Qualifications"? Actually Requirements could be basic qualifications. Qualifications could be preferred? But we have both Requirements and Qualifications sections. We need to decide.
- Skills: maybe "What You Bring" includes skills.
- Benefits: posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also "sign-on payments and restricted stock units (RSUs)". So we have benefits content.
- Pay: posting includes base salary range: "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, Herndon - 127,100.00 - 171,900.00 USD annually". So we have pay info.
- Schedule: not mentioned. No schedule info. So we should NOT create Schedule section.
We must not create sections with placeholder/filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. No Schedule.
We need to ensure we don't repeat content unnecessarily but preserve all substantive info. We can combine overlapping info but must not lose detail.
We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. Many bullet-like sentences are separated by line breaks. We can turn them into
- .
We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions. Also remove duplicated lines.
We need to preserve all substantive info: that includes description, what you will own, what you bring, why role stands out, key responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay.
We need to avoid repeating same info across sections if possible, but we must preserve all substantive info. Could be okay to have some overlap but better to avoid duplication.
Let's extract each piece.
**About the role** (maybe combine initial description and "Why This Role Stands Out" and "About The Team").
Initial description: "The infrastructure powering AWS's next-generation AI services does not build itself. Behind every large-scale machine learning workload is a physical network: racks of compute, miles of fiber, and a precise sequence of construction, deployment, and validation events that have to land on time and in the right order. The AMER AWS Brick and Network Deployment (BaND) ML team owns Machine Learning DC Network Delivery across the US for customized DC’s built for ML. We are looking for a Technical Program Manager who wants to be at the center of it. You will own network delivery end-to-end across a portfolio of US-wide data center builds, driving the full network lifecycle from early construction coordination through network general services, optical turnup, and production fabric readiness. You will work directly with network engineers, data center construction teams, optical design, and supply chain, cutting through ambiguity, resolving blockers, and keeping complex multi-stream programs moving in parallel. Candidates who arrive with fluency in hyperscale network architecture, structured cabling systems, and data center construction sequencing will be effective from the first week. The work is technical, fast-paced, and consequential."
"Why This Role Stands Out": "The BaND ML team operates at the intersection of physical construction and hyperscale network delivery at a scale very few organizations reach. You will manage concurrent builds across multiple US regions, own real program outcomes that directly affect AWS's AI capacity roadmap, and develop deep cross-functional relationships across some of the most technically demanding infrastructure teams in the industry. If you have been looking for a role where your data center and network domain knowledge is a genuine competitive advantage from day one, this is it."
"About The Team": "The Brick and Network Deployment (BaND) team ensures network and port capacity is ready for incoming customer server racks across AWS data centers. As a Technical Infrastructure Program Manager (TIPM), you will coordinate with infrastructure, networking, optical, and supply chain teams to deliver that capacity on time. AWS values diverse experiences and nontraditional career paths -- we encourage all qualified candidates to apply. We offer a culture built on curiosity and inclusion, ongoing mentorship and career development, and a genuine commitment to work-life flexibility."
We can combine these into About the role section as prose (maybe multiple paragraphs). Use
for each paragraph.
**Responsibilities**: includes "What You Will Own", "Key job responsibilities", "A day in the life". Also maybe some from description.
Let's list them.
What You Will Own (bullet-like sentences):
- End-to-end network delivery across all service layers for US-wide builds: production fabric (10p10u ML brick rack deployments including top-of-rack and spine cabling), optical (border, edge, backbone, and internet circuit turnup), and general services (Corp, security, WiFi, management console)
- Rack deployment sequencing and cabling execution: you understand structured cabling plant, tray fill, fiber termination workflows, cut sheet coordination, and what it takes to move from empty cage to powered and patched on a hyperscale floor
- Optical and circuit readiness: familiarity with DWDM, dark fiber provisioning, circuit activation workflows, and the handoff sequence between optical design, field teams, and network engineering
- Construction phase coordination: you know how MEP sequencing, raised floor or overhead cable routing, and power-on sequencing affect network deployment timelines
- Cross-org coordination across Network Engineering, Cabling, Construction, and supply chain to maintain critical path alignment and surface dependencies before they become blockers
- Milestone tracking and readiness reporting tied to key program gates, with clear escalation to senior leadership when commitments are at risk
- Escalation ownership: you identify the blocker, frame the ask, and drive resolution with the right stakeholders at the right level
Key job responsibilities (bullet-like):
- Work with stakeholders (networking engineers/tech program managers/senior management) to define requirements and processes.
- Manage the dependencies and the interfaces between projects and negotiate the trade-offs needed.
- Provide program progress reporting on a regular basis.
- End to end responsibility for the program’s execution and success.
- Manage multiple competing projects/programs simultaneously.
- Develop and implement scalable, data-driven process improvement/automated solutions.
- Keep the customer experience as the primary focus.
- Meets/exceeds Amazon’s leadership principles requirements for this role
A day in the life:
- Day-to-day, you track build milestones, coordinate across engineering and operations teams, manage contractor and vendor schedules, and surface risks to leadership before they impact timelines.
- You serve as the connective tissue between physical construction and network readiness, ensuring capacity comes online on time.
- Success in this role requires strong cross-functional communication, schedule management discipline, and the ability to drive clarity in complex, fast-moving environments.
We can combine these into a list under Responsibilities.
**Requirements**: Basic Qualifications:
- 3+ years of technical infrastructure management experience
- Knowledge of best practices and emerging technologies, related to infrastructure (i.e. network, data center, hardware, software)
- Experience with varying scenarios of infrastructure builds
**Qualifications**: Preferred Qualifications:
- 2+ years of computer networking experience, or experience in networking
- Experience with large scale infrastructure
**Skills**: What You Bring:
- 3+ years of technical program management experience in hyperscale infrastructure, network deployment, or data center construction environments
- Hands-on familiarity with large-scale structured cabling systems: you can read a cut sheet, understand tray and conduit routing, and have a working mental model of how fiber moves through a data center building
- Working knowledge of data center network architecture at scale: CLOS topologies, spine-leaf fabric design, ToR switching, and how production ML fabrics differ from standard compute deployments
- Experience coordinating across construction, facilities, and network engineering in a live build environment, including managing the interface between construction milestones and network deployment readiness
- Demonstrated ability to manage multiple concurrent workstreams across organizational boundaries without losing precision on any of them
- Comfort going deep on technical dependencies while communicating clearly at the leadership level: you can translate a fiber tray congestion issue into a program risk statement for Director level audience without losing accuracy
- A bias for action and a track record of moving programs forward in ambiguous, fast-moving environments
- Strong written and verbal communication: you write clearly, escalate with precision, and do not bury the lead
We could also include some from description like fluency in hyperscale network architecture etc. But that's covered.
**Benefits**: from posting:
- 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
- parental leave
- sign-on payments and restricted stock units (RSUs)
Also mention: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link but maybe we can keep as prose.
**Pay**: base salary range: USA, VA, Herndon - 127,100.00 - 171,900.00 USD annually. Also mention sign-on payments and RSUs, final compensation based on experience, qualifications, location.
We should include that as prose.
We must not include Schedule section.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
...
...
Responsibilities
- ...
...
Similarly for Requirements, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't include any empty sections.
Let's craft the content.
**About the role** paragraphs:
Paragraph 1: The infrastructure powering AWS's next-generation AI services does not build itself. Behind every large-scale machine learning
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. Do not invent or summarize away detail. Include a section only when posting has real specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to extract content. Let's parse the description. First paragraph: "Description The infrastructure powering AWS's next-generation AI services does not build itself..." This is description. Could be "About the role" maybe. Then "What You Will Own" bullet list (actually sentences). Then "What You Bring" bullet list. Then "Why This Role Stands Out". Then "Key job responsibilities" bullet list. Then "A day in the life". Then "About The Team". Then "Basic Qualifications". Then "Preferred Qualifications". Then EEO etc. Then benefits and salary info. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where. - About the role: likely the initial description and maybe "What You Will Own" and "Why This Role Stands Out" and "About The Team". Could be combined. - Responsibilities: "What You Will Own" and "Key job responsibilities" and "A day in the life". - Requirements: maybe "Basic Qualifications" and "Preferred Qualifications"? Actually Requirements could be basic qualifications. Qualifications could be preferred? But we have both Requirements and Qualifications sections. We need to decide. - Skills: maybe "What You Bring" includes skills. - Benefits: posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also "sign-on payments and restricted stock units (RSUs)". So we have benefits content. - Pay: posting includes base salary range: "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, Herndon - 127,100.00 - 171,900.00 USD annually". So we have pay info. - Schedule: not mentioned. No schedule info. So we should NOT create Schedule section. We must not create sections with placeholder/filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. No Schedule. We need to ensure we don't repeat content unnecessarily but preserve all substantive info. We can combine overlapping info but must not lose detail. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. Many bullet-like sentences are separated by line breaks. We can turn them into
- .
We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions. Also remove duplicated lines.
We need to preserve all substantive info: that includes description, what you will own, what you bring, why role stands out, key responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay.
We need to avoid repeating same info across sections if possible, but we must preserve all substantive info. Could be okay to have some overlap but better to avoid duplication.
Let's extract each piece.
**About the role** (maybe combine initial description and "Why This Role Stands Out" and "About The Team").
Initial description: "The infrastructure powering AWS's next-generation AI services does not build itself. Behind every large-scale machine learning workload is a physical network: racks of compute, miles of fiber, and a precise sequence of construction, deployment, and validation events that have to land on time and in the right order. The AMER AWS Brick and Network Deployment (BaND) ML team owns Machine Learning DC Network Delivery across the US for customized DC’s built for ML. We are looking for a Technical Program Manager who wants to be at the center of it. You will own network delivery end-to-end across a portfolio of US-wide data center builds, driving the full network lifecycle from early construction coordination through network general services, optical turnup, and production fabric readiness. You will work directly with network engineers, data center construction teams, optical design, and supply chain, cutting through ambiguity, resolving blockers, and keeping complex multi-stream programs moving in parallel. Candidates who arrive with fluency in hyperscale network architecture, structured cabling systems, and data center construction sequencing will be effective from the first week. The work is technical, fast-paced, and consequential."
"Why This Role Stands Out": "The BaND ML team operates at the intersection of physical construction and hyperscale network delivery at a scale very few organizations reach. You will manage concurrent builds across multiple US regions, own real program outcomes that directly affect AWS's AI capacity roadmap, and develop deep cross-functional relationships across some of the most technically demanding infrastructure teams in the industry. If you have been looking for a role where your data center and network domain knowledge is a genuine competitive advantage from day one, this is it."
"About The Team": "The Brick and Network Deployment (BaND) team ensures network and port capacity is ready for incoming customer server racks across AWS data centers. As a Technical Infrastructure Program Manager (TIPM), you will coordinate with infrastructure, networking, optical, and supply chain teams to deliver that capacity on time. AWS values diverse experiences and nontraditional career paths -- we encourage all qualified candidates to apply. We offer a culture built on curiosity and inclusion, ongoing mentorship and career development, and a genuine commitment to work-life flexibility."
We can combine these into About the role section as prose (maybe multiple paragraphs). Use
for each paragraph.
**Responsibilities**: includes "What You Will Own", "Key job responsibilities", "A day in the life". Also maybe some from description.
Let's list them.
What You Will Own (bullet-like sentences):
- End-to-end network delivery across all service layers for US-wide builds: production fabric (10p10u ML brick rack deployments including top-of-rack and spine cabling), optical (border, edge, backbone, and internet circuit turnup), and general services (Corp, security, WiFi, management console)
- Rack deployment sequencing and cabling execution: you understand structured cabling plant, tray fill, fiber termination workflows, cut sheet coordination, and what it takes to move from empty cage to powered and patched on a hyperscale floor
- Optical and circuit readiness: familiarity with DWDM, dark fiber provisioning, circuit activation workflows, and the handoff sequence between optical design, field teams, and network engineering
- Construction phase coordination: you know how MEP sequencing, raised floor or overhead cable routing, and power-on sequencing affect network deployment timelines
- Cross-org coordination across Network Engineering, Cabling, Construction, and supply chain to maintain critical path alignment and surface dependencies before they become blockers
- Milestone tracking and readiness reporting tied to key program gates, with clear escalation to senior leadership when commitments are at risk
- Escalation ownership: you identify the blocker, frame the ask, and drive resolution with the right stakeholders at the right level
Key job responsibilities (bullet-like):
- Work with stakeholders (networking engineers/tech program managers/senior management) to define requirements and processes.
- Manage the dependencies and the interfaces between projects and negotiate the trade-offs needed.
- Provide program progress reporting on a regular basis.
- End to end responsibility for the program’s execution and success.
- Manage multiple competing projects/programs simultaneously.
- Develop and implement scalable, data-driven process improvement/automated solutions.
- Keep the customer experience as the primary focus.
- Meets/exceeds Amazon’s leadership principles requirements for this role
A day in the life:
- Day-to-day, you track build milestones, coordinate across engineering and operations teams, manage contractor and vendor schedules, and surface risks to leadership before they impact timelines.
- You serve as the connective tissue between physical construction and network readiness, ensuring capacity comes online on time.
- Success in this role requires strong cross-functional communication, schedule management discipline, and the ability to drive clarity in complex, fast-moving environments.
We can combine these into a list under Responsibilities.
**Requirements**: Basic Qualifications:
- 3+ years of technical infrastructure management experience
- Knowledge of best practices and emerging technologies, related to infrastructure (i.e. network, data center, hardware, software)
- Experience with varying scenarios of infrastructure builds
**Qualifications**: Preferred Qualifications:
- 2+ years of computer networking experience, or experience in networking
- Experience with large scale infrastructure
**Skills**: What You Bring:
- 3+ years of technical program management experience in hyperscale infrastructure, network deployment, or data center construction environments
- Hands-on familiarity with large-scale structured cabling systems: you can read a cut sheet, understand tray and conduit routing, and have a working mental model of how fiber moves through a data center building
- Working knowledge of data center network architecture at scale: CLOS topologies, spine-leaf fabric design, ToR switching, and how production ML fabrics differ from standard compute deployments
- Experience coordinating across construction, facilities, and network engineering in a live build environment, including managing the interface between construction milestones and network deployment readiness
- Demonstrated ability to manage multiple concurrent workstreams across organizational boundaries without losing precision on any of them
- Comfort going deep on technical dependencies while communicating clearly at the leadership level: you can translate a fiber tray congestion issue into a program risk statement for Director level audience without losing accuracy
- A bias for action and a track record of moving programs forward in ambiguous, fast-moving environments
- Strong written and verbal communication: you write clearly, escalate with precision, and do not bury the lead
We could also include some from description like fluency in hyperscale network architecture etc. But that's covered.
**Benefits**: from posting:
- 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
- parental leave
- sign-on payments and restricted stock units (RSUs)
Also mention: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link but maybe we can keep as prose.
**Pay**: base salary range: USA, VA, Herndon - 127,100.00 - 171,900.00 USD annually. Also mention sign-on payments and RSUs, final compensation based on experience, qualifications, location.
We should include that as prose.
We must not include Schedule section.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
...
...
Responsibilities
- ...
...
Similarly for Requirements, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't include any empty sections.
Let's craft the content.
**About the role** paragraphs:
Paragraph 1: The infrastructure powering AWS's next-generation AI services does not build itself. Behind every large-scale machine learning
for prose. We need to decide what constitutes a list. Many bullet-like sentences are separated by line breaks. We can turn them into
- .
We must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions. Also remove duplicated lines.
We need to preserve all substantive info: that includes description, what you will own, what you bring, why role stands out, key responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay.
We need to avoid repeating same info across sections if possible, but we must preserve all substantive info. Could be okay to have some overlap but better to avoid duplication.
Let's extract each piece.
**About the role** (maybe combine initial description and "Why This Role Stands Out" and "About The Team").
Initial description: "The infrastructure powering AWS's next-generation AI services does not build itself. Behind every large-scale machine learning workload is a physical network: racks of compute, miles of fiber, and a precise sequence of construction, deployment, and validation events that have to land on time and in the right order. The AMER AWS Brick and Network Deployment (BaND) ML team owns Machine Learning DC Network Delivery across the US for customized DC’s built for ML. We are looking for a Technical Program Manager who wants to be at the center of it. You will own network delivery end-to-end across a portfolio of US-wide data center builds, driving the full network lifecycle from early construction coordination through network general services, optical turnup, and production fabric readiness. You will work directly with network engineers, data center construction teams, optical design, and supply chain, cutting through ambiguity, resolving blockers, and keeping complex multi-stream programs moving in parallel. Candidates who arrive with fluency in hyperscale network architecture, structured cabling systems, and data center construction sequencing will be effective from the first week. The work is technical, fast-paced, and consequential."
"Why This Role Stands Out": "The BaND ML team operates at the intersection of physical construction and hyperscale network delivery at a scale very few organizations reach. You will manage concurrent builds across multiple US regions, own real program outcomes that directly affect AWS's AI capacity roadmap, and develop deep cross-functional relationships across some of the most technically demanding infrastructure teams in the industry. If you have been looking for a role where your data center and network domain knowledge is a genuine competitive advantage from day one, this is it."
"About The Team": "The Brick and Network Deployment (BaND) team ensures network and port capacity is ready for incoming customer server racks across AWS data centers. As a Technical Infrastructure Program Manager (TIPM), you will coordinate with infrastructure, networking, optical, and supply chain teams to deliver that capacity on time. AWS values diverse experiences and nontraditional career paths -- we encourage all qualified candidates to apply. We offer a culture built on curiosity and inclusion, ongoing mentorship and career development, and a genuine commitment to work-life flexibility."
We can combine these into About the role section as prose (maybe multiple paragraphs). Use
for each paragraph. **Responsibilities**: includes "What You Will Own", "Key job responsibilities", "A day in the life". Also maybe some from description. Let's list them. What You Will Own (bullet-like sentences): - End-to-end network delivery across all service layers for US-wide builds: production fabric (10p10u ML brick rack deployments including top-of-rack and spine cabling), optical (border, edge, backbone, and internet circuit turnup), and general services (Corp, security, WiFi, management console) - Rack deployment sequencing and cabling execution: you understand structured cabling plant, tray fill, fiber termination workflows, cut sheet coordination, and what it takes to move from empty cage to powered and patched on a hyperscale floor - Optical and circuit readiness: familiarity with DWDM, dark fiber provisioning, circuit activation workflows, and the handoff sequence between optical design, field teams, and network engineering - Construction phase coordination: you know how MEP sequencing, raised floor or overhead cable routing, and power-on sequencing affect network deployment timelines - Cross-org coordination across Network Engineering, Cabling, Construction, and supply chain to maintain critical path alignment and surface dependencies before they become blockers - Milestone tracking and readiness reporting tied to key program gates, with clear escalation to senior leadership when commitments are at risk - Escalation ownership: you identify the blocker, frame the ask, and drive resolution with the right stakeholders at the right level Key job responsibilities (bullet-like): - Work with stakeholders (networking engineers/tech program managers/senior management) to define requirements and processes. - Manage the dependencies and the interfaces between projects and negotiate the trade-offs needed. - Provide program progress reporting on a regular basis. - End to end responsibility for the program’s execution and success. - Manage multiple competing projects/programs simultaneously. - Develop and implement scalable, data-driven process improvement/automated solutions. - Keep the customer experience as the primary focus. - Meets/exceeds Amazon’s leadership principles requirements for this role A day in the life: - Day-to-day, you track build milestones, coordinate across engineering and operations teams, manage contractor and vendor schedules, and surface risks to leadership before they impact timelines. - You serve as the connective tissue between physical construction and network readiness, ensuring capacity comes online on time. - Success in this role requires strong cross-functional communication, schedule management discipline, and the ability to drive clarity in complex, fast-moving environments. We can combine these into a list under Responsibilities. **Requirements**: Basic Qualifications: - 3+ years of technical infrastructure management experience - Knowledge of best practices and emerging technologies, related to infrastructure (i.e. network, data center, hardware, software) - Experience with varying scenarios of infrastructure builds **Qualifications**: Preferred Qualifications: - 2+ years of computer networking experience, or experience in networking - Experience with large scale infrastructure **Skills**: What You Bring: - 3+ years of technical program management experience in hyperscale infrastructure, network deployment, or data center construction environments - Hands-on familiarity with large-scale structured cabling systems: you can read a cut sheet, understand tray and conduit routing, and have a working mental model of how fiber moves through a data center building - Working knowledge of data center network architecture at scale: CLOS topologies, spine-leaf fabric design, ToR switching, and how production ML fabrics differ from standard compute deployments - Experience coordinating across construction, facilities, and network engineering in a live build environment, including managing the interface between construction milestones and network deployment readiness - Demonstrated ability to manage multiple concurrent workstreams across organizational boundaries without losing precision on any of them - Comfort going deep on technical dependencies while communicating clearly at the leadership level: you can translate a fiber tray congestion issue into a program risk statement for Director level audience without losing accuracy - A bias for action and a track record of moving programs forward in ambiguous, fast-moving environments - Strong written and verbal communication: you write clearly, escalate with precision, and do not bury the lead We could also include some from description like fluency in hyperscale network architecture etc. But that's covered. **Benefits**: from posting: - 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 - parental leave - sign-on payments and restricted stock units (RSUs) Also mention: "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link but maybe we can keep as prose. **Pay**: base salary range: USA, VA, Herndon - 127,100.00 - 171,900.00 USD annually. Also mention sign-on payments and RSUs, final compensation based on experience, qualifications, location. We should include that as prose. We must not include Schedule section. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce something like:
About the role
...
...
...Responsibilities
- ... ...