Sr. Mech Product Manager-Tech, DCE - Mechanical Products & Services (MPS)

We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, accommodation, etc. Must preserve all substantive info. We need to parse the description. First, description 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." That's about the role. Then: "Within Data Center Engineering, the Mechanical Products & Services (MPS) team is driving rapid innovation in Mechanical Cooling and Controls systems used by AWS. Our designs are fundamentally changing the Data Center, providing operational and financial benefits that are critical to the success of the AWS business, and its millions of customers. Our engineers solve challenging technology problems and take big bets on new concepts enabling AWS services to continue to revolutionize the industry. This role provides the opportunity to engage with and lead the Technical Product Management aspect for these advanced cloud infrastructure solutions and the exceptional people that develop them. Our PMTs work closely with key partners to innovate, create, manage, and deliver world class products to be deployed in our data centers. Our product managers work passionately to define customer requirements, development compelling product strategies to drive business value, and partner with cross functional teams and external vendors to make their strategies a reality at AWS scale! Our PMTs work closely with key partners to innovate, create, manage, and deliver holistic product solutions, and ensure products are fully production ready at launch. “Production ready at launch” addresses requirements for a product to be viable for global deployment: approved financials, technical specifications and designs, supplier sourcing and qualification, testing, operations training, and similar requirements. We develop the strategy and roadmap for product development to meet or exceed customer needs. This position requires approximately 30% travel to AWS offices, data centers, suppliers, vendors, and product validation sites. While most travel is domestic, some international travel may be required." Then "Key job responsibilities" list. Then "A day in the life" paragraph. Then "About The Team" paragraph. Then "Why AWS" paragraph. Then "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth" – these are more about culture; but they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not EEO but they are generic culture statements. Might be considered not substantive? However they are part of description; but they may be considered filler? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine culture info into About the role or maybe omit if not specific. However they are not duplicated lines; they are specific to AWS culture. Might keep as part of About the role? But we need to decide sections. We have responsibilities list: Build strategic plans for new Mechanical Solutions and methods to reach maturity for global deployment; Build trust and relationships with different stakeholders (e.g. reliability, operations, design, compliance); Work on concurrent projects, in multiple geographic zones; Understand and explain complex systems in clear and concise language; Develop Product Roadmaps; Listen to the voice of the customer to understand technical and business requirements; Work with global supplier and manufacturers to design new products; Contribute to our global body of knowledge and drive a cycle of continuous improvement at a global scale; Review, update, and approve equipment submittals. Also "A day in the life" repeats similar content: "Our team of Technical Program Managers, Product Managers – Technical, Mechanical Engineers, and Principal Engineers work closely to innovate, create, manage, and deliver holistic programs, and ensure products are fully production ready at launch. “Production ready at launch” addresses requirements for a product to be viable for global deployment: approved financials, technical specifications and designs, supplier sourcing and qualification, testing, operations training, and similar requirements. We build and execute the plan that addresses requirements in these areas, resulting in a product or solution that is production ready for global deployment." That's similar to responsibilities; could be merged. About The Team: description of team. Why AWS: description of AWS. Diverse Experiences etc: culture. We need to decide which sections to include: About the role (maybe combine initial description + Within Data Center Engineering + role opportunity). Responsibilities (list). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills (maybe not explicit; could infer from qualifications). Benefits (the paragraph about benefits). Pay (salary ranges). Schedule (travel requirement). The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to check each. - About the role: we have substantive content (description of AWS Infrastructure Services, role opportunity). Good. - Responsibilities: we have list of responsibilities. Good. - Requirements: Basic Qualifications list: 5+ years technical product or program management experience; 7+ years end to end product delivery experience; Bachelor's degree or above in Mechanical Engineering; 5+ years water treatment experience; 7+ years working directly with engineering teams. That's specific. - Qualifications: Preferred Qualifications list: 7+ years technical product or program management experience; 7+ years of product or program management, product marketing, business development or technology experience; Experience owning/driving roadmap strategy and definition; Bachelors in Chemical Enginering and experience with cooling technology and industrial water treatment. That's specific. - Skills: Not explicitly listed; could be derived but not explicit. Better to omit Skills section if no explicit skills list. - Benefits: paragraph about benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. That's specific. - Pay: salary ranges for locations: USA, TX, Austin - 151,200.00 - 204,600.00 USD annually; USA, VA, Herndon - same; USA, WA, Seattle - same. That's specific. - Schedule: travel requirement: approximately 30% travel, domestic/international. That's specific. Thus we include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not repeat job title. Not include Job ID etc. Must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines: there is duplicated sentence about "Production ready at launch" appears twice; we should keep only once? The instruction: remove duplicated lines. So we should deduplicate. We'll keep one instance. We need to output only HTML fragment, no /, no markdown. We'll use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include travel requirement under Schedule. Let's craft content. About the role: combine 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. Within Data Center Engineering, the Mechanical Products & Services (MPS) team is driving rapid innovation in Mechanical Cooling and Controls systems used by AWS. Our designs are fundamentally changing the Data Center, providing operational and financial benefits that are critical to the success of the AWS business, and its millions of customers. Our engineers solve challenging technology problems and take big bets on new concepts enabling AWS services to continue to revolutionize the industry. This role provides the opportunity to engage with and lead the Technical Product Management aspect for these advanced cloud infrastructure solutions and the exceptional people that develop them. Our PMTs work closely with key partners to innovate, create, manage, and deliver world class products to be deployed in our data centers. Our product managers work passionately to define customer requirements, develop compelling product strategies to drive business value, and partner with cross functional teams and external vendors to make their strategies a reality at AWS scale! Our PMTs work closely with key partners to innovate, create, manage, and deliver holistic product solutions, and ensure products are fully production ready at launch. “Production ready at launch” addresses requirements for a product to be viable for global deployment: approved financials, technical specifications and designs, supplier sourcing and qualification, testing, operations training, and similar requirements. We develop the strategy and roadmap for product development to meet or exceed customer needs." We need to avoid duplication: The sentence about production ready appears also later; we have it once here. Responsibilities: list items as given. We should ensure we don't duplicate responsibilities from day in the life. We'll just list the responsibilities from "Key job responsibilities". Also maybe include "Work on concurrent projects, in multiple geographic zones" etc. List: - Build strategic plans for new Mechanical Solutions and methods to reach maturity for global deployment - Build trust and relationships with different stakeholders (e.g. reliability, operations, design, compliance) - Work on concurrent projects, in multiple geographic zones - Understand and explain complex systems in clear and concise language - Develop Product Roadmaps - Listen to the voice of the customer to understand technical and business requirements - Work with global supplier and manufacturers to design new products - Contribute to our global body of knowledge and drive a cycle of continuous improvement at a global scale - Review, update, and approve equipment submittals That's it. Requirements (Basic Qualifications): list: - 5+ years of technical product or program management experience - 7+ years of end to end product delivery experience - Bachelor's degree or above in Mechanical Engineering - 5+ years water treatment experience - 7+ years working directly with engineering teams Qualifications (Preferred Qualifications): list: - 7+ years of technical product or program management experience - 7+ years of product or program management, product marketing, business development or technology experience - Experience owning/driving roadmap strategy and definition - Bachelors in Chemical Enginering and experience with cooling technology and industrial water treatment Benefits: paragraph: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." We should keep the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is part of benefits info; we can keep it as part of