Sr Product TPM, Amazon Infrastructure Service - Manufacturing Operation
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading (the page already shows it). No Job ID/requisition numbers as headings; fold minor metadata into short
or drop it.
We need to include a section only when posting has real specific content; never emit heading followed by filler/placeholder text.
We need to prefer few substantive sections over many thin ones.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
The posting:
Description: AWS Infrastructure Services ... (intro paragraph). Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph.
Then "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more like company culture; but they might be considered part of "About the role" or maybe we can include as "About the Team". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have responsibilities list.
We have Basic Qualifications and Preferred Qualifications.
We have Benefits description (health insurance, 401(k) matching, paid time off, parental leave). Also mention sign-on payments and RSUs.
We have Pay: "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 "USA, WA, Bellevue - 148,700.00 - 201,200.00 USD annually". So we have pay range.
We have Schedule? Not mentioned. So we should not include Schedule section.
We have Skills? Not explicit separate list; but qualifications include experience etc. Could treat qualifications as Requirements and Preferred Qualifications as maybe Skills? But we have headings: Requirements, Qualifications, Skills. We need to decide.
We could combine Basic Qualifications and Preferred Qualifications into a "Requirements" section (maybe split into Required and Preferred). But we need to follow instruction: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple of those if content exists.
We need to avoid filler. So we need to see if we have content for each.
- About the role: we have introductory paragraphs describing AWS Infrastructure Services, role purpose, team, etc. That's substantive.
- Responsibilities: we have list of responsibilities.
- Requirements: we have Basic Qualifications (Bachelor's degree, 5+ years technical program management, etc). That's requirements.
- Qualifications: maybe Preferred Qualifications? Could treat as Qualifications.
- Skills: maybe we could extract skills from responsibilities? But we might not have explicit skills list; we could skip Skills section if no specific content.
- Benefits: we have description of benefits.
- Pay: we have salary range and sign-on payments/RSUs.
- Schedule: none, so omit.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to ensure we don't repeat job title.
We need to format lists with
- .
We need to preserve all substantive info; not invent or summarize away detail.
We need to remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." lines. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep as part of benefits? It's a link; but we can keep the description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly boilerplate but could be considered navigation? It's a link to learn more; might be considered application instruction? Safer to keep the description of benefits but maybe drop the link. However we need to preserve ALL substantive information; the link is not substantive; it's a reference. Could drop.
Also remove "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's substantive about pay; keep.
Also remove "Final compensation will be determined based on factors including experience, qualifications, and location." That's substantive about pay determination; keep.
Also remove "The base salary range for this position is listed below." That's intro to pay; keep.
Also remove "USA, WA, Bellevue - 148,700.00 - 201,200.00 USD annually" keep.
Also remove "Company - Amazon Data Services, Inc." maybe minor metadata; we can fold into short
or drop. Probably drop as minor.
Also remove "Job ID: A10553667" drop.
Also remove "Description" heading? Not needed.
Now we need to craft About the role paragraph(s). The intro includes multiple paragraphs: "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion. AWS’ Infrastructure Services & Supply Chain (AIS-SC) organization works to deliver leading-edge solutions to source, build and maintain our socially responsible data center supply chains. We are a team of highly-motivated, engaged, and responsive professionals who enable the core sustainable infrastructure of AWS. We are seeking a highly effective candidate to identify, create, develop and integrate innovative technology to deliver the best operating, lowest cost infrastructure in the world."
That's a lot; we can keep as prose in
.
Then Responsibilities: list bullet points under "Key job responsibilities". We need to convert each bullet to
- .
List:
- You will lead a cross function team to deliver AWS roadmap and achieve manufacturing operation readiness for new product release in our global manufacturing locations.
- You will work on new product development program from concept phase and drive manufacturing capability and capacity enablement strategy and implementation.
- You will work with R&D and ODM to manage new product/ technology deployment risk.
- You ensure manufacturing infrastructure and manufacturing capability (automation, assembly, test) are planned ahead and enabled for NPI release.
- You drive DFx to achieve better design for manufacturability, quality, serviceability and cost.
- You define integration strategy to drive cost-effective and reliable supply chain setup.
- You manage supply chain readiness through extended team and drive critical commodity supply readiness (both quality and supply continuity).
- You'll ensure seamless teamwork and synergy among AWS, ODM and CMs on NPI program on every details from product/process qualification plan, material readiness, process/test readiness, change management, quality management and production ramp plan etc.
- Your objective is to achieve Factory Readiness Complete on time with required capability and capacity to serve customer demand.
Note: Some bullets start with "You will", "You ensure", "You drive", etc. Keep as is.
Then "A day in the life" paragraph: Could be part of About the role or Responsibilities? It's a description of typical day. Could be included in About the role as additional prose. But we already have About the role intro; we could add another paragraph after that. However we need to avoid duplication. We could incorporate it into About the role as a separate
. That's fine.
Then "About The Team" sections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These are more about company culture; could be considered part of About the role or maybe we could create a separate section like "About the Team". But headings limited to given list; we could put them under About the role as additional prose. However they are somewhat generic but still substantive. We'll include them as part of About the role.
But we need to avoid boilerplate like "Amazon is an equal opportunity employer". We'll remove that.
Now Requirements: Basic Qualifications list:
- Bachelor's degree in engineering, computer science or equivalent
- 5+ years of technical program management working directly with software engineering teams experience
- 5+ years experience managing hardware product development and new product introduction with global manufacturing scale.
- Experience on server/network/storage product test development and implementation
- Experience managing manufacturing engineering, quality, supply chain enablement, operation process improvement.
We need to keep each as
- .
Preferred Qualifications:
- 8+ years of project management disciplines including scope, schedule, budget, quality, along with risk and critical path management experience
- 8+ years of technical program management working directly with software engineering teams experience
- Experience managing manufacturing test engineering team in server/network/storage industry.
We could put these under Qualifications heading.
Now Benefits: description: "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 earlier mention "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's more compensation but could be under Pay. We'll keep benefits as described.
Pay: include base salary range, sign-on payments and RSUs, final compensation determination.
We'll create
for prose.
Now ensure we don't include filler like "commensurate with experience", "not specified", etc. We don't have those.
Now produce HTML.
Structure:
About the role
... (intro + A day in the life + About The Team content)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
.
Benefits
...
Pay
...
We must not include Schedule.
Now we need to ensure we didn't repeat any content inadvertently.
Let's craft About the role paragraph(s). We'll combine the intro paragraphs and "A day in the life" and "About The Team" sections into maybe multiple elements. It's okay to have multiple
under same heading? The instruction: Use
for prose. It didn't say only one
per section. So we can have multiple <
for prose. We must not repeat job title as heading (the page already shows it). No Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. We need to include a section only when posting has real specific content; never emit heading followed by filler/placeholder text. We need to prefer few substantive sections over many thin ones. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. The posting: Description: AWS Infrastructure Services ... (intro paragraph). Then "Key job responsibilities" list bullet points. Then "A day in the life" paragraph. Then "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more like company culture; but they might be considered part of "About the role" or maybe we can include as "About the Team". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have responsibilities list. We have Basic Qualifications and Preferred Qualifications. We have Benefits description (health insurance, 401(k) matching, paid time off, parental leave). Also mention sign-on payments and RSUs. We have Pay: "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 "USA, WA, Bellevue - 148,700.00 - 201,200.00 USD annually". So we have pay range. We have Schedule? Not mentioned. So we should not include Schedule section. We have Skills? Not explicit separate list; but qualifications include experience etc. Could treat qualifications as Requirements and Preferred Qualifications as maybe Skills? But we have headings: Requirements, Qualifications, Skills. We need to decide. We could combine Basic Qualifications and Preferred Qualifications into a "Requirements" section (maybe split into Required and Preferred). But we need to follow instruction: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple of those if content exists. We need to avoid filler. So we need to see if we have content for each. - About the role: we have introductory paragraphs describing AWS Infrastructure Services, role purpose, team, etc. That's substantive. - Responsibilities: we have list of responsibilities. - Requirements: we have Basic Qualifications (Bachelor's degree, 5+ years technical program management, etc). That's requirements. - Qualifications: maybe Preferred Qualifications? Could treat as Qualifications. - Skills: maybe we could extract skills from responsibilities? But we might not have explicit skills list; we could skip Skills section if no specific content. - Benefits: we have description of benefits. - Pay: we have salary range and sign-on payments/RSUs. - Schedule: none, so omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't repeat job title. We need to format lists with
- .
We need to preserve all substantive info; not invent or summarize away detail.
We need to remove boilerplate: EEO statement, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." lines. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe keep as part of benefits? It's a link; but we can keep the description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly boilerplate but could be considered navigation? It's a link to learn more; might be considered application instruction? Safer to keep the description of benefits but maybe drop the link. However we need to preserve ALL substantive information; the link is not substantive; it's a reference. Could drop.
Also remove "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's substantive about pay; keep.
Also remove "Final compensation will be determined based on factors including experience, qualifications, and location." That's substantive about pay determination; keep.
Also remove "The base salary range for this position is listed below." That's intro to pay; keep.
Also remove "USA, WA, Bellevue - 148,700.00 - 201,200.00 USD annually" keep.
Also remove "Company - Amazon Data Services, Inc." maybe minor metadata; we can fold into short
or drop. Probably drop as minor. Also remove "Job ID: A10553667" drop. Also remove "Description" heading? Not needed. Now we need to craft About the role paragraph(s). The intro includes multiple paragraphs: "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion. AWS’ Infrastructure Services & Supply Chain (AIS-SC) organization works to deliver leading-edge solutions to source, build and maintain our socially responsible data center supply chains. We are a team of highly-motivated, engaged, and responsive professionals who enable the core sustainable infrastructure of AWS. We are seeking a highly effective candidate to identify, create, develop and integrate innovative technology to deliver the best operating, lowest cost infrastructure in the world." That's a lot; we can keep as prose in
. Then Responsibilities: list bullet points under "Key job responsibilities". We need to convert each bullet to
- .
List:
- You will lead a cross function team to deliver AWS roadmap and achieve manufacturing operation readiness for new product release in our global manufacturing locations.
- You will work on new product development program from concept phase and drive manufacturing capability and capacity enablement strategy and implementation.
- You will work with R&D and ODM to manage new product/ technology deployment risk.
- You ensure manufacturing infrastructure and manufacturing capability (automation, assembly, test) are planned ahead and enabled for NPI release.
- You drive DFx to achieve better design for manufacturability, quality, serviceability and cost.
- You define integration strategy to drive cost-effective and reliable supply chain setup.
- You manage supply chain readiness through extended team and drive critical commodity supply readiness (both quality and supply continuity).
- You'll ensure seamless teamwork and synergy among AWS, ODM and CMs on NPI program on every details from product/process qualification plan, material readiness, process/test readiness, change management, quality management and production ramp plan etc.
- Your objective is to achieve Factory Readiness Complete on time with required capability and capacity to serve customer demand.
Note: Some bullets start with "You will", "You ensure", "You drive", etc. Keep as is.
Then "A day in the life" paragraph: Could be part of About the role or Responsibilities? It's a description of typical day. Could be included in About the role as additional prose. But we already have About the role intro; we could add another paragraph after that. However we need to avoid duplication. We could incorporate it into About the role as a separate
. That's fine. Then "About The Team" sections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These are more about company culture; could be considered part of About the role or maybe we could create a separate section like "About the Team". But headings limited to given list; we could put them under About the role as additional prose. However they are somewhat generic but still substantive. We'll include them as part of About the role. But we need to avoid boilerplate like "Amazon is an equal opportunity employer". We'll remove that. Now Requirements: Basic Qualifications list: - Bachelor's degree in engineering, computer science or equivalent - 5+ years of technical program management working directly with software engineering teams experience - 5+ years experience managing hardware product development and new product introduction with global manufacturing scale. - Experience on server/network/storage product test development and implementation - Experience managing manufacturing engineering, quality, supply chain enablement, operation process improvement. We need to keep each as
- .
Preferred Qualifications:
- 8+ years of project management disciplines including scope, schedule, budget, quality, along with risk and critical path management experience
- 8+ years of technical program management working directly with software engineering teams experience
- Experience managing manufacturing test engineering team in server/network/storage industry.
We could put these under Qualifications heading.
Now Benefits: description: "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 earlier mention "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's more compensation but could be under Pay. We'll keep benefits as described.
Pay: include base salary range, sign-on payments and RSUs, final compensation determination.
We'll create
for prose. Now ensure we don't include filler like "commensurate with experience", "not specified", etc. We don't have those. Now produce HTML. Structure:
About the role
... (intro + A day in the life + About The Team content)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ... .
Benefits
...
Pay
...
We must not include Schedule. Now we need to ensure we didn't repeat any content inadvertently. Let's craft About the role paragraph(s). We'll combine the intro paragraphs and "A day in the life" and "About The Team" sections into maybe multipleelements. It's okay to have multiple
under same heading? The instruction: Use
for prose. It didn't say only one
per section. So we can have multiple <