Hardware Support Engineer, Robotics Technical Services

We need to output HTML fragment with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. Must not create sections with filler like "commensurate etc. We need to parse the description. Key sections: - About the role: The initial paragraph describing inspiration, team, role description. Could be "About the role" heading. - Responsibilities: The list of key job responsibilities (bulleted). Also "A day in the life" could be part of responsibilities or separate? Probably responsibilities. - Requirements: Basic Qualifications and Preferred Qualifications? Could be "Qualifications" heading. Might separate Basic and Preferred? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. So we can have "Qualifications" for basic qualifications, maybe "Preferred Qualifications" as sub? But we only have h3 headings; we could combine Basic and Preferred under Qualifications with sub-lists? Might be okay to have separate sections: "Basic Qualifications" and "Preferred Qualifications". But the allowed headings list includes Qualifications (maybe covering both). We'll decide to have "Qualifications" for basic qualifications, and maybe "Preferred Qualifications" as another heading? The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine basic and preferred under Qualifications with two sub-lists? But we need to use

• for any list. Could have nested lists? Probably okay. We also have Skills: maybe from knowledge of networking fundamentals, Six Sigma, etc. Could be separate Skills section. Benefits: The paragraph about benefits: "Amazon offers a full range of benefits..." includes list of benefits. So we can have Benefits heading with ul list. Pay: The base salary range listed: "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 there are location-specific ranges: USA, TX, Dallas - 82,400.00 - 144,100.00 USD annually etc. So we have pay info. So we should include Pay heading with that info. Schedule: Not mentioned besides "Up to 50% travel expected". That's not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section. Also there is "A day in the life" narrative; could be part of Responsibilities or separate section "Day in the Life". Not in allowed headings list but we could incorporate into Responsibilities. We must not include boilerplate like EEO, accommodation, etc. We must not include navigation, cookie, legal, duplicated lines. We must preserve all substantive information: So we need to keep all responsibilities bullet points, qualifications, benefits list, pay ranges, travel expectation, etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  ...

  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
  Maybe also include "Up to 50% travel expected" as a responsibility? Could be a separate bullet. Add bullet: "Up to 50% travel expected". Now Qualifications: We'll have Basic Qualifications and Preferred Qualifications maybe as subheadings? But only h3 allowed. Could do two sections:

  Basic Qualifications

  and

  Preferred Qualifications

  . That seems okay as they are substantive. Basic Qualifications list: - 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 Preferred Qualifications list: - 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 Skills: Could extract from qualifications? But we already have qualifications. Maybe we can have a Skills section for things like "Knowledge of networking fundamentals", "Six Sigma", etc. But we already have them in qualifications. To avoid thin sections, maybe we combine qualifications and skills into one Qualifications section with sub-lists? But instruction says we can use Qualifications heading. We'll put both basic and preferred under Qualifications with headings inside? Not allowed because only h3 for section headings. Could use

  Qualifications

  then have two

  ? Not allowed? The instruction only mentions using

  for section headings; doesn't forbid other headings but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we stick to h3 only. So we could have separate sections: Basic Qualifications and Preferred Qualifications as h3 each. That's fine. Now Benefits: Provide list: - Medical, Dental, and Vision Coverage - Maternity and Parental Leave Options - Paid Time Off (PTO) - 401(k) Plan - Sign-on payments and restricted stock units (RSUs) (maybe part of compensation) - 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 - parental leave But we need to avoid duplication. The benefits paragraph includes: "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". Then 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." We should combine unique items: Medical, Dental, Vision; Prescription; Basic Life & AD&D; Supplemental life plans; EAP; Mental Health Support; Medical Advice Line; Flexible Spending Accounts; Adoption and Surrogacy Reimbursement; Maternity and Parental Leave; Paid Time Off; 401(k) Plan; 401(k) matching; Sign-on payments and RSUs (maybe part of compensation not benefits). We'll keep as benefits. Now Pay: Provide salary ranges for locations: Dallas, Pflugerville, San Antonio each 82,400 - 144,100 USD annually. Also mention sign-on payments and RSUs, final compensation based on experience, qualifications, location. We'll output as

  Pay

  ...

  maybe include list. Schedule: Not present, so omit. Now we need to ensure we didn't include boilerplate like EEO, accommodation, etc. We removed those. Check for duplicated lines: We have some duplication in qualifications; we keep as given but could deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines are part of the posting; we should keep them? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate repeated lines. In qualifications, there are duplicates: "Experience in site reliability engineering (SRE), systems engineering, systems administration, DevOps, security administration, or network administration experience" appears twice (once in 2+ years bullet and again later). Also "Experience building scripts, tooling, and automation for large-scale computing environments" appears twice. We should remove duplicates. Let's list unique qualifications: 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 Preferred Qualifications (unique): - 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 network capture and systems troubleshooting We removed duplicate lines. Now responsibilities: Are there duplicates? Not really. Now benefits: Need to deduplicate. Items: Medical, Dental, Vision Coverage; Maternity and Parental Leave Options; Paid Time Off (PTO); 401(k) Plan; 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; parental leave. We see Paid Time Off appears twice (PTO and paid time off). Parental leave appears twice (Maternity and Parental Leave Options and parental leave). We'll deduplicate. Let's compile unique benefits: - Medical, Dental, and Vision Coverage - Prescription coverage - Basic Life & AD&D insurance - Supplemental life plans (option) - Employee Assistance Program (EAP) - Mental Health Support - Medical Advice Line - Flexible Spending Accounts - Adoption and Surrogacy Reimbursement coverage - Maternity and Parental Leave - Paid Time Off (PTO) - 401(k) Plan - 401(k)