Sr. Technical Program Manager - Storage, AWS Hardware Engineering, Hardware Engineering Services
Amazon Web Services (AWS) · Denver, CO · 3 wk ago
Project ManagementFull-time
We need to output HTML fragment with sections: About the role (maybe from description?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
First, description includes: "Application deadline: Sep 29, 2026" - metadata, can be short p.
Then description paragraphs about AWS storage fleet etc. That's about the role.
Then "Key job responsibilities" with subheadings: RFP & ODM Selection, NPI Program Delivery, Production Yield & Manufacturing Delivery, Fleet Operations & Feed-Forward, Dashboards & Mechanisms, Risk & Quality. Also "May require occasional ( for section headings. Use
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include details like bullet points for responsibilities etc. We need to avoid boilerplate: EEO, equal opportunity, accommodation links, etc. Remove those. Also remove duplicated lines, application instructions. We need to include job ID? Not as heading; fold minor metadata into short p or drop it. So we can include Application deadline and Job ID in a short p at top maybe. Let's craft. First, maybe a
for metadata: Application deadline: Sep 29, 2026. Job ID: A10559721. Then
About the role
with paragraphs: combine the initial description paragraphs and About The Team. We need to preserve all substantive info: The description about AWS operates world’s largest fleet of storage servers, team designs, builds, operates fleet, solving systemic hardware issues, building systems that detect and prevent recurrence, seeking Senior Technical Program Manager to drive end-to-end delivery of storage servers across global fleet, coordinate cross-functional engineering teams spanning hardware, firmware, software, manage ODM partnerships across multiple continents, 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. Then About The Team paragraph: The Storage Server Hardware Engineering team designs and delivers the storage platforms that power Amazon S3, EBS, and other critical AWS storage services. We own our platforms cradle-to-grave: from architecture definition through NPI, manufacturing, fleet deployment, and end-of-life. Our sustaining engineers are the backbone of fleet reliability — ensuring that deployed platforms continue to meet quality and performance targets throughout their operational life. We can put that as separateunder About the role. Now Responsibilities: Use
Responsibilities
then- with
- for each duty. Need to preserve all details from "Key job responsibilities" sections and subpoints.
Let's extract each bullet:
Under RFP & ODM Selection:
- Translate technical requirements into ODM evaluation criteria.
- Build scoring frameworks covering technical capability, manufacturing capacity, DFx maturity, automation capability, and commercial terms.
- Coordinate technical deep-dives between engineering and ODM design teams during competitive evaluation.
- Compile selection decision packages and drive decision meetings.
- Transition to NPI with requirements locked and statement of work signed.
Under NPI Program Delivery:
- Facilitate requirements gathering with internal customers; develop Technical Requirements Documents (TRDs) covering server specs, rack configurations, PCIe topology, NVMe/SSD layout, power/cooling topology, and drive interconnects.
- Build program timelines with critical path analysis, risk identification, and milestone tracking.
- Own milestone-driven gate progression: manufacturing readiness, production readiness, operational readiness review, and general availability.
- Drive cross-functional dependencies across firmware, thermal, mechanical, and silicon teams.
- Communicate program status to leadership with clear reporting on milestone progress, risk posture, and mitigation plans.
Under Production Yield & Manufacturing Delivery:
- Own manufacturing readiness gates and production yield tracking from first build through volume ramp.
- Monitor first-pass yield by test stage, drive root cause analysis on excursions, and ensure corrective actions close before yield issues compound.
- Track ODM delivery cadence, line throughput, and supply chain continuity.
Under Fleet Operations & Feed-Forward:
- Maintain fleet-level program visibility: AFR targets, unsellable resolution velocity, and component lifecycle risk.
- Own the feed-forward cadence — ensuring fleet failure patterns, manufacturing yield data, and vetting escapes translate into requirements and test content for next-generation programs.
Under Dashboards & Mechanisms:
- Build and own mechanisms for program visibility — defining metrics, dashboards, and review cadences that enable data-driven decisions and early risk detection.
- Define leading indicators: unsellable inflow/outflow rate, NPI milestone velocity, first-pass yield by test stage, and component lifecycle risk.
- Streamline delivery processes across teams; identify and eliminate dependencies, redundant gates, or coordination overhead that slow velocity.
Under Risk & Quality:
- Challenge technical workstreams to surface risks early; quantify impact to schedule and reliability (annualized failure rate targets, availability SLAs) with proposed mitigations.
- 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 storage services.
Also "May require occasional ( after list describing a day in the life. However the instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can keep the list for duties, and then a
for the day in the life prose. Thus after the
- , add a
- for any list of duties/requirements/benefits. So we can put Basic Qualifications as a list, Preferred Qualifications as another list. Could also have a
intro. We'll do:
Qualifications
Basic Qualifications:
- Bachelor's degree in Computer Science, Electrical Engineering, Computer Engineering or a related discipline or equivalent
- 6+ years of technical product or program management experience, working directly with multiple engineering teams.
- 6+ years of experience driving hardware development programs (servers, racks, networking, or storage) through full product lifecycle including design, validation, manufacturing, and fleet deployment
- Experience managing programs across cross-functional teams, building processes, and coordinating release schedules
Preferred Qualifications:
- Master’s degree in Computer Science, Electrical Engineering, or a related field
- 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 storage server platforms or NVMe/SSD infrastructure across NPI qualification 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.
- Experience driving zero-touch automation or fleet health programs for large-scale infrastructure
- Experience communicating engineering trade-offs and technical risks in business terms to leadership.
Benefits
then- with each benefit item.
List: 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, restricted stock units (RSUs). Also maybe link to learn more but we can omit link as it's not substantive? Might be considered boilerplate; we can drop.
Now Pay:
Pay
thenwith the base salary range: "USA, CO, Denver - 148,700.00 - 201,200.00 USD annually". Also mention that final compensation based on experience, qualifications, location, includes sign-on payments and RSUs (but we already put those in Benefits). Could mention that base salary range is as listed. We should not include "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." if we already put in Benefits; but we could keep it in Pay as part of total compensation. However to avoid duplication, we can mention that base
describing a day in the life: "You start the day syncing with ODM partners across time zones on build status and open engineering actions. Mid-morning, you run an engineering review connecting firmware, software, and hardware teams to unblock a qualification gate. In the afternoon, you lead the weekly feed-forward review — translating fleet failure patterns into test content requirements for the next-generation program. You end the day reviewing NPI milestone readiness and updating the production yield dashboard before the ODM delivery cadence call." Now Qualifications: We have Basic Qualifications and Preferred Qualifications. Could combine under
Qualifications
with two subsections? But we only have headings for sections; we could just list both as- items, maybe differentiate with
preceding? The instruction: Use
- for any list of duties/requirements/benefits. So we can put Basic Qualifications as a list, Preferred Qualifications as another list. Could also have a
- for any list of duties/requirements/benefits, and
- for each duty. Need to preserve all details from "Key job responsibilities" sections and subpoints.
Let's extract each bullet:
Under RFP & ODM Selection:
- Translate technical requirements into ODM evaluation criteria.
- Build scoring frameworks covering technical capability, manufacturing capacity, DFx maturity, automation capability, and commercial terms.
- Coordinate technical deep-dives between engineering and ODM design teams during competitive evaluation.
- Compile selection decision packages and drive decision meetings.
- Transition to NPI with requirements locked and statement of work signed.
Under NPI Program Delivery:
- Facilitate requirements gathering with internal customers; develop Technical Requirements Documents (TRDs) covering server specs, rack configurations, PCIe topology, NVMe/SSD layout, power/cooling topology, and drive interconnects.
- Build program timelines with critical path analysis, risk identification, and milestone tracking.
- Own milestone-driven gate progression: manufacturing readiness, production readiness, operational readiness review, and general availability.
- Drive cross-functional dependencies across firmware, thermal, mechanical, and silicon teams.
- Communicate program status to leadership with clear reporting on milestone progress, risk posture, and mitigation plans.
Under Production Yield & Manufacturing Delivery:
- Own manufacturing readiness gates and production yield tracking from first build through volume ramp.
- Monitor first-pass yield by test stage, drive root cause analysis on excursions, and ensure corrective actions close before yield issues compound.
- Track ODM delivery cadence, line throughput, and supply chain continuity.
Under Fleet Operations & Feed-Forward:
- Maintain fleet-level program visibility: AFR targets, unsellable resolution velocity, and component lifecycle risk.
- Own the feed-forward cadence — ensuring fleet failure patterns, manufacturing yield data, and vetting escapes translate into requirements and test content for next-generation programs.
Under Dashboards & Mechanisms:
- Build and own mechanisms for program visibility — defining metrics, dashboards, and review cadences that enable data-driven decisions and early risk detection.
- Define leading indicators: unsellable inflow/outflow rate, NPI milestone velocity, first-pass yield by test stage, and component lifecycle risk.
- Streamline delivery processes across teams; identify and eliminate dependencies, redundant gates, or coordination overhead that slow velocity.
Under Risk & Quality:
- Challenge technical workstreams to surface risks early; quantify impact to schedule and reliability (annualized failure rate targets, availability SLAs) with proposed mitigations.
- 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 storage services.
Also "May require occasional ( after list describing a day in the life. However the instruction: Use