Hardware Support Engineer, Robotics Technical Services
Amazon · San Antonio, TX · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as 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. Include a section ONLY when 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Description (intro) – we can treat as "About the role" maybe. The posting starts with description about RTS. We'll put that under
About the role
with paragraphs.
- Responsibilities: "Key job responsibilities" list bullet points. Also "A day in the life" maybe part of responsibilities but we can include as prose.
- Requirements: "Basic Qualifications" and "Preferred Qualifications". Could combine as Requirements/Qualifications. Use Requirements
maybe separate Basic and Preferred? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate if needed. But we can combine Basic and Preferred under Requirements or Qualifications. Let's decide: Use Requirements for basic qualifications, Qualifications for preferred? Or we could have Requirements (basic) and Qualifications (preferred). We'll include both.
- Skills: maybe not explicit separate list; but we have knowledge of networking fundamentals, Six Sigma tools, etc. Could be under Skills.
- Benefits: The posting mentions benefits: "Amazon offers a full range of benefits... Benefits can vary... The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan". Also later: "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." So we have benefits details. So we can include Benefits section.
- Pay: The posting includes "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." Then lists locations with salary ranges: USA, TX, Dallas - 82,400.00 - 144,100.00 USD annually etc. So we have Pay info. So we should include Pay section.
- Schedule: Not explicitly mentioned. There's "Up to 50% travel expected". That's not schedule. No mention of work hours, shift, etc. So we should NOT create Schedule section because no specific content.
- Also we have "About The Team" section. Could be part of About the role or separate. Could treat as About the role. We'll include that content under About the role.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines, application instructions like "If you are not sure that every qualification..." etc. That's application encouragement; maybe we should remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So lines like "If you are not sure that every qualification on the list above describes you exactly, we'd still love to hear from you! At Amazon, we value people with unique backgrounds, experiences, and skillsets. If you’re passionate about this role and want to make an impact on a global scale, please apply!" That's application instruction; remove. Also "About The Team" maybe not boilerplate; it's substantive. Keep.
Also "Amazon is an equal opportunity employer..." remove.
Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove.
Also "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe part of benefits but it's a link; could keep? It's more like application instruction; maybe remove.
We need to preserve all substantive information: responsibilities list, qualifications, benefits, pay, travel expectation, etc.
We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to avoid creating sections with filler.
Let's outline:
About the role
... intro paragraph(s) ... plus About The Team content maybe.
Responsibilities
- ... each bullet from Key job responsibilities ...
Maybe also include "A day in the life" as prose under responsibilities? Could add a after list.
Requirements
Basic Qualifications:
- ... each basic qualification ...
Qualifications
Preferred Qualifications:
- ... each preferred qualification ...
Skills
Maybe we can embed skills within Requirements/Qualifications; but we have separate list of skills like networking fundamentals, Six Sigma tools, etc. Those are already in Basic Qualifications. Could treat them as part of Requirements. So maybe we don't need separate Skills section.
Benefits
- ... list benefits ...
Pay
Base salary range (locations) ...
Maybe also mention sign-on payments and RSUs.
We need to ensure we don't create sections with placeholder text.
Now let's extract content.
Intro description:
"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."
That's the description.
Then "About The Team" paragraph:
"About The Team RTS Field Hardware Support Engineers (FHSE) ensure that our customers—site Reliability and Maintenance Engineers—are equipped to independently maintain Amazon Robotics technologies. Our team achieves this by identifying deficiencies, communicating risk, and proposing mitigation strategies. Our hands-on approach to testing, troubleshooting, and investigating puts us in the shoes of operators and technicians in the field. We work backwards from these insights to satisfy engineering requirements, partnering with safety, hardware, software, and cross-functional support teams."
We can combine into About the role.
Now Responsibilities list (Key job 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
- Up to 50% travel expected
Note: "Up to 50% travel expected" is a responsibility/travel expectation; we can include as bullet.
Now "A day in the life" paragraph:
"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."
We can include as prose after responsibilities list.
Now Basic Qualifications:
- Bachelor's degree or above in Mechanical, Electrical, Industrial Engineering, or related STEM field
- Knowledge of networking fundamentals
- Experience working in a 24/7 production environment
- Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred
- Knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems
- Experience in Linux systems administration and/or development
Note: "Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred" is phrased as preferred but it's under Basic Qualifications. We'll keep as is.
Now Preferred Qualifications:
- 2+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience
- 1+ years of building scripts, tooling, and automation for large-scale computing environments experience
- Experience in site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration
- Experience in network capture and systems troubleshooting
- Experience building scripts, tooling, and automation for large-scale computing environments
Note there is some duplication; we keep as given.
Now Benefits:
First benefits paragraph: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. 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. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan"
Second benefits paragraph: "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."
We should combine into a list, avoiding duplication. Let's extract unique benefits
for prose. Do NOT repeat job title as 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. Include a section ONLY when 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Description (intro) – we can treat as "About the role" maybe. The posting starts with description about RTS. We'll put that under
About the role
with paragraphs. - Responsibilities: "Key job responsibilities" list bullet points. Also "A day in the life" maybe part of responsibilities but we can include as prose. - Requirements: "Basic Qualifications" and "Preferred Qualifications". Could combine as Requirements/Qualifications. UseRequirements
maybe separate Basic and Preferred? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate if needed. But we can combine Basic and Preferred under Requirements or Qualifications. Let's decide: Use Requirements for basic qualifications, Qualifications for preferred? Or we could have Requirements (basic) and Qualifications (preferred). We'll include both. - Skills: maybe not explicit separate list; but we have knowledge of networking fundamentals, Six Sigma tools, etc. Could be under Skills. - Benefits: The posting mentions benefits: "Amazon offers a full range of benefits... Benefits can vary... The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan". Also later: "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." So we have benefits details. So we can include Benefits section. - Pay: The posting includes "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." Then lists locations with salary ranges: USA, TX, Dallas - 82,400.00 - 144,100.00 USD annually etc. So we have Pay info. So we should include Pay section. - Schedule: Not explicitly mentioned. There's "Up to 50% travel expected". That's not schedule. No mention of work hours, shift, etc. So we should NOT create Schedule section because no specific content. - Also we have "About The Team" section. Could be part of About the role or separate. Could treat as About the role. We'll include that content under About the role. We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines, application instructions like "If you are not sure that every qualification..." etc. That's application encouragement; maybe we should remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So lines like "If you are not sure that every qualification on the list above describes you exactly, we'd still love to hear from you! At Amazon, we value people with unique backgrounds, experiences, and skillsets. If you’re passionate about this role and want to make an impact on a global scale, please apply!" That's application instruction; remove. Also "About The Team" maybe not boilerplate; it's substantive. Keep. Also "Amazon is an equal opportunity employer..." remove. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe part of benefits but it's a link; could keep? It's more like application instruction; maybe remove. We need to preserve all substantive information: responsibilities list, qualifications, benefits, pay, travel expectation, etc. We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to avoid creating sections with filler.
Let's outline:
About the role
... intro paragraph(s) ... plus About The Team content maybe.
Responsibilities
- ... each bullet from Key job responsibilities ...
Maybe also include "A day in the life" as prose under responsibilities? Could add a after list.
Requirements
Basic Qualifications:
- ... each basic qualification ...
Qualifications
Preferred Qualifications:
- ... each preferred qualification ...
Skills
Maybe we can embed skills within Requirements/Qualifications; but we have separate list of skills like networking fundamentals, Six Sigma tools, etc. Those are already in Basic Qualifications. Could treat them as part of Requirements. So maybe we don't need separate Skills section.
Benefits
- ... list benefits ...
Pay
Base salary range (locations) ...
Maybe also mention sign-on payments and RSUs.
We need to ensure we don't create sections with placeholder text.
Now let's extract content.
Intro description:
"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."
That's the description.
Then "About The Team" paragraph:
"About The Team RTS Field Hardware Support Engineers (FHSE) ensure that our customers—site Reliability and Maintenance Engineers—are equipped to independently maintain Amazon Robotics technologies. Our team achieves this by identifying deficiencies, communicating risk, and proposing mitigation strategies. Our hands-on approach to testing, troubleshooting, and investigating puts us in the shoes of operators and technicians in the field. We work backwards from these insights to satisfy engineering requirements, partnering with safety, hardware, software, and cross-functional support teams."
We can combine into About the role.
Now Responsibilities list (Key job 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
- Up to 50% travel expected
Note: "Up to 50% travel expected" is a responsibility/travel expectation; we can include as bullet.
Now "A day in the life" paragraph:
"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."
We can include as prose after responsibilities list.
Now Basic Qualifications:
- Bachelor's degree or above in Mechanical, Electrical, Industrial Engineering, or related STEM field
- Knowledge of networking fundamentals
- Experience working in a 24/7 production environment
- Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred
- Knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems
- Experience in Linux systems administration and/or development
Note: "Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred" is phrased as preferred but it's under Basic Qualifications. We'll keep as is.
Now Preferred Qualifications:
- 2+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience
- 1+ years of building scripts, tooling, and automation for large-scale computing environments experience
- Experience in site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration
- Experience in network capture and systems troubleshooting
- Experience building scripts, tooling, and automation for large-scale computing environments
Note there is some duplication; we keep as given.
Now Benefits:
First benefits paragraph: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. 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. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan"
Second benefits paragraph: "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."
We should combine into a list, avoiding duplication. Let's extract unique benefits
for prose. We need to avoid creating sections with filler. Let's outline:
About the role
... intro paragraph(s) ... plus About The Team content maybe.
Responsibilities
- ... each bullet from Key job responsibilities ...
after list.
Requirements
Basic Qualifications:
- ... each basic qualification ...
Qualifications
Preferred Qualifications:
- ... each preferred qualification ...
Skills
Maybe we can embed skills within Requirements/Qualifications; but we have separate list of skills like networking fundamentals, Six Sigma tools, etc. Those are already in Basic Qualifications. Could treat them as part of Requirements. So maybe we don't need separate Skills section.Benefits
- ... list benefits ...
Pay
Base salary range (locations) ...
Maybe also mention sign-on payments and RSUs. We need to ensure we don't create sections with placeholder text. Now let's extract content. Intro description: "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." That's the description. Then "About The Team" paragraph: "About The Team RTS Field Hardware Support Engineers (FHSE) ensure that our customers—site Reliability and Maintenance Engineers—are equipped to independently maintain Amazon Robotics technologies. Our team achieves this by identifying deficiencies, communicating risk, and proposing mitigation strategies. Our hands-on approach to testing, troubleshooting, and investigating puts us in the shoes of operators and technicians in the field. We work backwards from these insights to satisfy engineering requirements, partnering with safety, hardware, software, and cross-functional support teams." We can combine into About the role. Now Responsibilities list (Key job 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 - Up to 50% travel expected Note: "Up to 50% travel expected" is a responsibility/travel expectation; we can include as bullet. Now "A day in the life" paragraph: "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." We can include as prose after responsibilities list. Now Basic Qualifications: - Bachelor's degree or above in Mechanical, Electrical, Industrial Engineering, or related STEM field - Knowledge of networking fundamentals - Experience working in a 24/7 production environment - Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred - Knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems - Experience in Linux systems administration and/or development Note: "Knowledge of Six Sigma tools, Lean techniques, PMP or similar standards preferred" is phrased as preferred but it's under Basic Qualifications. We'll keep as is. Now Preferred Qualifications: - 2+ years of site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience - 1+ years of building scripts, tooling, and automation for large-scale computing environments experience - Experience in site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration - Experience in network capture and systems troubleshooting - Experience building scripts, tooling, and automation for large-scale computing environments Note there is some duplication; we keep as given. Now Benefits: First benefits paragraph: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. 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. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan" Second benefits paragraph: "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." We should combine into a list, avoiding duplication. Let's extract unique benefits