Sr Technical Program Manager - Hardware, AWS Generative AI & ML Servers
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. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the description and extract sections.
The posting includes:
- Description (intro) about AWS GPU fleet etc. Could be "About the role" maybe.
- "What You Will Do" -> Responsibilities.
- "Why You Will Love It" maybe could be part of About the role or Benefits? It's more about motivation; could be part of About the role or maybe a separate section like "What We Offer"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
- "The Ideal Candidate" -> maybe Qualifications or Requirements.
- "Key job responsibilities" with subheadings: Strategy & Mechanisms, Requirements & Planning, Execution & Coordination, Risk & Quality, Transition. Those are responsibilities details.
- "A day in the life" maybe part of About the role.
- "About The Team" maybe About the role.
- "Basic Qualifications" -> Requirements.
- "Preferred Qualifications" -> Qualifications.
- Benefits: there is a paragraph about benefits after salary ranges: "Amazon also offers comprehensive benefits including health insurance ...". Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also "Final compensation will be determined based on factors including experience, qualifications, and location." Also salary ranges listed per location.
- Pay: we have salary ranges for three locations. Should we include Pay section? Yes, we have specific numbers. So include Pay.
- Schedule: not mentioned besides occasional travel ( for each section heading.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we should list items as
- . For requirements and qualifications also list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like specific tasks, etc.
We must not include boilerplate like EEO, equal opportunity, scam warning, legal, cookie/navigation, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, About the role section: combine introductory paragraphs, "Why You Will Love It", "A day in the life", "About The Team". Keep as prose (
) maybe multiple paragraphs.
We need to avoid repeating content verbatim? We can keep as is.
Let's extract:
Intro: "AWS operates the world's largest fleet of GPU-accelerated servers powering AI/ML workloads at cloud scale. Our team designs, builds, and operates this fleet — solving systemic hardware issues and building systems that detect and prevent recurrence so customers experience the highest quality of service. We are seeking a Senior Technical Program Manager to drive end-to-end delivery of GPU-accelerated servers across our global fleet. You will coordinate cross-functional engineering teams spanning hardware, firmware, and software, manage ODM partnerships across multiple continents, and establish closed-loop quality systems that drive continuous improvements. This role requires technical depth to translate engineering constraints into program risk, combined with program management excellence to deliver complex hardware at global scale."
Why You Will Love It: "The world's most advanced frontier models are trained on the platforms you help build. Your programs launch the GPU servers that power the largest AI/ML workloads on the planet. You will see your decisions reflected in fleet reliability metrics within weeks of deployment. The team is small and high-trust — you own programs end to end from concept through production, with direct access to leadership and engineering alike."
A day in the life: paragraph describing typical day.
About The Team: "The Hardware Engineering AI/ML UltraServer platform team is a group of engineers and technical program managers directly responsible for launching GPU-accelerated servers into the AWS fleet. Located in Seattle, Austin, and Cupertino, we collaborate with global development teams and ODM partners to deliver next-generation AI/ML infrastructure deployed in datacenters worldwide. We move fast with small, empowered teams delivering end-to-end — from server conception through fleet-scale operations."
We can combine into About the role.
Now Responsibilities: "What You Will Do" plus the key job responsibilities subsections.
What You Will Do: "You will own programs where the critical path runs through silicon, firmware, and software teams simultaneously. You will translate ambiguity into structure: turning a fleet telemetry signal into a corrective action plan with quantified failure rates, a customer requirement into a new platform milestone with EVT/DVT/PVT gates, or a manufacturing escape into a design change with updated validation criteria. You will drive decisions on program trade-offs — adjusting scope when qualification gates slip, balancing deployment speed against fleet risk, and determining when to accept interim mitigations instead of holding for root-cause fixes. When a large scale of GPU servers depend on your program landing on time, you are the one ensuring hardware readiness, qualification completeness, and operational handoff happen without gaps."
Then key job responsibilities with subheadings; we can incorporate as list items under Responsibilities.
We need to use
- for any list of duties/requirements/benefits. So we can make each responsibility as a list item. Could also keep subheadings as
? Not allowed; only headings allowed are for sections. We cannot add other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use
for prose and
- for lists. We can embed subheadings as bold text within
maybe. But better to keep as list items with description.
We'll create a
with items covering each bullet.
List items:
- Define program strategy, objectives, and success criteria; influence resource allocation and priority decisions across engineering workstreams to align with organizational goals (Strategy & Mechanisms)
- Build and own mechanisms for program visibility — defining metrics, dashboards, and review cadences that enable data-driven decisions and early risk detection
- Streamline delivery processes across teams; identify and eliminate dependencies, redundant gates, or coordination overhead that slow velocity
- Facilitate requirements gathering with internal customers; develop Technical Requirements Documents (TRDs) covering server specs, rack configurations, PCIe topology, power/cooling topology, and SKU definitions (Requirements & Planning)
- Build program timelines aligned to different phases (Program Initiation, Design, Qualification, Pilot, Post-launch) with critical path analysis, risk identification with new & unique changes to the hardware, and milestone tracking for the program.
- Drive Program Initiation reviews: scope definition, preliminary annualized failure rate predictions, resource planning, supply chain long-lead identification, and RFP (Request for Proposal) issuance to ODMs
- Drive cross-functional alignment across hardware, firmware (BIOS, BMC, CPLD), software, and operations teams through design reviews, manufacturing readiness and production readiness for fleet deployment.
- Manage ODM partnerships: track EVT/DVT/PVT builds, manufacturing readiness gates, Bill of Materials (BOM) management in PLM systems, and quality checkpoints
- Identify blockers early, escalate dependencies before they impact critical path, and facilitate technical trade-off decisions across engineering workstreams.
- Communicate program status to leadership with clear reporting on milestone progress, risk posture, and mitigation plans.
- Challenge technical workstreams to surface risks early; quantify impact to schedule and reliability (annualized failure rate targets, availability SLAs) with proposed mitigations (Risk & Quality)
- Drive root cause analysis of fleet-wide hardware failures and ensure corrective actions flow back into qualification criteria and design requirements
- Define acceptance criteria, coordinate qualification testing at server and rack levels, and manage go/no-go decisions for mission-critical AI/ML workloads
- Conduct knowledge transfer and document lessons learned; ensure operational readiness including automation, monitoring, and runbook completeness for production handoff (Transition)
Also include the earlier "What You Will Do" paragraphs maybe as prose before list.
Now Requirements: Basic Qualifications list:
- Bachelor's degree in Computer Science, Electrical Engineering, Computer Engineering or a related discipline or equivalent
- Experience managing programs across cross-functional teams, building processes and coordinating release schedules
- 6+ years of technical product or program management experience, working directly with multiple engineering teams.
- 5+ years of experience driving hardware development programs (servers, racks, networking, or storage) through full product lifecycle including design, validation, manufacturing, and fleet deployment
We could also include any other basic qualifications? That's it.
Now Qualifications: Preferred Qualifications list:
- Master's degree in Computer Science, Computer Engineering, Electrical Engineering, or related fields
- Experience leading the design, automation, deployment, and support of large-scale infrastructure
- Experience facilitating discussions with senior leadership regarding technical / architectural trade-offs, best practices, and risk mitigation
- 5+ years of experience coordinating complex server programs with ODM/JDM partners across multiple geographies, managing design reviews, manufacturing readiness gates, and quality checkpoints
- 5+ years of experience working with GPU/accelerator server platforms, NPI (New Product Introduction), or hardware qualification programs across various phases (EVT, DVT, PVT)
- Experience driving root cause analysis and corrective action processes for hardware reliability issues at fleet scale
- Knowledge of server hardware development lifecycle: electrical/mechanical design, firmware, thermal/power validation, and manufacturing testing.
Now Benefits: list of benefits:
- 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) (mentioned earlier)
- Also maybe mention "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation but could be benefits.
We'll include as list.
Pay: Provide salary ranges per location:
- USA, CA, Cupertino: $171,000.00 - $231,400.00 USD annually
- USA, TX, Austin: $148,700.00 - $201,200.00 USD annually
- USA, WA, Seattle: $148,700.00 - $201,200.00 USD annually
We could present as list.
Now ensure we don't include any boilerplate like EEO, Los Angeles County stuff, etc. Also remove duplicated lines.
We must not include job ID or company etc.
Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
- . For requirements and qualifications also list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like specific tasks, etc.
We must not include boilerplate like EEO, equal opportunity, scam warning, legal, cookie/navigation, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, About the role section: combine introductory paragraphs, "Why You Will Love It", "A day in the life", "About The Team". Keep as prose (
) maybe multiple paragraphs. We need to avoid repeating content verbatim? We can keep as is. Let's extract: Intro: "AWS operates the world's largest fleet of GPU-accelerated servers powering AI/ML workloads at cloud scale. Our team designs, builds, and operates this fleet — solving systemic hardware issues and building systems that detect and prevent recurrence so customers experience the highest quality of service. We are seeking a Senior Technical Program Manager to drive end-to-end delivery of GPU-accelerated servers across our global fleet. You will coordinate cross-functional engineering teams spanning hardware, firmware, and software, manage ODM partnerships across multiple continents, and establish closed-loop quality systems that drive continuous improvements. This role requires technical depth to translate engineering constraints into program risk, combined with program management excellence to deliver complex hardware at global scale." Why You Will Love It: "The world's most advanced frontier models are trained on the platforms you help build. Your programs launch the GPU servers that power the largest AI/ML workloads on the planet. You will see your decisions reflected in fleet reliability metrics within weeks of deployment. The team is small and high-trust — you own programs end to end from concept through production, with direct access to leadership and engineering alike." A day in the life: paragraph describing typical day. About The Team: "The Hardware Engineering AI/ML UltraServer platform team is a group of engineers and technical program managers directly responsible for launching GPU-accelerated servers into the AWS fleet. Located in Seattle, Austin, and Cupertino, we collaborate with global development teams and ODM partners to deliver next-generation AI/ML infrastructure deployed in datacenters worldwide. We move fast with small, empowered teams delivering end-to-end — from server conception through fleet-scale operations." We can combine into About the role. Now Responsibilities: "What You Will Do" plus the key job responsibilities subsections. What You Will Do: "You will own programs where the critical path runs through silicon, firmware, and software teams simultaneously. You will translate ambiguity into structure: turning a fleet telemetry signal into a corrective action plan with quantified failure rates, a customer requirement into a new platform milestone with EVT/DVT/PVT gates, or a manufacturing escape into a design change with updated validation criteria. You will drive decisions on program trade-offs — adjusting scope when qualification gates slip, balancing deployment speed against fleet risk, and determining when to accept interim mitigations instead of holding for root-cause fixes. When a large scale of GPU servers depend on your program landing on time, you are the one ensuring hardware readiness, qualification completeness, and operational handoff happen without gaps." Then key job responsibilities with subheadings; we can incorporate as list items under Responsibilities. We need to use
- for any list of duties/requirements/benefits. So we can make each responsibility as a list item. Could also keep subheadings as
? Not allowed; only headings allowed are
for sections. We cannot add other headings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use
for prose and
- for lists. We can embed subheadings as bold text within
maybe. But better to keep as list items with description. We'll create a
- with items covering each bullet.
List items:
- Define program strategy, objectives, and success criteria; influence resource allocation and priority decisions across engineering workstreams to align with organizational goals (Strategy & Mechanisms)
- Build and own mechanisms for program visibility — defining metrics, dashboards, and review cadences that enable data-driven decisions and early risk detection
- Streamline delivery processes across teams; identify and eliminate dependencies, redundant gates, or coordination overhead that slow velocity
- Facilitate requirements gathering with internal customers; develop Technical Requirements Documents (TRDs) covering server specs, rack configurations, PCIe topology, power/cooling topology, and SKU definitions (Requirements & Planning)
- Build program timelines aligned to different phases (Program Initiation, Design, Qualification, Pilot, Post-launch) with critical path analysis, risk identification with new & unique changes to the hardware, and milestone tracking for the program.
- Drive Program Initiation reviews: scope definition, preliminary annualized failure rate predictions, resource planning, supply chain long-lead identification, and RFP (Request for Proposal) issuance to ODMs
- Drive cross-functional alignment across hardware, firmware (BIOS, BMC, CPLD), software, and operations teams through design reviews, manufacturing readiness and production readiness for fleet deployment.
- Manage ODM partnerships: track EVT/DVT/PVT builds, manufacturing readiness gates, Bill of Materials (BOM) management in PLM systems, and quality checkpoints
- Identify blockers early, escalate dependencies before they impact critical path, and facilitate technical trade-off decisions across engineering workstreams.
- Communicate program status to leadership with clear reporting on milestone progress, risk posture, and mitigation plans.
- Challenge technical workstreams to surface risks early; quantify impact to schedule and reliability (annualized failure rate targets, availability SLAs) with proposed mitigations (Risk & Quality)
- Drive root cause analysis of fleet-wide hardware failures and ensure corrective actions flow back into qualification criteria and design requirements
- Define acceptance criteria, coordinate qualification testing at server and rack levels, and manage go/no-go decisions for mission-critical AI/ML workloads
- Conduct knowledge transfer and document lessons learned; ensure operational readiness including automation, monitoring, and runbook completeness for production handoff (Transition)
Also include the earlier "What You Will Do" paragraphs maybe as prose before list.
Now Requirements: Basic Qualifications list:
- Bachelor's degree in Computer Science, Electrical Engineering, Computer Engineering or a related discipline or equivalent
- Experience managing programs across cross-functional teams, building processes and coordinating release schedules
- 6+ years of technical product or program management experience, working directly with multiple engineering teams.
- 5+ years of experience driving hardware development programs (servers, racks, networking, or storage) through full product lifecycle including design, validation, manufacturing, and fleet deployment
We could also include any other basic qualifications? That's it.
Now Qualifications: Preferred Qualifications list:
- Master's degree in Computer Science, Computer Engineering, Electrical Engineering, or related fields
- Experience leading the design, automation, deployment, and support of large-scale infrastructure
- Experience facilitating discussions with senior leadership regarding technical / architectural trade-offs, best practices, and risk mitigation
- 5+ years of experience coordinating complex server programs with ODM/JDM partners across multiple geographies, managing design reviews, manufacturing readiness gates, and quality checkpoints
- 5+ years of experience working with GPU/accelerator server platforms, NPI (New Product Introduction), or hardware qualification programs across various phases (EVT, DVT, PVT)
- Experience driving root cause analysis and corrective action processes for hardware reliability issues at fleet scale
- Knowledge of server hardware development lifecycle: electrical/mechanical design, firmware, thermal/power validation, and manufacturing testing.
Now Benefits: list of benefits:
- 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) (mentioned earlier)
- Also maybe mention "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation but could be benefits.
We'll include as list.
Pay: Provide salary ranges per location:
- USA, CA, Cupertino: $171,000.00 - $231,400.00 USD annually
- USA, TX, Austin: $148,700.00 - $201,200.00 USD annually
- USA, WA, Seattle: $148,700.00 - $201,200.00 USD annually
We could present as list.
Now ensure we don't include any boilerplate like EEO, Los Angeles County stuff, etc. Also remove duplicated lines.
We must not include job ID or company etc.
Now produce HTML fragment:
- ... ...
- ... ...
- ... ...
- ... ...
About the role
... paragraphs ...
Responsibilities
Requirements
Qualifications
Benefits
Pay
- for lists. We can embed subheadings as bold text within
- for any list of duties/requirements/benefits. So we can make each responsibility as a list item. Could also keep subheadings as