Product Manager - Technical, Customer Experience and Business Trends
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to extract substantive content.
Let's parse the posting:
Description: Amazon's Customer Experience and Business Trends (CXBT) is seeking a Product Manager - Technical to directly influence the direction of AWS product through the customer experience lens. We seek a technically proficient person to join our team working with AWS leadership to deliver innovative products to customers worldwide. We are the independent internal product consultants that advise senior leaders on product direction and CX improvements. This role needs a person who is passionate to understand about the best possible customer experiences across AWS services. They stay on top of technical innovation and advances in the industry, with an eye on identifying opportunities where AWS can positively impact CX the most. This role requires dive deep into current and future customer needs, and deliver actionable insights that drive development of continuously improving AWS products, customer workflows, and features. Primary deliverables are reports with narratives that cover both the qualitative and quantitative aspects of customer use cases for specific AWS offerings which are presented to senior AWS leadership to influence them in products like AI Services, GenAI/ Agentic AI customer applications etc. to deliver the best customer experience. This role allows a person to explore different parts of AWS with a strategic vantage point. The person will excel at influencing stakeholders without formal authority, across a wide range of technical profiles and seniority levels. They are comfortable with hands-on work using cloud services, write well, and their verbal communication is concise and perceptive. They tirelessly advocate on behalf of customers and escalate immediately when they believe course correction is needed. Finally, they deliver results without compromising on quality.
Key job responsibilities: list bullet points.
A day in the life: bullet points.
About The Team: description.
Basic Qualifications: list.
Preferred Qualifications: list.
Benefits: description of benefits.
Pay: salary range.
Location: USA, WA, Seattle - salary.
We need to output sections: About the role (maybe combine description + About The Team?), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Possibly Skills not present; we can omit.
We must not repeat job title. No Job ID.
We must not include boilerplate like EEO, accommodations, etc. Remove those.
We need to preserve all substantive info: description, responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay.
We need to format as HTML fragment: use
for each section heading. Inside sections, use
for prose,
- for lists.
We need to decide how to split content.
Potential sections:
About the role
-> combine the initial description paragraph(s) and maybe "About The Team"? Actually "About The Team" is separate. Could be its own section but we could combine under About the role? The instruction says prefer a few substantive sections over many thin ones. So we could have About the role (including description and team info). Responsibilities (including key responsibilities and day in the life). Requirements (basic qualifications). Qualifications (preferred qualifications). Benefits. Pay.
We must not include schedule.
Now extract content.
Description paragraphs:
- "Amazon's Customer Experience and Business Trends (CXBT) is seeking a Product Manager - Technical to directly influence the direction of AWS product through the customer experience lens. We seek a technically proficient person to join our team working with AWS leadership to deliver innovative products to customers worldwide. We are the independent internal product consultants that advise senior leaders on product direction and CX improvements. This role needs a person who is passionate to understand about the best possible customer experiences across AWS services. They stay on top of technical innovation and advances in the industry, with an eye on identifying opportunities where AWS can positively impact CX the most. This role requires dive deep into current and future customer needs, and deliver actionable insights that drive development of continuously improving AWS products, customer workflows, and features. Primary deliverables are reports with narratives that cover both the qualitative and quantitative aspects of customer use cases for specific AWS offerings which are presented to senior AWS leadership to influence them in products like AI Services, GenAI/ Agentic AI customer applications etc. to deliver the best customer experience. This role allows a person to explore different parts of AWS with a strategic vantage point. The person will excel at influencing stakeholders without formal authority, across a wide range of technical profiles and seniority levels. They are comfortable with hands-on work using cloud services, write well, and their verbal communication is concise and perceptive. They tirelessly advocate on behalf of customers and escalate immediately when they believe course correction is needed. Finally, they deliver results without compromising on quality."
That's a lot; we can keep as prose in .
About The Team paragraph:
"Customer Experience and Business Trends (CXBT) is an organization made up of a diverse suite of functions dedicated to deeply understanding and improving customer experience, globally. We are a team of builders that develop products, services, ideas, and various ways of leveraging data to influence product and service offerings – for almost every business at Amazon – for every customer (e.g., consumers, developers, sellers/brands, employees, investors, streamers, gamers). Our team offers high quality work that drives significant customer impact with good work life harmony."
We can include that in About the role section or separate. Probably combine.
Responsibilities: list bullet points:
- Design and build proof of concept experiments that best describe the quality (performance and ease of use) of the customer experiences of AWS products and services
- Collaborate with engineering and science teams to build products and processes for efficient performance evaluations of AWS services
- Develop roadmap for evaluations by synthesizing AWS product plans, customer needs, and industry trends
- Own entire evaluation lifecycle from scoping, to execution, to delivery of findings and recommendations on CX of AWS products to AWS leadership through crisp narratives
- Continuously absorb and share knowledge about the latest product and scientific developments relevant to AWS/cloud space with a focus on AI services, and AI applications
Also "A day in the life" bullet points:
- Depending on the stage of the study that you own, you may:
- Do exploratory research to understand industry trends and customer use cases. This may involve learning new areas, talking to experts across science/ engineering/ solution architects/ sales, customers etc.
- Build the customer use case using AWS or other required cloud services to evaluate the customer experience and performance.
- Work with engineering and science teams, as needed to build new CX evaluation capabilities.
- Consolidate your insights in crisp narratives for AWS product leadership, influencing the product roadmap and helping to remove CX pain points.
- Continuous learning is always a constant.
We could merge responsibilities and day-in-life into one responsibilities section, maybe as a combined list.
Requirements (Basic Qualifications):
- 4+ years of customer-facing product development and product management, including defining, launching, and optimizing product and services experience
- Bachelor's degree
Preferred Qualifications:
- Knowledge of agile product development and life-cycle management process
- Experience leading cross-functional teams to deliver products and online services on tight deadlines
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 mention sign-on payments and restricted stock units (RSUs) as part of Amazon package.
Pay:
- 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.
- USA, WA, Seattle - 129,200.00 - 174,800.00 USD annually
We need to preserve all substantive info; we can include sign-on payments and RSUs in Benefits or Pay? The posting says: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation component; could be in Pay section.
We should not include boilerplate like EEO, accommodations, etc.
Now produce HTML.
We'll have:
About the role
... description + about the team ...
Responsibilities
- ... each bullet ...
Requirements
- ... each basic qualification ...
Qualifications
- ... each preferred qualification ...
Benefits
... benefits description ...
Pay
... salary range and sign-on/RSU info ...
We need to ensure we don't include any filler like "commensurate with experience". Not present.
Now craft the HTML.
Let's write the About the role paragraph: combine description and about the team.
Description paragraph: we can keep as is but maybe break into two for readability? The instruction says use
for prose. Could have multiple
inside section. That's fine.
We'll put first
with the description (the long paragraph). Then second
with About The Team.
Now Responsibilities: combine key responsibilities and day-in-life bullets.
We'll list all bullets.
Let's list them:
1. Design and build proof of concept experiments that best describe the quality (performance and ease of use) of the customer experiences of AWS products and services
2. Collaborate with engineering and science teams to build products and processes for efficient performance evaluations of AWS services
3. Develop roadmap for evaluations by synthesizing AWS product plans, customer needs, and industry trends
4. Own entire evaluation lifecycle from scoping, to execution, to delivery of findings and recommendations on CX of AWS products to AWS leadership through crisp narratives
5. Continuously absorb and share knowledge about the latest product and scientific developments relevant to AWS/cloud space with a focus on AI services, and AI applications
6. Do exploratory research to understand industry trends and customer use cases. This may involve learning new areas, talking to experts across science/ engineering/ solution architects/ sales, customers etc.
7. Build the customer use case using AWS or other required cloud services to evaluate the customer experience and performance.
8. Work with engineering and science teams, as needed to build new CX evaluation capabilities.
9. Consolidate your insights in crisp narratives for AWS product leadership, influencing the product roadmap and helping to remove CX pain points.
10. Continuous learning is always a constant.
We could combine 6-10 as day-in-life.
Now Requirements:
- 4+ years of customer-facing product development
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to extract substantive content. Let's parse the posting: Description: Amazon's Customer Experience and Business Trends (CXBT) is seeking a Product Manager - Technical to directly influence the direction of AWS product through the customer experience lens. We seek a technically proficient person to join our team working with AWS leadership to deliver innovative products to customers worldwide. We are the independent internal product consultants that advise senior leaders on product direction and CX improvements. This role needs a person who is passionate to understand about the best possible customer experiences across AWS services. They stay on top of technical innovation and advances in the industry, with an eye on identifying opportunities where AWS can positively impact CX the most. This role requires dive deep into current and future customer needs, and deliver actionable insights that drive development of continuously improving AWS products, customer workflows, and features. Primary deliverables are reports with narratives that cover both the qualitative and quantitative aspects of customer use cases for specific AWS offerings which are presented to senior AWS leadership to influence them in products like AI Services, GenAI/ Agentic AI customer applications etc. to deliver the best customer experience. This role allows a person to explore different parts of AWS with a strategic vantage point. The person will excel at influencing stakeholders without formal authority, across a wide range of technical profiles and seniority levels. They are comfortable with hands-on work using cloud services, write well, and their verbal communication is concise and perceptive. They tirelessly advocate on behalf of customers and escalate immediately when they believe course correction is needed. Finally, they deliver results without compromising on quality. Key job responsibilities: list bullet points. A day in the life: bullet points. About The Team: description. Basic Qualifications: list. Preferred Qualifications: list. Benefits: description of benefits. Pay: salary range. Location: USA, WA, Seattle - salary. We need to output sections: About the role (maybe combine description + About The Team?), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Possibly Skills not present; we can omit. We must not repeat job title. No Job ID. We must not include boilerplate like EEO, accommodations, etc. Remove those. We need to preserve all substantive info: description, responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay. We need to format as HTML fragment: use
for each section heading. Inside sections, use
for prose,
- for lists.
We need to decide how to split content.
Potential sections:
About the role
-> combine the initial description paragraph(s) and maybe "About The Team"? Actually "About The Team" is separate. Could be its own section but we could combine under About the role? The instruction says prefer a few substantive sections over many thin ones. So we could have About the role (including description and team info). Responsibilities (including key responsibilities and day in the life). Requirements (basic qualifications). Qualifications (preferred qualifications). Benefits. Pay. We must not include schedule. Now extract content. Description paragraphs: - "Amazon's Customer Experience and Business Trends (CXBT) is seeking a Product Manager - Technical to directly influence the direction of AWS product through the customer experience lens. We seek a technically proficient person to join our team working with AWS leadership to deliver innovative products to customers worldwide. We are the independent internal product consultants that advise senior leaders on product direction and CX improvements. This role needs a person who is passionate to understand about the best possible customer experiences across AWS services. They stay on top of technical innovation and advances in the industry, with an eye on identifying opportunities where AWS can positively impact CX the most. This role requires dive deep into current and future customer needs, and deliver actionable insights that drive development of continuously improving AWS products, customer workflows, and features. Primary deliverables are reports with narratives that cover both the qualitative and quantitative aspects of customer use cases for specific AWS offerings which are presented to senior AWS leadership to influence them in products like AI Services, GenAI/ Agentic AI customer applications etc. to deliver the best customer experience. This role allows a person to explore different parts of AWS with a strategic vantage point. The person will excel at influencing stakeholders without formal authority, across a wide range of technical profiles and seniority levels. They are comfortable with hands-on work using cloud services, write well, and their verbal communication is concise and perceptive. They tirelessly advocate on behalf of customers and escalate immediately when they believe course correction is needed. Finally, they deliver results without compromising on quality." That's a lot; we can keep as prose in. About The Team paragraph: "Customer Experience and Business Trends (CXBT) is an organization made up of a diverse suite of functions dedicated to deeply understanding and improving customer experience, globally. We are a team of builders that develop products, services, ideas, and various ways of leveraging data to influence product and service offerings – for almost every business at Amazon – for every customer (e.g., consumers, developers, sellers/brands, employees, investors, streamers, gamers). Our team offers high quality work that drives significant customer impact with good work life harmony." We can include that in About the role section or separate. Probably combine. Responsibilities: list bullet points: - Design and build proof of concept experiments that best describe the quality (performance and ease of use) of the customer experiences of AWS products and services - Collaborate with engineering and science teams to build products and processes for efficient performance evaluations of AWS services - Develop roadmap for evaluations by synthesizing AWS product plans, customer needs, and industry trends - Own entire evaluation lifecycle from scoping, to execution, to delivery of findings and recommendations on CX of AWS products to AWS leadership through crisp narratives - Continuously absorb and share knowledge about the latest product and scientific developments relevant to AWS/cloud space with a focus on AI services, and AI applications Also "A day in the life" bullet points: - Depending on the stage of the study that you own, you may: - Do exploratory research to understand industry trends and customer use cases. This may involve learning new areas, talking to experts across science/ engineering/ solution architects/ sales, customers etc. - Build the customer use case using AWS or other required cloud services to evaluate the customer experience and performance. - Work with engineering and science teams, as needed to build new CX evaluation capabilities. - Consolidate your insights in crisp narratives for AWS product leadership, influencing the product roadmap and helping to remove CX pain points. - Continuous learning is always a constant. We could merge responsibilities and day-in-life into one responsibilities section, maybe as a combined list. Requirements (Basic Qualifications): - 4+ years of customer-facing product development and product management, including defining, launching, and optimizing product and services experience - Bachelor's degree Preferred Qualifications: - Knowledge of agile product development and life-cycle management process - Experience leading cross-functional teams to deliver products and online services on tight deadlines 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 mention sign-on payments and restricted stock units (RSUs) as part of Amazon package. Pay: - 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. - USA, WA, Seattle - 129,200.00 - 174,800.00 USD annually We need to preserve all substantive info; we can include sign-on payments and RSUs in Benefits or Pay? The posting says: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation component; could be in Pay section. We should not include boilerplate like EEO, accommodations, etc. Now produce HTML. We'll have:
About the role
... description + about the team ...
Responsibilities
- ... each bullet ...
Requirements
- ... each basic qualification ...
Qualifications
- ... each preferred qualification ...
Benefits
... benefits description ...
Pay
... salary range and sign-on/RSU info ...
We need to ensure we don't include any filler like "commensurate with experience". Not present. Now craft the HTML. Let's write the About the role paragraph: combine description and about the team. Description paragraph: we can keep as is but maybe break into twofor readability? The instruction says use
for prose. Could have multiple
inside section. That's fine. We'll put first
with the description (the long paragraph). Then second
with About The Team. Now Responsibilities: combine key responsibilities and day-in-life bullets. We'll list all bullets. Let's list them: 1. Design and build proof of concept experiments that best describe the quality (performance and ease of use) of the customer experiences of AWS products and services 2. Collaborate with engineering and science teams to build products and processes for efficient performance evaluations of AWS services 3. Develop roadmap for evaluations by synthesizing AWS product plans, customer needs, and industry trends 4. Own entire evaluation lifecycle from scoping, to execution, to delivery of findings and recommendations on CX of AWS products to AWS leadership through crisp narratives 5. Continuously absorb and share knowledge about the latest product and scientific developments relevant to AWS/cloud space with a focus on AI services, and AI applications 6. Do exploratory research to understand industry trends and customer use cases. This may involve learning new areas, talking to experts across science/ engineering/ solution architects/ sales, customers etc. 7. Build the customer use case using AWS or other required cloud services to evaluate the customer experience and performance. 8. Work with engineering and science teams, as needed to build new CX evaluation capabilities. 9. Consolidate your insights in crisp narratives for AWS product leadership, influencing the product roadmap and helping to remove CX pain points. 10. Continuous learning is always a constant. We could combine 6-10 as day-in-life. Now Requirements: - 4+ years of customer-facing product development