Program Manager, Ops Eval, WWRR
- for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: Description At Amazon Worldwide Returns & ReCommerce, (WWR&R), we aspire to zero: zero cost of returns, zero waste, and zero defects. We are an agile, innovative organization dedicated to “making zero happen” to benefit our customers, company, and environment. We are constantly innovating to create long-term value at Amazon by investing in the future and focusing on the planet, not just on the bottom line. WWR&R includes business, product, program, data, and software engineering teams, who together manage the lifecycle of returned and damaged products. In this role, you will work closely with product managers, program managers, software engineers, and operations stakeholders to support Return Center automation innovations. You will scale solutions which are required to develop the next generation of Return Centers at Amazon. These innovations will include robotics integration and automated traceability features. You will be an expert in optimizing inventory flow to ensure accurate item condition grading, optimized recovery, and best-in-class customer experience. Key job responsibilities - Establish partnerships with hardware teams to develop integration needs - Define clear metrics and KPIs for tool performance, ensuring these indicators reflect the effectiveness of new features and overall tool utility - Construct a robust analytics framework that delivers actionable insights into tool performance and Associate behavior, enabling data-driven enhancements - Implement a framework for collaboration with regional stakeholders to address unique use cases that impact our tools, users, and customers, ensuring global initiatives accommodate local requirements while maintaining a cohesive strategy Basic Qualifications - 2+ years of program or project management experience - 3+ years of Computerized Maintenance Management System program experience - 3+ years of maintenance planner/scheduler in industrial maintenance, manufacturing, or distribution industries experience - 3+ years of advanced Microsoft Word and Excel experience - Bachelor's degree in relevant field, or 2+ years of Amazon RME (BB/3P) full time experience - Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays Preferred Qualifications - Knowledge of Lean principles and DMAIC methodology - Experience in MS Access and SQL - Experience in requirement gathering and ability to write clear and detailed requirement document - Experience using Microsoft Projects software - Experience with material handling systems (MHS) installation, operation and maintenance - Experience working in an analytical environment with cross-functional teams Then there is EEO boilerplate: "Amazon is an equal opportunity employer..." etc. Remove. Then: "If you have a disability..." remove. Then: "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." 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 location salary ranges: USA, AZ, Phoenix - 55,600.00 - 97,400.00 USD annually etc. Then: "Company - Amazon.com Services LLC - A57 Job ID: A10541234" We need to decide sections. We have description (intro) -> could be "About the role" or maybe just a paragraph. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (intro), Responsibilities (key job responsibilities), Requirements (basic qualifications?), Qualifications (maybe preferred?), Skills (maybe not separate?), Benefits (benefits described), Pay (salary ranges), Schedule (flexible schedule). However we must only include sections when posting has real, specific content for it. So we need to see if we have content for each. - About the role: we have description paragraph(s). Yes. - Responsibilities: we have bullet list under "Key job responsibilities". Yes. - Requirements: we have "Basic Qualifications". That's requirements. Yes. - Qualifications: we have "Preferred Qualifications". Could be considered Qualifications section. Yes. - Skills: Not explicitly listed as a separate section; but we could combine some skill items under Qualifications or maybe not create a Skills section if no explicit skill list. The instruction says prefer few substantive sections over many thin ones. So we could omit Skills if not distinct. - Benefits: we have description of benefits (health insurance, 401k, PTO, parental leave). Yes. - Pay: we have salary ranges for multiple locations. Yes. - Schedule: we have "Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays" under Basic Qualifications. That's schedule info. Could be a Schedule section. However we might incorporate schedule info into Requirements or maybe separate. The instruction says include a section only when posting has real, specific content for it. The schedule info is present. So we could create a Schedule section with that bullet. But note: The schedule info is currently under Basic Qualifications as a bullet. If we move it to Schedule section, we need to ensure we don't lose info. We could keep it in Requirements (Basic Qualifications) and also have Schedule? The instruction says prefer few sections; maybe we can incorporate schedule into Requirements and not create separate Schedule section. However the schedule is a specific piece of content; but we could keep it under Requirements as a bullet. That would avoid extra thin section. Similarly, Benefits: we have a paragraph describing benefits. Could be a Benefits section. Pay: we have salary ranges; could be Pay section. Thus we may have sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. We need to output HTML fragment with
headings and appropriate
or
- .
We must not repeat job title as heading. Not include Job ID.
We must drop boilerplate: EEO, accommodation, recruiting partner, learn more about benefits link? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is part of benefits description; but it's a link to benefits page. Should we keep it? It's not boilerplate; it's part of benefits info. However the instruction says remove application instructions. The link is not an instruction to apply; it's just a reference. Might be okay to keep. But we could drop the link as it's not essential substantive info? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits description; it's a reference to learn more. It's substantive? It's a URL; maybe we keep it as part of the benefits paragraph.
Similarly, the sentence "Learn more about our benefits at https://amazon.jobs/en/benefits." is part of benefits description. Keep.
Now, we need to format.
We'll produce:
About the role
At Amazon Worldwide Returns & ReCommerce, (WWR&R), we aspire to zero: zero cost of returns, zero waste, and zero defects. We are an agile, innovative organization dedicated to “making zero happen” to benefit our customers, company, and environment. We are constantly innovating to create long-term value at Amazon by investing in the future and focusing on the planet, not just on the bottom line. WWR&R includes business, product, program, data, and software engineering teams, who together manage the lifecycle of returned and damaged products. In this role, you will work closely with product managers, program managers, software engineers, and operations stakeholders to support Return Center automation innovations. You will scale solutions which are required to develop the next generation of Return Centers at Amazon. These innovations will include robotics integration and automated traceability features. You will be an expert in optimizing inventory flow to ensure accurate item condition grading, optimized recovery, and best-in-class customer experience.
Responsibilities
- Establish partnerships with hardware teams to develop integration needs
- Define clear metrics and KPIs for tool performance, ensuring these indicators reflect the effectiveness of new features and overall tool utility
- Construct a robust analytics framework that delivers actionable insights into tool performance and Associate behavior, enabling data-driven enhancements
- Implement a framework for collaboration with regional stakeholders to address unique use cases that impact our tools, users, and customers, ensuring global initiatives accommodate local requirements while maintaining a cohesive strategy
Requirements
- 2+ years of program or project management experience
- 3+ years of Computerized Maintenance Management System program experience
- 3+ years of maintenance planner/scheduler in industrial maintenance, manufacturing, or distribution industries experience
- 3+ years of advanced Microsoft Word and Excel experience
- Bachelor's degree in relevant field, or 2+ years of Amazon RME (BB/3P) full time experience
- Work a flexible schedule/shift/work area, including weekends, nights, and/or holidays
Qualifications
- Knowledge of Lean principles and DMAIC methodology
- Experience in MS Access and SQL
- Experience in requirement gathering and ability to write clear and detailed requirement document
- Experience using Microsoft Projects software
- Experience with material handling systems (MHS) installation, operation and maintenance
- Experience working in an analytical environment with cross-functional teams
Benefits
Amazon 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.
Pay
USA, AZ, Phoenix - $55,600.00 - $97,400.00 USD annually
USA, KY, Shepherdsville - $50,100.00 - $87,600.00 USD annually
USA, TX, Dallas - $55,600.00 - $97,400.00 USD annually
USA, WA, Bellevue - $80,200.00 -
- .
We must not repeat job title as heading. Not include Job ID.
We must drop boilerplate: EEO, accommodation, recruiting partner, learn more about benefits link? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is part of benefits description; but it's a link to benefits page. Should we keep it? It's not boilerplate; it's part of benefits info. However the instruction says remove application instructions. The link is not an instruction to apply; it's just a reference. Might be okay to keep. But we could drop the link as it's not essential substantive info? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is part of benefits description; it's a reference to learn more. It's substantive? It's a URL; maybe we keep it as part of the benefits paragraph.
Similarly, the sentence "Learn more about our benefits at https://amazon.jobs/en/benefits." is part of benefits description. Keep.
Now, we need to format.
We'll produce: