Operations Reliability Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting:
- It has a description/overview section
- Key job responsibilities (detailed list)
- A day in the life (prose)
- About The Team (prose)
- Basic Qualifications (list)
- Preferred Qualifications (list)
- Pay information (base salary range for Nashville, TN)
- Benefits information (comprehensive benefits listed)
- Company and Job ID metadata
I need to structure this into appropriate sections. The headings should be semantic: About the role, Responsibilities, Qualifications (or Requirements), Benefits, Pay. The posting has both Basic and Preferred qualifications - I can combine into a Qualifications section with sub-lists or separate. The rules say use
for section headings like "Qualifications". I'll create a Qualifications section with both basic and preferred.
The posting mentions "Schedule" - not explicitly, but it's a full-time role presumably. No schedule details given, so I won't create a Schedule section.
Benefits are listed in detail, so I'll include a Benefits section.
Pay is given: base salary range for Nashville, TN. So I'll include a Pay section.
Job ID and company metadata: fold into a short
at the end or beginning? The rules say "fold minor metadata into a short
or drop it." I'll include a brief metadata paragraph at the end.
Now, I need to output only the HTML fragment. No markdown fences.
Let me draft the HTML:
About the role
Amazon is seeking an Operations Reliability Engineer to support the Amazon Logistics North America (AMZL NA) Engineering team, part of Amazon's Last Mile organization. The Last Mile team helps get customer packages from delivery stations to a customer's doorstep. This is a unique opportunity to own reliability programs and mechanisms that advance the intelligence of our last mile business. We are looking for an individual who has experience creating scalable, data-driven solutions to complex reliability and engineering problems. In this role, you will be responsible for driving proactive reliability across delivery station processes, equipment, and operations—hunting down the true causes of failures, eliminating them before they recur, and getting ahead of problems through systematic risk identification and mitigation. As a customer-obsessed leader, you will lead high-impact failure investigations, turn data into clear actions, and drive measurable improvements in uptime and performance across the network. You will design and enhance the tools, dashboards, and methodologies that enable the organization to learn from failures and prevent them at scale. Partnering with internal customers and internal/external stakeholders, you will ensure reliability improvements are executed on time and deliver lasting results. Key competencies of this position include insisting on the highest standards in root cause quality and corrective action effectiveness; analyzing and deep diving systems performance; inventing and simplifying solutions that improve equipment reliability and operational processes; and providing technical expertise to internal customers and stakeholders.
Responsibilities
- Lead Root Cause Analysis (RCA) for high-impact and recurring failures, driving deep-dive investigations to identify true root causes and ensure effective, lasting corrective actions
- Develop, maintain, and continuously improve Failure Modes and Effects Analysis (FMEA) to proactively identify risks, prioritize mitigation, and prevent future failures
- Analyze equipment and operational data to identify trends, systemic issues, and performance gaps, translating findings into actionable reliability improvements
- Lead cross-functional reliability improvements by partnering with operations, engineering, maintenance, and external vendors across multiple sites and regions
- Conduct technical deep dives into advanced technology applications, conveyor systems, and material handling integration to identify reliability risks and design-out failure modes
- Develop innovative solutions through collaboration with vendors, suppliers, and cross-functional teams
- Create and maintain BI dashboards and data visualizations to ensure transparency, predictability, and data-driven prioritization with all stakeholders
- Analyze High-Impact Event (HIE) data to identify patterns, measure reliability performance, and inform engineering investment decisions across the network
- Design and maintain automated reporting pipelines and performance dashboards (e.g., HIE trends, failure rates, uptime) that enable leadership and cross-functional teams to make data-driven decisions
- Translate complex data sets into clear, compelling narratives and recommendations for stakeholders at all levels, supporting business reviews and program prioritization
A day in the life
In this role, you will drive reliability excellence across the Last Mile network in close partnership with RME (Reliability & Maintenance Engineering) and Engineering teams. Your typical day involves analyzing failure trends and HIE data to identify recurring issues, systemic gaps, and opportunities to improve reliability and performance. You will review high-impact events and completed RCAs to ensure quality, consistency, and actionable outcomes. A key focus is supporting FMEA initiatives by helping RME and Engineering partners proactively identify risks and implement effective mitigation strategies. You will partner closely with RME teams and Engineering stakeholders to refine and improve tools, processes, and systems that support RCA and FMEA at scale. You'll facilitate planning and implementation meetings with RME leadership, Engineering program managers, and cross-functional partners to ensure alignment on objectives, expectations, and next steps—capturing and distributing comprehensive notes that drive accountability and follow-through on actions and decisions. You will collaborate with RME technicians, engineers, and regional stakeholders to align corrective actions, close the loop on reliability improvements, and strengthen how the organization learns from and prevents failures. You will also develop and enhance BI tools, automated reporting, and dashboards that surface reliability insights to RME and Engineering leaders.
About the team
At Amazon, we embody a culture of ownership, embracing unique opportunities that span from firm engineering to project execution and final customer hand-off. Our diverse, upbeat, and innovative team of engineers and program managers works tirelessly to ensure our internal customers have the capabilities to deliver on the Customer Promise. We don't just build; we consistently enhance our systems and capabilities through continuous improvement, striving for both incremental and breakthrough developments. This commitment to excellence means we're constantly raising the quality bar and are never truly satisfied. We capture lessons learned and incorporate them back into our mechanisms, perpetually improving our designs and processes with each iteration. Our approach to growth is holistic—we continually learn, develop, and expand our expertise throughout the organization, leveraging our subject matter knowledge on a global scale. Collaboration is at the heart of our ethos; we are a true team that supports, helps, and leverages each other's strengths to deliver on our business objectives.
Qualifications
Basic Qualifications
- Bachelor's degree in industrial or manufacturing engineering
- 3+ years of industrial engineer, operations engineer, manufacturing engineer, or project engineer in a manufacturing environment experience
- Experience in material handling equipment (MHE) or automation environments, or experience in reliability/maintenance environments
- Knowledge of Microsoft Excel (macros, pivots, lookups) at an advanced level
- Experience with reporting and Data Visualization tools such as Quick Sight / Tableau / Power BI or other BI packages
- Experience using data analysis to drive business decisions
Preferred Qualifications
- Knowledge of performance metrics such as OEE (Overall Equipment Effectiveness), downtime, throughput, or quality
- Experience with Six Sigma, lean manufacturing
- Master's degree or above in engineering, mechanical, operations, supply chain, business administration, or equivalent STEM field
- Experience with performance metrics such as OEE (Overall Equipment Effectiveness), downtime, throughput, or quality
- Experience developing and presenting recommendations of new metrics allowing better understanding of the performance of the business
- Experience in identifying, leading, and executing opportunities to improve, automate, standardize or simplify finance or business tools and processes
Pay
Base salary range: $68,900 - $103,400 annually (USA, TN, Nashville). Compensation includes sign-on payments and restricted stock units (RSUs). Final compensation determined based on experience, qualifications, and location.
Benefits
- Health insurance (medical, dental, vision, prescription)
- Basic Life & AD&D insurance and option for Supplemental life plans
- Employee Assistance Program (EAP)
- Mental Health Support
- Medical Advice Line
- Flexible Spending Accounts
- Adoption and Surrogacy Reimbursement coverage
- 401(k) matching
- Paid time off
- Parental leave
Company: Amazon.com Services LLC | Job ID: A10486487
I need to ensure I'm not including EEO boilerplate. The posting includes an EEO statement and accommodation link - that's boilerplate, so remove.
Also, the "Preferred Qualifications" list has a duplicate: "Experience with performance metrics such as OEE..." appears twice. I'll keep both as they appear in the source? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. But duplicate lines should be removed? The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So duplicated lines should be removed. The duplicate is exactly the same line. I'll include it once.
Also, the "Key job responsibilities" section is split into two subsections: "Reliability Engineering & Root Cause Analysis" and "Data Analytics & Business Intelligence". I've combined them into a single Responsibilities list. That's fine.
Now, check if any section is missing: The posting has "Key job responsibilities" with two sub-headings. I've captured all bullet points.
The "A day in the life" is a prose section, I'll keep as a separate section with heading "A day in the life" (but the rule says use for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "A day in the life" is not in that list, but it's a substantive section. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. I think it's okay to have "A day in the life" as an . However, the rule also says "Prefer a few substantive sections over many thin ones."
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: - It has a description/overview section - Key job responsibilities (detailed list) - A day in the life (prose) - About The Team (prose) - Basic Qualifications (list) - Preferred Qualifications (list) - Pay information (base salary range for Nashville, TN) - Benefits information (comprehensive benefits listed) - Company and Job ID metadata I need to structure this into appropriate sections. The headings should be semantic: About the role, Responsibilities, Qualifications (or Requirements), Benefits, Pay. The posting has both Basic and Preferred qualifications - I can combine into a Qualifications section with sub-lists or separate. The rules say use
for section headings like "Qualifications". I'll create a Qualifications section with both basic and preferred. The posting mentions "Schedule" - not explicitly, but it's a full-time role presumably. No schedule details given, so I won't create a Schedule section. Benefits are listed in detail, so I'll include a Benefits section. Pay is given: base salary range for Nashville, TN. So I'll include a Pay section. Job ID and company metadata: fold into a short
at the end or beginning? The rules say "fold minor metadata into a short
or drop it." I'll include a brief metadata paragraph at the end. Now, I need to output only the HTML fragment. No markdown fences. Let me draft the HTML:
About the role
Amazon is seeking an Operations Reliability Engineer to support the Amazon Logistics North America (AMZL NA) Engineering team, part of Amazon's Last Mile organization. The Last Mile team helps get customer packages from delivery stations to a customer's doorstep. This is a unique opportunity to own reliability programs and mechanisms that advance the intelligence of our last mile business. We are looking for an individual who has experience creating scalable, data-driven solutions to complex reliability and engineering problems. In this role, you will be responsible for driving proactive reliability across delivery station processes, equipment, and operations—hunting down the true causes of failures, eliminating them before they recur, and getting ahead of problems through systematic risk identification and mitigation. As a customer-obsessed leader, you will lead high-impact failure investigations, turn data into clear actions, and drive measurable improvements in uptime and performance across the network. You will design and enhance the tools, dashboards, and methodologies that enable the organization to learn from failures and prevent them at scale. Partnering with internal customers and internal/external stakeholders, you will ensure reliability improvements are executed on time and deliver lasting results. Key competencies of this position include insisting on the highest standards in root cause quality and corrective action effectiveness; analyzing and deep diving systems performance; inventing and simplifying solutions that improve equipment reliability and operational processes; and providing technical expertise to internal customers and stakeholders.
Responsibilities
- Lead Root Cause Analysis (RCA) for high-impact and recurring failures, driving deep-dive investigations to identify true root causes and ensure effective, lasting corrective actions
- Develop, maintain, and continuously improve Failure Modes and Effects Analysis (FMEA) to proactively identify risks, prioritize mitigation, and prevent future failures
- Analyze equipment and operational data to identify trends, systemic issues, and performance gaps, translating findings into actionable reliability improvements
- Lead cross-functional reliability improvements by partnering with operations, engineering, maintenance, and external vendors across multiple sites and regions
- Conduct technical deep dives into advanced technology applications, conveyor systems, and material handling integration to identify reliability risks and design-out failure modes
- Develop innovative solutions through collaboration with vendors, suppliers, and cross-functional teams
- Create and maintain BI dashboards and data visualizations to ensure transparency, predictability, and data-driven prioritization with all stakeholders
- Analyze High-Impact Event (HIE) data to identify patterns, measure reliability performance, and inform engineering investment decisions across the network
- Design and maintain automated reporting pipelines and performance dashboards (e.g., HIE trends, failure rates, uptime) that enable leadership and cross-functional teams to make data-driven decisions
- Translate complex data sets into clear, compelling narratives and recommendations for stakeholders at all levels, supporting business reviews and program prioritization
A day in the life
In this role, you will drive reliability excellence across the Last Mile network in close partnership with RME (Reliability & Maintenance Engineering) and Engineering teams. Your typical day involves analyzing failure trends and HIE data to identify recurring issues, systemic gaps, and opportunities to improve reliability and performance. You will review high-impact events and completed RCAs to ensure quality, consistency, and actionable outcomes. A key focus is supporting FMEA initiatives by helping RME and Engineering partners proactively identify risks and implement effective mitigation strategies. You will partner closely with RME teams and Engineering stakeholders to refine and improve tools, processes, and systems that support RCA and FMEA at scale. You'll facilitate planning and implementation meetings with RME leadership, Engineering program managers, and cross-functional partners to ensure alignment on objectives, expectations, and next steps—capturing and distributing comprehensive notes that drive accountability and follow-through on actions and decisions. You will collaborate with RME technicians, engineers, and regional stakeholders to align corrective actions, close the loop on reliability improvements, and strengthen how the organization learns from and prevents failures. You will also develop and enhance BI tools, automated reporting, and dashboards that surface reliability insights to RME and Engineering leaders.
About the team
At Amazon, we embody a culture of ownership, embracing unique opportunities that span from firm engineering to project execution and final customer hand-off. Our diverse, upbeat, and innovative team of engineers and program managers works tirelessly to ensure our internal customers have the capabilities to deliver on the Customer Promise. We don't just build; we consistently enhance our systems and capabilities through continuous improvement, striving for both incremental and breakthrough developments. This commitment to excellence means we're constantly raising the quality bar and are never truly satisfied. We capture lessons learned and incorporate them back into our mechanisms, perpetually improving our designs and processes with each iteration. Our approach to growth is holistic—we continually learn, develop, and expand our expertise throughout the organization, leveraging our subject matter knowledge on a global scale. Collaboration is at the heart of our ethos; we are a true team that supports, helps, and leverages each other's strengths to deliver on our business objectives.
Qualifications
Basic Qualifications
- Bachelor's degree in industrial or manufacturing engineering
- 3+ years of industrial engineer, operations engineer, manufacturing engineer, or project engineer in a manufacturing environment experience
- Experience in material handling equipment (MHE) or automation environments, or experience in reliability/maintenance environments
- Knowledge of Microsoft Excel (macros, pivots, lookups) at an advanced level
- Experience with reporting and Data Visualization tools such as Quick Sight / Tableau / Power BI or other BI packages
- Experience using data analysis to drive business decisions
Preferred Qualifications
- Knowledge of performance metrics such as OEE (Overall Equipment Effectiveness), downtime, throughput, or quality
- Experience with Six Sigma, lean manufacturing
- Master's degree or above in engineering, mechanical, operations, supply chain, business administration, or equivalent STEM field
- Experience with performance metrics such as OEE (Overall Equipment Effectiveness), downtime, throughput, or quality
- Experience developing and presenting recommendations of new metrics allowing better understanding of the performance of the business
- Experience in identifying, leading, and executing opportunities to improve, automate, standardize or simplify finance or business tools and processes
Pay
Base salary range: $68,900 - $103,400 annually (USA, TN, Nashville). Compensation includes sign-on payments and restricted stock units (RSUs). Final compensation determined based on experience, qualifications, and location.
Benefits
- Health insurance (medical, dental, vision, prescription)
- Basic Life & AD&D insurance and option for Supplemental life plans
- Employee Assistance Program (EAP)
- Mental Health Support
- Medical Advice Line
- Flexible Spending Accounts
- Adoption and Surrogacy Reimbursement coverage
- 401(k) matching
- Paid time off
- Parental leave
Company: Amazon.com Services LLC | Job ID: A10486487
I need to ensure I'm not including EEO boilerplate. The posting includes an EEO statement and accommodation link - that's boilerplate, so remove. Also, the "Preferred Qualifications" list has a duplicate: "Experience with performance metrics such as OEE..." appears twice. I'll keep both as they appear in the source? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. But duplicate lines should be removed? The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So duplicated lines should be removed. The duplicate is exactly the same line. I'll include it once. Also, the "Key job responsibilities" section is split into two subsections: "Reliability Engineering & Root Cause Analysis" and "Data Analytics & Business Intelligence". I've combined them into a single Responsibilities list. That's fine. Now, check if any section is missing: The posting has "Key job responsibilities" with two sub-headings. I've captured all bullet points. The "A day in the life" is a prose section, I'll keep as a separate section with heading "A day in the life" (but the rule says use