Sr. Mech Product Manager-Tech, Data Center Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. First, "About the role": The description starts with "Description AWS Infrastructure Services ...". That's about the role. So we can put that in

About the role

and then

with the prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the description paragraphs. We need to extract responsibilities: "Key job responsibilities" bullet list. Responsibilities list: - Direct Liquid Cooling technology product development and validation for data center cooling - Product management of categories like Coolant Distribution Units (CDUs), Rear Door Heat Exchangers (RDHx), and Secondary Fluid Networks (SFNs) - Aligning product roadmaps for mechanical data center cooling technology to rack hardware and data center template roadmaps - Drive product strategic decisions that impact performance, cost, and schedule cross-functionally - Develop cross functional relationships that facilitate the gathering of robust and complete product requirements for mechanical solutions - Lead the development, deployment, and sustainment of Mechanical Systems for our next generation data center in a highly cross-functional environment, which includes internal customers, hardware, and software development teams. - Collaborate with teams inside and outside the organization to deliver complex cross-functional programs with high impact. Also "A day in the life" paragraph: "Our Technical Product Managers work closely..." That could be part of responsibilities or maybe separate but we can include as part of responsibilities or maybe as part of About the role? It's more description of day-to-day. Could be included under Responsibilities as prose. But we have bullet list already; we can also include a

after list for that paragraph. Now "About The Team" section: includes subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This is more about company culture, not strictly role. Could be considered "About the role"? But we already used About the role for description. Could create a section "About the Team" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit content into those. The "About The Team" content could go under About the role (maybe as additional prose) or under Requirements? Not appropriate. Probably we can incorporate into About the role as additional paragraphs. Now Basic Qualifications and Preferred Qualifications: these are qualifications. So we can have a section

Qualifications

with sub-sections? The instruction says use

for section headings. It doesn't forbid subheadings like

but we should stick to

for main sections. Within Qualifications we can have

or

• for Basic and Preferred. We need to preserve all substantive information: Basic Qualifications list: - Bachelor's degree - 5+ years of technical product or program management experience - 3+ years of designing, deploying, or operating direct-to-chip or immersion forms of rack-level liquid cooling - 5+ years of experience developing, validating, and launching new hardware products Preferred Qualifications: - 7+ years of technical product or program management experience - Master's degree Also there is EEO statement etc which we should remove (boilerplate). Also "Amazon is an equal opportunity employer..." remove. Also "If you have a disability..." remove. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. Also "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. 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." That contains Pay and Benefits info. So we need sections Pay and Benefits. Pay: The base salary ranges for various locations: list of locations with same range: USA, GA, Atlanta - 151,200.00 - 204,600.00 USD annually etc. So we can put that as a
  • list. 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. Also mention sign-on payments and RSUs? That is part of compensation but could be in Pay? The instruction: include Pay section only if posting actually states them. It does state base salary range and mentions sign-on payments and RSUs. So we can include those in Pay. Benefits: we have the list. Schedule: Not mentioned. So we should not include Schedule section. Skills: Not explicitly listed; maybe we could infer from responsibilities but not explicit. So we should not create Skills section unless there is explicit skills list. There's none. So omit Skills. Requirements: Could be same as Qualifications? The instruction separate Requirements and Qualifications. Usually Requirements are like mandatory, Qualifications are preferred. But we have Basic Qualifications (mandatory) and Preferred Qualifications (preferred). So we could map Basic Qualifications to Requirements, and Preferred Qualifications to Qualifications. Or we could combine. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which content goes where. We have Basic Qualifications (mandatory) -> Requirements. Preferred Qualifications -> Qualifications. We also have "About the role" description. We also have Responsibilities. We also have Benefits and Pay. We should not include sections with filler like "commensurate with experience". Not present. Now we need to remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines: maybe none. Now produce HTML fragment. Structure:

    About the role

    ... (description paragraph(s) )

    Responsibilities

    • ...
    ...

    A day in the life ...

    Requirements

    • Bachelor's degree
    • 5+ years of technical product or program management experience
    • 3+ years of designing, deploying, or operating direct-to-chip or immersion forms of rack-level liquid cooling
    • 5+ years of experience developing, validating, and launching new hardware products

    Qualifications

    • 7+ years of technical product or program management experience
    • Master's degree

    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

    Pay

    • USA, GA, Atlanta - $151,200.00 - $204,600.00 USD annually
    • USA, OH, COLUMBUS - $151,200.00 - $204,600.00 USD annually
    • USA, TX, Austin - $151,200.00 - $204,600.00 USD annually
    • USA, VA, Herndon - $151,200.00 - $204,600.00 USD annually
    • USA, WA, Seattle - $151,200.00 - $204,600.00 USD annually

    Sign-on payments and restricted stock units (RSUs) are included in the Amazon package; final compensation determined based on experience, qualifications, and location.

    We need to ensure we didn't repeat job title as heading. Not. We need to ensure we didn't include Job ID. Now check for any leftover boilerplate: The EEO statement removed. Also "Amazon is an equal opportunity employer..." removed. Also "If you have a disability..." removed. Also "If the country/region you’re applying in isn’t listed..." removed. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." we could keep as part of Benefits? It's a link; but it's not substantive benefit detail; it's a reference. Might be considered boilerplate? It's a link to learn more; could be considered optional. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not exactly boilerplate but could be considered navigation? It's a link to learn more; maybe we can keep it as part of Benefits as a

    but it's not a benefit itself. Safer to omit it. We already listed benefits; we can omit the link. Now check for any duplicated lines: none. Now ensure we preserved all substantive information: The description paragraph about AWS Infrastructure Services, the team, etc. We included that in About the role. Did we include the "About The Team" subsections? We omitted them; but they contain substantive info about diversity, inclusive culture, mentorship, work-life balance. Those are substantive. Should we include them? They are not covered by any of the allowed headings except maybe About the role (we could add them there). The instruction: "Prefer a few substantive sections over many thin ones." So we could merge About the Team content into About the role section as additional paragraphs. That would preserve the info. Thus About the role should include the initial description plus the About The Team paragraphs (Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). We need to keep them as prose. Let's extract those paragraphs: "About The Team Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." "Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." "Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences, inspire us to never stop embracing our uniqueness." "Mentorship & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to