Senior Product Manager - Technical, AWS Field eXperiences
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Opening description: "Are you looking for an opportunity to create a new, global product from scratch? AWS is seeking innovative, passionate, results-oriented leader to drive product for an exciting new global product. This is a confidential strategic initiative for AWS. We are looking for an experienced product manager that thrives by creating high-bar product and engineering cultures. You will be a member of a team working on a game changing AWS offering that intersects highly scalable real-time software, front-end technologies, innovative user experience, machine learning, and analytics. You will be responsible for driving the technical product roadmap, and partnering with development and success teams to deliver new products. In this position, you’ll be an owner in innovating and delivering disruptive value to our customers, expanding customer adoption and usage growth, and raising the bar in ensuring we deliver the possible experience. We’re looking for a tenacious self-starter with a passion for and engagement products, who can serve as a strong advocate for our customers. You should have excellent capabilities, strong writing skills, ability to technically dive deep and work independently with development teams, and the desire to develop ideas independently and thrive in a fast-paced start-up environment. You must have a track record of understanding needs and delivering technology solutions to address those needs. Come join a smart, innovative team that’s obsessed with serving its customers and is having fun doing so in a start-up-like environment!"
- About Us: includes Inclusive Team Culture, Work/Life Balance, Mentorship & Career Growth. These are subsections under About Us. Should we treat them as separate sections? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow typical sections. However we can include headings like "About Us" maybe not required. But we need to preserve substantive info. Could embed those paragraphs under a generic "About the role" or "About Us". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, not exclusive. We can create sections that match content: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay". Also "About Us" could be considered "About the role"? But we have separate "About Us" describing culture. Could put under "About the role" or "About Us". Since they didn't list "About Us" as example, but we can still use for any section heading. Safer to include headings that reflect content: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay". Also maybe "Work/Life Balance", "Inclusive Team Culture", "Mentorship & Career Growth" could be subheadings but not required. We could combine them under "About Us" as a section.
We must not create sections with filler like "commensurate with experience". We have actual content for Pay: salary ranges listed for three locations. So we can include Pay section with those specifics.
Benefits: The posting mentions comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page. So we have benefits content.
Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section.
Skills: Not explicitly listed as a separate list, but there are capabilities: excellent capabilities, strong writing skills, ability to technically dive deep, work independently, desire to develop ideas independently, thrive in fast-paced start-up environment, track record of understanding needs and delivering technology solutions. Could treat as Skills or Requirements. We'll decide.
Requirements: Basic Qualifications list: Bachelor's degree, Experience owning/driving roadmap strategy and definition, Experience with feature delivery and tradeoffs of a product, Experience contributing to engineering discussions around technology decisions and strategy related to a product, Experience managing technical products or online services, Experience in representing and advocating for a variety of critical customers and stakeholders during executive-level prioritization and planning.
Preferred Qualifications: Experience in using analytical tools such as Tableau, Qlikview, QuickSight; Experience in building and driving adoption of new tools.
We could combine Requirements and Preferred Qualifications under "Requirements" and "Preferred Qualifications" maybe as separate sections. But instruction says use headings like Requirements, Qualifications, Skills. Could have "Requirements" for basic qualifications, "Preferred Qualifications" for preferred, "Skills" for capabilities.
Responsibilities: The "Key job responsibilities" section: As a Senior Product Manager-Tech on AFX ProServe Team, you will drive the product roadmap for next-generation agentic tools that revolutionize how AWS ProServe works. You'll be responsible for building and orchestrating AI agents that collaborate seamlessly to automate administrative tasks—enabling sellers to focus their time and energy on what they do best: building relationships and closing deals. Working cross-functionally with engineering, design, and field teams, you'll define product requirements, prioritize features, and deliver solutions that measurably reduce seller workload while improving sales effectiveness. Your work will directly impact thousands of sellers managing hundreds to thousands of accounts, with the goal of achieving significant time savings through intelligent automation and agentic workflows.
Also earlier description includes responsibilities like driving technical product roadmap, partnering with development and success teams to deliver new products, innovating and delivering disruptive value, expanding adoption, raising bar, etc. Could combine.
We need to preserve all substantive info, not invent or summarize away detail. So we need to include all those points.
We must not include boilerplate: EEO, legal, accommodation link, etc. Also remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About The Team About AWS Diverse Experiences" maybe duplicate? There's a line: "About The Team About AWS Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the 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." This is substantive about encouraging applicants; we should keep it. It's not boilerplate. It's about inclusive hiring. We'll keep.
Also "Company - Amazon Web Services, Inc." maybe minor metadata; we can fold into a short p or drop. Probably drop as minor metadata.
Job ID: drop.
Now produce HTML.
Structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, not exclusive. We can create sections that match content: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay". Also "About Us" could be considered "About the role"? But we have separate "About Us" describing culture. Could put under "About the role" or "About Us". Since they didn't list "About Us" as example, but we can still use for any section heading. Safer to include headings that reflect content: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay". Also maybe "Work/Life Balance", "Inclusive Team Culture", "Mentorship & Career Growth" could be subheadings but not required. We could combine them under "About Us" as a section.
We must not create sections with filler like "commensurate with experience". We have actual content for Pay: salary ranges listed for three locations. So we can include Pay section with those specifics.
Benefits: The posting mentions comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also link to benefits page. So we have benefits content.
Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section.
Skills: Not explicitly listed as a separate list, but there are capabilities: excellent capabilities, strong writing skills, ability to technically dive deep, work independently, desire to develop ideas independently, thrive in fast-paced start-up environment, track record of understanding needs and delivering technology solutions. Could treat as Skills or Requirements. We'll decide.
Requirements: Basic Qualifications list: Bachelor's degree, Experience owning/driving roadmap strategy and definition, Experience with feature delivery and tradeoffs of a product, Experience contributing to engineering discussions around technology decisions and strategy related to a product, Experience managing technical products or online services, Experience in representing and advocating for a variety of critical customers and stakeholders during executive-level prioritization and planning.
Preferred Qualifications: Experience in using analytical tools such as Tableau, Qlikview, QuickSight; Experience in building and driving adoption of new tools.
We could combine Requirements and Preferred Qualifications under "Requirements" and "Preferred Qualifications" maybe as separate sections. But instruction says use headings like Requirements, Qualifications, Skills. Could have "Requirements" for basic qualifications, "Preferred Qualifications" for preferred, "Skills" for capabilities.
Responsibilities: The "Key job responsibilities" section: As a Senior Product Manager-Tech on AFX ProServe Team, you will drive the product roadmap for next-generation agentic tools that revolutionize how AWS ProServe works. You'll be responsible for building and orchestrating AI agents that collaborate seamlessly to automate administrative tasks—enabling sellers to focus their time and energy on what they do best: building relationships and closing deals. Working cross-functionally with engineering, design, and field teams, you'll define product requirements, prioritize features, and deliver solutions that measurably reduce seller workload while improving sales effectiveness. Your work will directly impact thousands of sellers managing hundreds to thousands of accounts, with the goal of achieving significant time savings through intelligent automation and agentic workflows.
Also earlier description includes responsibilities like driving technical product roadmap, partnering with development and success teams to deliver new products, innovating and delivering disruptive value, expanding adoption, raising bar, etc. Could combine.
We need to preserve all substantive info, not invent or summarize away detail. So we need to include all those points.
We must not include boilerplate: EEO, legal, accommodation link, etc. Also remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "About The Team About AWS Diverse Experiences" maybe duplicate? There's a line: "About The Team About AWS Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the 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." This is substantive about encouraging applicants; we should keep it. It's not boilerplate. It's about inclusive hiring. We'll keep.
Also "Company - Amazon Web Services, Inc." maybe minor metadata; we can fold into a short p or drop. Probably drop as minor metadata.
Job ID: drop.
Now produce HTML.
Structure:
About the role
About the role
... (the introductory paragraph(s) describing opportunity, mission, etc.)
Maybe also include "About Us" as separate heading? But we already have About the role. Could incorporate About Us content under About the role or separate. Since they gave examples, we can add "About Us" as heading if we want. But to be safe, we can include "About the role" covering the initial description and also the "About Us" sections (Inclusive Team Culture, Work/Life Balance, Mentorship & Career Growth) as subparagraphs. ThenResponsibilities
with- items.
Then
Requirements
with- for basic qualifications.
Then
Preferred Qualifications
with- .
Then
Skills
with- for capabilities (excellent capabilities, strong writing skills, ability to technically dive deep, work independently, desire to develop ideas independently, thrive in fast-paced start-up environment, track record of understanding needs and delivering technology solutions). Could also include "strong advocacy for customers" etc.
Then
Benefits
with- for benefits.
Then
Pay
withshowing salary ranges for each location. We must not include Schedule. Make sure to preserve all specifics: mention "confidential strategic initiative for AWS", "game changing AWS offering that intersects highly scalable real-time software, front-end technologies, innovative user experience, machine learning, and analytics", "driving the technical product roadmap", "partnering with development and success teams", "owner in innovating and delivering disruptive value", "expanding customer adoption and usage growth", "raising the bar in ensuring we deliver the possible experience", "tenacious self-starter with a passion for and engagement products", "strong advocate for our customers", "excellent capabilities, strong writing skills, ability to technically dive deep and work independently with development teams, and the desire to develop ideas independently and thrive in a fast-paced start-up environment", "track record of understanding needs and delivering technology solutions to address those needs", "Come join a smart, innovative team that’s obsessed with serving its customers and is having fun doing so in a start-up-like environment!" About Us: Inclusive Team Culture: twelve employee-led affinity groups, reaching 40,000 employees in over 190 chapters globally. innovative benefit offerings, host annual and ongoing learning experiences, including Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences. Amazon’s culture of inclusion reinforced within 14 Leadership Principles. Work/Life Balance: team puts high value on work-life balance, flexibility in working hours, encourage find own balance. Mentorship & Career Growth: team dedicated to supporting new members, broad mix of experience levels, building environment that celebrates knowledge sharing and mentorship, care about career growth, assign projects to develop into better-rounded professional, enable them to take on more complex tasks. Key job responsibilities: as described. Also "About The Team About AWS Diverse Experiences" paragraph: AWS values diverse experiences, encourage candidates to apply even if not meet all qualifications, etc. We need to include that. Now produce HTML. Be careful to not include any markdown fences. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll output:
About the role
Are you looking for an opportunity to create a new, global product from scratch? AWS is seeking an innovative, passionate, results‑oriented leader to drive product for an exciting new global product. This is a confidential strategic initiative for AWS. We are looking for an experienced product manager that thrives by creating high‑bar product and engineering cultures. You will be a member of a team working on a game‑changing AWS offering that intersects highly scalable real‑time software, front‑end technologies, innovative user experience, machine learning, and analytics. You will be responsible for driving the technical product roadmap, and partnering with development and success teams to deliver new products. In this position, you’ll be an owner in innovating and delivering disruptive value to our customers, expanding customer adoption and usage growth, and raising the bar in ensuring we deliver the possible experience. We’re looking for a tenacious self‑starter with a passion for and engagement products, who can serve as a strong advocate for our customers. You should have excellent capabilities, strong writing skills, ability to technically dive deep and work independently with development teams, and the desire to develop ideas independently and thrive in a fast‑paced start‑up environment. You must have a track record of understanding needs and delivering technology solutions to address those needs. Come join a smart, innovative team that’s obsessed with serving its customers and is having fun doing so in a start‑up‑like environment!
Then About Us sections maybe asAbout Us
with subparagraphs. But the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits,
- for benefits.
Then
- for capabilities (excellent capabilities, strong writing skills, ability to technically dive deep, work independently, desire to develop ideas independently, thrive in fast-paced start-up environment, track record of understanding needs and delivering technology solutions). Could also include "strong advocacy for customers" etc.
Then
- .
Then
- for basic qualifications.
Then