Sr. Product Manager Technical, Deal Tooling & Insights, Strategic Customer Engagements

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must not repeat job title as heading. No Job ID/requisition numbers as headings; can fold minor metadata into short

or drop it. We need to extract content: Description includes paragraphs about AWS GDSP team, role description, responsibilities, etc. Also "Basic Qualifications", "Preferred Qualifications". Also benefits and pay info: base salary range per location, mention sign-on payments and RSUs, comprehensive benefits list. Also work/life balance, inclusive team culture, mentorship etc. Those could be considered "About the team" or "Benefits". The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: description of role, what you will do, etc. Could be "About the role" section. - Responsibilities: list of key job responsibilities (bulleted). We have "Key job responsibilities In This Role You will ..." then bullet-like sentences. We can put as

• . - Requirements: maybe basic qualifications? Could be "Requirements" heading. - Qualifications: maybe "Preferred Qualifications". Could be separate or combine. - Skills: maybe not explicit; we could omit if no specific skills list. - Benefits: we have benefits description: comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. So we can have Benefits section. - Pay: we have base salary ranges per location. That's specific. So we can have Pay section with list of locations and ranges. - Schedule: not mentioned; maybe work/life balance but not explicit schedule. Could omit. Also we have "About The Team" with subsections: Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Could be part of "About the role" or separate "About the team". But headings list does not include About the team; but we could use About the role to cover that. However we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also include other headings if needed, but better to stick to those. Thus we need to map content: - About the role: include description of role, team context, what you will do, motivations, etc. Could combine the initial paragraphs about AWS GDSP team, role description, motivations, etc. - Responsibilities: bullet list of responsibilities. - Requirements: basic qualifications. - Qualifications: preferred qualifications. - Benefits: benefits description. - Pay: salary ranges. - Skills: maybe not present; we could omit. - Schedule: not present; omit. We must not include filler like "commensurate with experience". We have specific salary ranges, so include. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reformat. Must not drop any substantive info. That includes the details about team, work/life balance, inclusive culture, mentorship, etc. Those are substantive; we need to keep them somewhere. If we only have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, we might lose the team culture details. We could incorporate them into About the role section (since it's about the team and role). That seems acceptable. We must not repeat job title as heading. The job title is "Senior Product Manager - Technical". We must not put that as heading. We must not put Job ID as heading; we can drop it or put in a short

  . Probably drop it. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, the Los Angeles County stuff, the San Francisco Fair Chance, the disability accommodation link, the "If the country/region you’re applying in isn’t listed..." etc. Also remove the "Company - Amazon Web Services, Inc." line? That's maybe metadata but not boilerplate; could be considered minor metadata; we could drop or put in a short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop the Job ID line and maybe the Company line. We must preserve ALL substantive information; the EEO statement is not substantive? It's legal boilerplate; we can remove. The Los Angeles County specifics maybe considered legal; we can remove. The disability accommodation link maybe also boilerplate; remove. Now we need to craft HTML. Let's extract substantive paragraphs: From description: "At AWS, the Global Deal Strategy and Programs (GDSP) team drives cloud adoption and business growth through innovative pricing strategies. The organization comprises two specialized teams: Strategic Customer Engagements, which guide transformative deals with industry leaders, and Private Pricing Programs & Experiences, which scales and optimizes pricing solutions across our diverse customer base. Within GDSP, you will develop deep expertise in cloud economics, hone your strategic thinking, and directly impact AWS's market leadership while working with new technologies and global clients. Are you passionate about driving product innovation and leveraging new technologies like generative AI to transform how AWS delivers value to customers? Do you want to have a direct impact on strategic deal-making and shape the future of cloud adoption? Are you excited to blend technical expertise with product strategy to solve complex business challenges? We are seeking a highly skilled Senior Product Manager - Technical to propose and own the development of new features and functionality within our broader platform. You will work closely with stakeholders to prioritize features and capabilities that scale our ability to execute transformative deals through automation and AI-driven solutions. The ideal candidate is a strategic thinker with deep technical expertise, a passion for learning new skills and experience in cloud-based or AI-driven product management. Successful candidates must have the ability to collaborate effectively across multiple technical and non-technical business units to deliver successfully against the highest standards. The ideal candidate will have strong technical skills with business acumen and be detail-oriented with excellent analytical problem-solving skills. A keen sense of end-to-end ownership, drive, and scrappiness is a must." Then "Key job responsibilities In This Role You will own the entire lifecycle of new product feature development, from initial concept through launch and beyond, ensuring continuous improvement through data-driven iteration and stakeholder feedback. You will leverage both product management expertise and technical skills to understand complex business requirements, design innovative solutions, and develop generative AI-powered features that deliver measurable business impact. You will propose and own the development of new features within our broader platform, working closely with stakeholders to prioritize features and capabilities that scale our ability to execute transformative deals through automation and AI-driven solutions. You will lead the technical development of new product features, including hands-on contribution to development efforts, particularly in areas involving generative AI implementation and integration. You will collaborate with Data Engineers, Product Managers, and other stakeholders to define success metrics, measure product performance, and quantify the business impact of new features and capabilities You will translate complex technical concepts into clear, compelling communications for senior leadership" Note there is a missing period before "You will collaborate". We'll keep as is. Then "About The Team 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. Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud. 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 inspire us to never stop embracing our uniqueness. Mentorship and 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 help you develop into a better-rounded professional." Then "Basic Qualifications Bachelor's degree 5+ years of technical product or program management experience Experience in building and driving adoption of new tools Experience with feature delivery and tradeoffs of a product Experience contributing to engineering discussions around technology decisions and strategy related to a product" Then "Preferred Qualifications Experience in representing and advocating for a variety of critical customers and stakeholders during executive-level prioritization and planning Experience in using analytical tools, such as Tableau, Qlikview, QuickSight Experience with AWS services or other cloud offerings 3+ years of hands-on technical experience in software development, data science, or related technical field Experience in the application of GenAI technologies to drive operational efficiencies and speed to insights" Then EEO etc removed. Then "Los Angeles County applicants: ..." remove. Then "Pursuant to the Los Angeles County Fair Chance Ordinance..." remove. Then "Pursuant to the San Francisco Fair Chance Ordinance..." remove. Then "Our inclusive culture empowers Amazonians..." maybe part of earlier; but it's somewhat boilerplate; but it's about culture; could keep? It's similar to Inclusive Team Culture. Might be considered duplicate; we can drop as it's repetitive. Then "If you have a disability and need a workplace accommodation..." remove. Then "If the country/region you’re applying in isn’t listed..." remove. Then "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." Then list of locations with salary ranges. Then "Company - Amazon Web Services, Inc. Job ID: A10520489" drop. Now we need to format. We'll create sections:

  About the role

  ... combine the initial paragraphs about GDSP team, role description, motivations, etc. Also maybe include the About The Team content (Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth) as part of About the role? Could be separate but we don't have heading for About the team; we could incorporate into About the role. We need to ensure we don't lose any substantive info: The About The Team content includes description of AWS, work/life balance, inclusive culture, mentorship. We'll include that in About the role section. Thus About the role paragraph(s) will be long but okay. Then

  Responsibilities

  • ... each responsibility as separate
  • . We need to split the responsibilities into distinct items. Responsibilities sentences: 1. You will own the entire