Field Hardware Systems Engineer, Robotics Technical Services
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Keep substantive info.
We need to parse the posting.
Key sections:
- About the role / description: The first paragraph(s) about RTS, role description, etc. Could be "About the role" or "Overview". We'll use About the role
with paragraphs.
- Responsibilities: The bullet list under "Key job responsibilities". Also "A day in the life" maybe part of responsibilities or separate. We'll combine responsibilities.
- Requirements: Basic Qualifications and Preferred Qualifications. Could be "Requirements" or "Qualifications". We'll use Requirements
with sub-sections? But we can list basic and preferred as bullet lists.
- Skills: Not explicitly listed separate; maybe part of qualifications. Could omit if not specific.
- Benefits: The posting mentions benefits: "Amazon offers a full range of benefits..." then list: Medical, Dental, Vision Coverage, Maternity and Parental Leave Options, Paid Time Off (PTO), 401(k) Plan. Also later mentions comprehensive benefits including health insurance etc. We'll include Benefits section with bullet list.
- Pay: Salary ranges listed for multiple locations. We need to include Pay section with that info. Should we list each location? Probably yes, preserve all substantive info. Use - for each location line.
- Schedule: Not mentioned except "Up to 50% travel expected". That's not schedule. No explicit schedule like full-time, part-time. Could omit Schedule section.
- Also maybe "About The Team" section. Could be included as "About the team". But we already have About the role. Could add About the team as separate section if content specific. The posting includes "About The Team RTS Field Hardware Support Engineers (FHSE) ensure..." That's substantive. Could make a section
About the team
.
We must not include filler like "commensurate with experience". Not present.
We must not include application instructions, EEO, legal, etc. Remove those paragraphs.
We must not include duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
...
Maybe also About the team
...
Responsibilities
- Provide on-site support for new product implementations, upgrades, hardware audits, and troubleshooting for advanced robotics systems
...
Also include "A day in the life" maybe as paragraph under responsibilities? Could be separate but we can incorporate as paragraph after responsibilities? The instruction: Use for prose. Could add a paragraph describing day in the life. But we already have responsibilities list; we could add a
after list describing typical day. However we must preserve all substantive info. The "A day in the life" paragraph is substantive; we can include as a
under responsibilities section or separate section like "Typical day". But we only have allowed headings list; we could add a
Typical day
but not in list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if needed, but better to stick to those. We could incorporate day in the life into responsibilities as prose.
Thus after we add describing day in the life.
Requirements
We could split into Basic Qualifications and Preferred Qualifications as subheadings? Not allowed but we can use or
. We'll just list basic qualifications as and preferred as another with preceding maybe.
Better:
Basic Qualifications
and Preferred Qualifications
but those are not in the example list but could be okay. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those generic headings, not create many thin ones. So we should combine into Requirements section with two lists maybe preceded by paragraphs.
Thus:
Requirements
Basic Qualifications:
...
Preferred Qualifications:
...
That preserves info.
Benefits
- Medical, Dental, and Vision Coverage
- Maternity and Parental Leave Options
- Paid Time Off (PTO)
- 401(k) Plan
Maybe also mention other benefits like health insurance etc. But we can keep the list as given; the later paragraph mentions comprehensive benefits but we can include that as prose.
Add a describing that benefits vary by location etc. But we should not include filler like "can vary by location". That's substantive though. It says "Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment." That's substantive; we can include as
.
Similarly Pay section: list salary ranges per location.
We'll create
Pay
- USA, CA, SAN LEANDRO - $126,300.00 - $185,000.00 USD annually
...
We need to preserve all locations: San Leandro, Sacramento, Salinas, Stockton, Tracy, Aurora, Colorado Springs, Las Vegas.
Also note that the base salary range is listed; also mention sign-on payments and RSUs. That's substantive; we can include as after list.
Schedule: Not present; we omit.
Now ensure we removed boilerplate: application deadline, EEO, equal opportunity, legal, etc. Also remove "Application deadline: Sep 17, 2026" maybe considered metadata but not boilerplate; it's a date. Should we keep? It's substantive info about deadline. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe at top. But we could also drop it. The instruction says "fold minor metadata into a short
or drop it." So we can include a short p at beginning:
Application deadline: Sep 17, 2026
. That's fine.
Also remove "Job ID: A10503211". Drop.
Remove "Los Angeles County applicants:" etc. That's legal/EEO; drop.
Remove "Amazon is an equal opportunity employer..." etc. Drop.
Remove "If you have a disability..." etc. Drop.
Remove "If the country/region you’re applying in isn’t listed..." Drop.
Remove "Learn more about our benefits at ..." maybe keep? It's a link; could be considered boilerplate; but it's about benefits. Might be okay to keep as part of benefits? But it's a link; maybe drop as it's navigation. Safer to drop.
Remove "Our inclusive culture empowers Amazonians..." maybe keep? It's fluff but not boilerplate? Might be considered generic; but it's substantive about culture. Could keep as part of About the team? Might be okay.
But we need to preserve ALL substantive information; not invent or summarize away detail. So we should keep culture statement if it's substantive. However it's generic; but still part of posting. We'll keep as a paragraph under About the team.
Now craft HTML.
Let's write:
Application deadline: Sep 17, 2026
About the role
Are you inspired by invention? Is problem solving through teamwork in your DNA? Do you like the idea of seeing how your work impacts the bigger picture? Answer yes to any of these and you'll fit right in here at Robotics Technical Services (RTS). We are a smart team of doers who work passionately to apply advances in robotics and software to solve real-world challenges that will transform our customers' experiences in ways we can't even imagine yet. The RTS Field Support team provides critical support to internal fulfillment and transportation network customers relying on advanced robotics technology. In this role, you serve as the vital link between on-site technicians and RTS engineering teams, ensuring maximum performance of advanced robotics systems. You will launch new systems, develop preventative maintenance procedures, ensure spare part availability, proactively monitor system performance, provide troubleshooting support, and drive continuous improvement initiatives across Amazon's fulfillment network. You will establish standard operating procedures, performance metrics, and feedback mechanisms that enable the RTS team to scale effectively. Working closely with technical support teams and regional support managers, you will build a cohesive organization responsible for the safety, reliability, and performance of emerging robotics technology. This role requires independent judgment and comfort working with ambiguity in a complex, fast-paced, high-throughput environment where multi-tasking is essential.
Responsibilities
- Provide on-site support for new product implementations, upgrades, hardware audits, and troubleshooting for advanced robotics systems
- Partner with site-level RME teams to maximize advanced robotics system performance
- Identify, analyze, and resolve mechanical and system issues across the RTS product suite
- Design and implement electro-mechanical tools, fixtures, and diagnostic solutions to minimize troubleshooting and machine downtime
- Develop and implement proactive monitoring tools to measure safety, reliability, and performance of advanced robotics systems
- Create escalation processes, standard operating procedures, and preventative maintenance protocols for the RTS product suite
- Design and lead training sessions and develop training content for on-site RME teams
- Develop and implement spare parts management systems and processes
- Produce performance reports and provide "voice of the customer" feedback to development and support teams
A day in the life: Your day begins by reviewing system performance reports for your region. Perhaps the metrics dashboard revealed unusual performance at a facility or spare parts dropped below threshold at a site. You analyze metrics to identify trends and risks, developing de-risking actions for leadership's weekly business review. You troubleshoot with RME technicians via video, walking them through diagnostic procedures. On-site, you conduct hardware audits for new deployments, gathering customer feedback. Afternoons include designing tools, optimizing processes, and coordinating with regional managers on scaling strategies. Throughout, you're the critical link between field technicians and engineering teams.
Requirements
Basic Qualifications:
- 4+ years of systems engineering experience
- Experience maintaining the resilience and reliability of services by troubleshooting deployment failures, creating infrastructure as code, creating resources (alarms, metrics, IAM role credentials), infrastructure provisioning and patching hosts
- Experience in automation or monitoring frameworks, deployment or development
Preferred Qualifications:
- Experience working in 24/7 production environment
- Experience designing, implementing, and executing systems and processes to ensure the reliability and performance of products and components, including the use of tools and techniques such as failure mode and effects analysis (FMEA) and reliability testing to identify root causes of failures and develop strategies to prevent
About the team
. We must not include filler like "commensurate with experience". Not present. We must not include application instructions, EEO, legal, etc. Remove those paragraphs. We must not include duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:About the role
...
Maybe alsoAbout the team
...
Responsibilities
- Provide on-site support for new product implementations, upgrades, hardware audits, and troubleshooting for advanced robotics systems ...
for prose. Could add a paragraph describing day in the life. But we already have responsibilities list; we could add a
after list describing typical day. However we must preserve all substantive info. The "A day in the life" paragraph is substantive; we can include as a
under responsibilities section or separate section like "Typical day". But we only have allowed headings list; we could add a
Typical day
but not in list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if needed, but better to stick to those. We could incorporate day in the life into responsibilities as prose.
Thus after we add describing day in the life.
Requirements
We could split into Basic Qualifications and Preferred Qualifications as subheadings? Not allowed but we can use or
. We'll just list basic qualifications as and preferred as another with preceding maybe.
Better:
Basic Qualifications
and Preferred Qualifications
but those are not in the example list but could be okay. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those generic headings, not create many thin ones. So we should combine into Requirements section with two lists maybe preceded by paragraphs.
Thus:
Requirements
Basic Qualifications:
...
Preferred Qualifications:
...
That preserves info.
Benefits
- Medical, Dental, and Vision Coverage
- Maternity and Parental Leave Options
- Paid Time Off (PTO)
- 401(k) Plan
Maybe also mention other benefits like health insurance etc. But we can keep the list as given; the later paragraph mentions comprehensive benefits but we can include that as prose.
Add a describing that benefits vary by location etc. But we should not include filler like "can vary by location". That's substantive though. It says "Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment." That's substantive; we can include as
.
Similarly Pay section: list salary ranges per location.
We'll create
Pay
- USA, CA, SAN LEANDRO - $126,300.00 - $185,000.00 USD annually
...
We need to preserve all locations: San Leandro, Sacramento, Salinas, Stockton, Tracy, Aurora, Colorado Springs, Las Vegas.
Also note that the base salary range is listed; also mention sign-on payments and RSUs. That's substantive; we can include as after list.
Schedule: Not present; we omit.
Now ensure we removed boilerplate: application deadline, EEO, equal opportunity, legal, etc. Also remove "Application deadline: Sep 17, 2026" maybe considered metadata but not boilerplate; it's a date. Should we keep? It's substantive info about deadline. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe at top. But we could also drop it. The instruction says "fold minor metadata into a short
or drop it." So we can include a short p at beginning:
Application deadline: Sep 17, 2026
. That's fine.
Also remove "Job ID: A10503211". Drop.
Remove "Los Angeles County applicants:" etc. That's legal/EEO; drop.
Remove "Amazon is an equal opportunity employer..." etc. Drop.
Remove "If you have a disability..." etc. Drop.
Remove "If the country/region you’re applying in isn’t listed..." Drop.
Remove "Learn more about our benefits at ..." maybe keep? It's a link; could be considered boilerplate; but it's about benefits. Might be okay to keep as part of benefits? But it's a link; maybe drop as it's navigation. Safer to drop.
Remove "Our inclusive culture empowers Amazonians..." maybe keep? It's fluff but not boilerplate? Might be considered generic; but it's substantive about culture. Could keep as part of About the team? Might be okay.
But we need to preserve ALL substantive information; not invent or summarize away detail. So we should keep culture statement if it's substantive. However it's generic; but still part of posting. We'll keep as a paragraph under About the team.
Now craft HTML.
Let's write:
Application deadline: Sep 17, 2026
About the role
Are you inspired by invention? Is problem solving through teamwork in your DNA? Do you like the idea of seeing how your work impacts the bigger picture? Answer yes to any of these and you'll fit right in here at Robotics Technical Services (RTS). We are a smart team of doers who work passionately to apply advances in robotics and software to solve real-world challenges that will transform our customers' experiences in ways we can't even imagine yet. The RTS Field Support team provides critical support to internal fulfillment and transportation network customers relying on advanced robotics technology. In this role, you serve as the vital link between on-site technicians and RTS engineering teams, ensuring maximum performance of advanced robotics systems. You will launch new systems, develop preventative maintenance procedures, ensure spare part availability, proactively monitor system performance, provide troubleshooting support, and drive continuous improvement initiatives across Amazon's fulfillment network. You will establish standard operating procedures, performance metrics, and feedback mechanisms that enable the RTS team to scale effectively. Working closely with technical support teams and regional support managers, you will build a cohesive organization responsible for the safety, reliability, and performance of emerging robotics technology. This role requires independent judgment and comfort working with ambiguity in a complex, fast-paced, high-throughput environment where multi-tasking is essential.
Responsibilities
- Provide on-site support for new product implementations, upgrades, hardware audits, and troubleshooting for advanced robotics systems
- Partner with site-level RME teams to maximize advanced robotics system performance
- Identify, analyze, and resolve mechanical and system issues across the RTS product suite
- Design and implement electro-mechanical tools, fixtures, and diagnostic solutions to minimize troubleshooting and machine downtime
- Develop and implement proactive monitoring tools to measure safety, reliability, and performance of advanced robotics systems
- Create escalation processes, standard operating procedures, and preventative maintenance protocols for the RTS product suite
- Design and lead training sessions and develop training content for on-site RME teams
- Develop and implement spare parts management systems and processes
- Produce performance reports and provide "voice of the customer" feedback to development and support teams
A day in the life: Your day begins by reviewing system performance reports for your region. Perhaps the metrics dashboard revealed unusual performance at a facility or spare parts dropped below threshold at a site. You analyze metrics to identify trends and risks, developing de-risking actions for leadership's weekly business review. You troubleshoot with RME technicians via video, walking them through diagnostic procedures. On-site, you conduct hardware audits for new deployments, gathering customer feedback. Afternoons include designing tools, optimizing processes, and coordinating with regional managers on scaling strategies. Throughout, you're the critical link between field technicians and engineering teams.
Requirements
Basic Qualifications:
- 4+ years of systems engineering experience
- Experience maintaining the resilience and reliability of services by troubleshooting deployment failures, creating infrastructure as code, creating resources (alarms, metrics, IAM role credentials), infrastructure provisioning and patching hosts
- Experience in automation or monitoring frameworks, deployment or development
Preferred Qualifications:
- Experience working in 24/7 production environment
- Experience designing, implementing, and executing systems and processes to ensure the reliability and performance of products and components, including the use of tools and techniques such as failure mode and effects analysis (FMEA) and reliability testing to identify root causes of failures and develop strategies to prevent
describing day in the life.
Requirements
We could split into Basic Qualifications and Preferred Qualifications as subheadings? Not allowed but we can useor
- . We'll just list basic qualifications as
- Medical, Dental, and Vision Coverage
- Maternity and Parental Leave Options
- Paid Time Off (PTO)
- 401(k) Plan
- USA, CA, SAN LEANDRO - $126,300.00 - $185,000.00 USD annually ...
- Provide on-site support for new product implementations, upgrades, hardware audits, and troubleshooting for advanced robotics systems
- Partner with site-level RME teams to maximize advanced robotics system performance
- Identify, analyze, and resolve mechanical and system issues across the RTS product suite
- Design and implement electro-mechanical tools, fixtures, and diagnostic solutions to minimize troubleshooting and machine downtime
- Develop and implement proactive monitoring tools to measure safety, reliability, and performance of advanced robotics systems
- Create escalation processes, standard operating procedures, and preventative maintenance protocols for the RTS product suite
- Design and lead training sessions and develop training content for on-site RME teams
- Develop and implement spare parts management systems and processes
- Produce performance reports and provide "voice of the customer" feedback to development and support teams
- 4+ years of systems engineering experience
- Experience maintaining the resilience and reliability of services by troubleshooting deployment failures, creating infrastructure as code, creating resources (alarms, metrics, IAM role credentials), infrastructure provisioning and patching hosts
- Experience in automation or monitoring frameworks, deployment or development
- Experience working in 24/7 production environment
- Experience designing, implementing, and executing systems and processes to ensure the reliability and performance of products and components, including the use of tools and techniques such as failure mode and effects analysis (FMEA) and reliability testing to identify root causes of failures and develop strategies to prevent
- and preferred as another
- with preceding
maybe. Better:
Basic Qualifications
andPreferred Qualifications
but those are not in the example list but could be okay. However instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those generic headings, not create many thin ones. So we should combine into Requirements section with two lists maybe preceded by paragraphs.
Thus:
Requirements
Basic Qualifications:
- ...
Preferred Qualifications:
- ...
Benefits
describing that benefits vary by location etc. But we should not include filler like "can vary by location". That's substantive though. It says "Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment." That's substantive; we can include as
. Similarly Pay section: list salary ranges per location. We'll create
Pay
after list. Schedule: Not present; we omit. Now ensure we removed boilerplate: application deadline, EEO, equal opportunity, legal, etc. Also remove "Application deadline: Sep 17, 2026" maybe considered metadata but not boilerplate; it's a date. Should we keep? It's substantive info about deadline. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe at top. But we could also drop it. The instruction says "fold minor metadata into a short
or drop it." So we can include a short p at beginning:
Application deadline: Sep 17, 2026
. That's fine. Also remove "Job ID: A10503211". Drop. Remove "Los Angeles County applicants:" etc. That's legal/EEO; drop. Remove "Amazon is an equal opportunity employer..." etc. Drop. Remove "If you have a disability..." etc. Drop. Remove "If the country/region you’re applying in isn’t listed..." Drop. Remove "Learn more about our benefits at ..." maybe keep? It's a link; could be considered boilerplate; but it's about benefits. Might be okay to keep as part of benefits? But it's a link; maybe drop as it's navigation. Safer to drop. Remove "Our inclusive culture empowers Amazonians..." maybe keep? It's fluff but not boilerplate? Might be considered generic; but it's substantive about culture. Could keep as part of About the team? Might be okay. But we need to preserve ALL substantive information; not invent or summarize away detail. So we should keep culture statement if it's substantive. However it's generic; but still part of posting. We'll keep as a paragraph under About the team. Now craft HTML. Let's write:Application deadline: Sep 17, 2026
About the role
Are you inspired by invention? Is problem solving through teamwork in your DNA? Do you like the idea of seeing how your work impacts the bigger picture? Answer yes to any of these and you'll fit right in here at Robotics Technical Services (RTS). We are a smart team of doers who work passionately to apply advances in robotics and software to solve real-world challenges that will transform our customers' experiences in ways we can't even imagine yet. The RTS Field Support team provides critical support to internal fulfillment and transportation network customers relying on advanced robotics technology. In this role, you serve as the vital link between on-site technicians and RTS engineering teams, ensuring maximum performance of advanced robotics systems. You will launch new systems, develop preventative maintenance procedures, ensure spare part availability, proactively monitor system performance, provide troubleshooting support, and drive continuous improvement initiatives across Amazon's fulfillment network. You will establish standard operating procedures, performance metrics, and feedback mechanisms that enable the RTS team to scale effectively. Working closely with technical support teams and regional support managers, you will build a cohesive organization responsible for the safety, reliability, and performance of emerging robotics technology. This role requires independent judgment and comfort working with ambiguity in a complex, fast-paced, high-throughput environment where multi-tasking is essential.
Responsibilities
A day in the life: Your day begins by reviewing system performance reports for your region. Perhaps the metrics dashboard revealed unusual performance at a facility or spare parts dropped below threshold at a site. You analyze metrics to identify trends and risks, developing de-risking actions for leadership's weekly business review. You troubleshoot with RME technicians via video, walking them through diagnostic procedures. On-site, you conduct hardware audits for new deployments, gathering customer feedback. Afternoons include designing tools, optimizing processes, and coordinating with regional managers on scaling strategies. Throughout, you're the critical link between field technicians and engineering teams.
Requirements
Basic Qualifications:
Preferred Qualifications: