Sr. Product Manager, Technical, Amazon Connect Customer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not put Job ID as heading. Remove boilerplate, EEO, etc. Preserve all substantive info. Only include sections when posting has real specific content. Avoid filler like "commensurate with experience". We need to extract content.
Let's parse description.
First paragraph: "Description As part of the AWS Applied AI Solutions organization, ..." This is about the role? It's description of organization and vision. Could be "About the role" or maybe "About the team"? There's later "About The Team" section. So we can treat initial description as "About the role". We'll put that in
.
Then "We are seeking a Senior Product Manager, Technical to help drive the product vision and execution for Amazon Connect Customer Step-by-Step Guides (Guides). In this role, you will own the product strategy and roadmap for Guides, and shape how businesses lead agents and end-customers through the steps that resolve each interaction. You will own how businesses build and refine guided experiences across agent-assisted and self-service use cases, and how those workflows evolve from static sequences into dynamically assembled interactions powered by AI. This role suits a builder who wants to set the direction for a growing product, not just execute against a defined one."
That's also role description.
Then "Key job responsibilities" bullet list.
We need to extract responsibilities as list items.
Responsibilities list:
- Own the product roadmap and execution for Step-by-Step Guides, setting the direction for your product and driving measurable usage growth and adoption across agent-assisted and self-service use cases.
- Own the guided workflows at the core of Guides, from creation and template management to AI-assisted assembly, so businesses make each interaction faster and more consistent.
- Define how businesses measure guided experiences, identifying what drives agent performance and self-service resolution, and closing the loop so each interaction improves the next.
- Lead the evolution of Guides from deterministic workflows into dynamically assembled experiences, partnering with Interactive AI teams while managing the tension between an AI-powered future and today's product needs.
- Make it easier for builders to create and customize guided experiences using Views, so businesses implement and scale Guides across their contact centers without specialized development.
- Partner with go-to-market teams to develop positioning that accelerates adoption, builds and nurtures the sales pipeline, and drives feature adoption across customer organizations.
- Work backwards from customers to identify and prioritize the right problems, then partner with engineering, design, and science to deliver.
- In this role, you will be part of a startup-like culture with the stability of an established industry leader.
- You will build software that materially improves people's lives.
Also "A day in the life" paragraph: could be part of responsibilities or maybe "About the role"? It's more about personal traits. Could be placed under "About the role" or maybe "Skills"? But we have a separate "Skills" section maybe not needed. The instructions: Use sections only when posting has real specific content. We have content for Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay (salary ranges), maybe Schedule not present. Also "About The Team" section with subpoints: Diverse Experiences, Why AWS, Inclusive Team Culture, Mentorship and Career Growth. Those could be under "About the team" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". However we could incorporate that info into "About the role" or maybe "Qualifications"? But better to put under "About the role" as additional description. The instructions: Use headings only for those listed. So we cannot create a heading for About the team. We must embed that content elsewhere, maybe under About the role as prose.
We also have "Basic Qualifications" and "Preferred Qualifications". Those map to Requirements and Qualifications? The headings: Requirements, Qualifications. Likely Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. We'll follow that.
Skills: Not explicitly listed; we could omit Skills section if no specific skills listed besides those in qualifications. Could combine into Requirements/Qualifications.
Benefits: The posting mentions benefits: "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: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So we have benefits content.
Pay: Salary ranges for locations: USA, NY, New York - 167,400.00 - 226,500.00 USD annually; USA, WA, Seattle - 152,200.00 - 205,900.00 USD annually. Also mention base salary range listed below. So we have Pay.
Schedule: Not mentioned. So we omit Schedule section.
Now we need to strip boilerplate: EEO, accommodation link, etc. Also remove "Company - Amazon Development Center U.S., Inc. Job ID: A10551601". 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." Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc.
Also remove "Why AWS" etc? That's part of About The Team, but we can keep as prose under About the role. However "Why AWS" includes description of AWS; that's substantive. Keep.
Now structure:
About the role
... (combined description from initial paragraphs plus About The Team subpoints maybe).
Responsibilities
- ... each responsibility.
Requirements
- ... each basic qualification.
Qualifications
- ... each preferred qualification.
Benefits
for prose. Do not repeat job title as heading. Do not put Job ID as heading. Remove boilerplate, EEO, etc. Preserve all substantive info. Only include sections when posting has real specific content. Avoid filler like "commensurate with experience". We need to extract content. Let's parse description. First paragraph: "Description As part of the AWS Applied AI Solutions organization, ..." This is about the role? It's description of organization and vision. Could be "About the role" or maybe "About the team"? There's later "About The Team" section. So we can treat initial description as "About the role". We'll put that in
. Then "We are seeking a Senior Product Manager, Technical to help drive the product vision and execution for Amazon Connect Customer Step-by-Step Guides (Guides). In this role, you will own the product strategy and roadmap for Guides, and shape how businesses lead agents and end-customers through the steps that resolve each interaction. You will own how businesses build and refine guided experiences across agent-assisted and self-service use cases, and how those workflows evolve from static sequences into dynamically assembled interactions powered by AI. This role suits a builder who wants to set the direction for a growing product, not just execute against a defined one." That's also role description. Then "Key job responsibilities" bullet list. We need to extract responsibilities as list items. Responsibilities list: - Own the product roadmap and execution for Step-by-Step Guides, setting the direction for your product and driving measurable usage growth and adoption across agent-assisted and self-service use cases. - Own the guided workflows at the core of Guides, from creation and template management to AI-assisted assembly, so businesses make each interaction faster and more consistent. - Define how businesses measure guided experiences, identifying what drives agent performance and self-service resolution, and closing the loop so each interaction improves the next. - Lead the evolution of Guides from deterministic workflows into dynamically assembled experiences, partnering with Interactive AI teams while managing the tension between an AI-powered future and today's product needs. - Make it easier for builders to create and customize guided experiences using Views, so businesses implement and scale Guides across their contact centers without specialized development. - Partner with go-to-market teams to develop positioning that accelerates adoption, builds and nurtures the sales pipeline, and drives feature adoption across customer organizations. - Work backwards from customers to identify and prioritize the right problems, then partner with engineering, design, and science to deliver. - In this role, you will be part of a startup-like culture with the stability of an established industry leader. - You will build software that materially improves people's lives. Also "A day in the life" paragraph: could be part of responsibilities or maybe "About the role"? It's more about personal traits. Could be placed under "About the role" or maybe "Skills"? But we have a separate "Skills" section maybe not needed. The instructions: Use sections only when posting has real specific content. We have content for Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay (salary ranges), maybe Schedule not present. Also "About The Team" section with subpoints: Diverse Experiences, Why AWS, Inclusive Team Culture, Mentorship and Career Growth. Those could be under "About the team" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the team". However we could incorporate that info into "About the role" or maybe "Qualifications"? But better to put under "About the role" as additional description. The instructions: Use headings only for those listed. So we cannot create a heading for About the team. We must embed that content elsewhere, maybe under About the role as prose. We also have "Basic Qualifications" and "Preferred Qualifications". Those map to Requirements and Qualifications? The headings: Requirements, Qualifications. Likely Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. We'll follow that. Skills: Not explicitly listed; we could omit Skills section if no specific skills listed besides those in qualifications. Could combine into Requirements/Qualifications. Benefits: The posting mentions benefits: "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: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So we have benefits content. Pay: Salary ranges for locations: USA, NY, New York - 167,400.00 - 226,500.00 USD annually; USA, WA, Seattle - 152,200.00 - 205,900.00 USD annually. Also mention base salary range listed below. So we have Pay. Schedule: Not mentioned. So we omit Schedule section. Now we need to strip boilerplate: EEO, accommodation link, etc. Also remove "Company - Amazon Development Center U.S., Inc. Job ID: A10551601". 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." Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "Why AWS" etc? That's part of About The Team, but we can keep as prose under About the role. However "Why AWS" includes description of AWS; that's substantive. Keep. Now structure:
About the role
... (combined description from initial paragraphs plus About The Team subpoints maybe).
Responsibilities
- ... each responsibility.
Requirements
- ... each basic qualification.
Qualifications
- ... each preferred qualification. Benefits
- ... benefits items.
Pay
... salary ranges.
We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract exact text. About the role content: Start: "Description As part of the AWS Applied AI Solutions organization, our vision is to provide business applications leveraging Amazon's unique experience and expertise, that are used by millions of companies worldwide to manage day-to-day operations. We will accomplish this by accelerating our customers' success through delivery of intuitive and differentiated technology solutions which solve enduring business challenges. We blend vision with curiosity and Amazon's real-world experience to build opinionated, turnkey solutions. Where customers prefer to buy over build, we become their trusted partner with solutions that are no-brainers to buy and easy to use. Amazon Connect is an AI-powered customer experience solution that enables superior outcomes at a lower cost. Since its 2017 public launch, Amazon Connect has become an AI leader, transforming how organizations of all types interact with their customers. Amazon Connect Customer is an easy-to-use cloud customer experience solution that helps companies of any size deliver exceptional customer outcomes at lower cost. Connect Customer has evolved into a unified customer engagement application that seamlessly blends human expertise with AI-driven interactions, supporting billions of customer engagements globally. We are seeking a Senior Product Manager, Technical to help drive the product vision and execution for Amazon Connect Customer Step-by-Step Guides (Guides). In this role, you will own the product strategy and roadmap for Guides, and shape how businesses lead agents and end-customers through the steps that resolve each interaction. You will own how businesses build and refine guided experiences across agent-assisted and self-service use cases, and how those workflows evolve from static sequences into dynamically assembled interactions powered by AI. This role suits a builder who wants to set the direction for a growing product, not just execute against a defined one." Then "A day in the life You like working directly with all levels and types of customers, from CxO to individual contributors and engineers to business people, to solve their most complicated problems through software. You enjoy being on a team that fosters a collaborative environment as we work towards common goals. You are a passionate learner and are motivated to take on new and, oftentimes, ambiguous challenges. You are able to lead and partner with a variety of stakeholders to identify and prioritize the right problems to solve and solutions to develop. You are comfortable and thrive in a fast-paced environment." Then "About The Team Diverse Experiences Amazon 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 and AmazeCon conferences, 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." We can combine all that into About the role paragraph(s). Might be long but okay. Now Responsibilities list: we have bullet points above. Need to ensure each is a separate