Sr Systems Development Engineer, AWS AI/ML Servers

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description and extract sections. The posting includes: - Description (intro) maybe as About the role? The first paragraph: "AWS runs the world's largest fleet...". That's about the role. Could be "About the role". We'll put that in

. - "What You Will Do" -> Responsibilities. - "Why You Will Love It" maybe could be Benefits? But it's more about why you'll love it; could be considered Benefits? However we have a Benefits section only if posting actually states them. There's also later "Benefits" mention: "Amazon also offers comprehensive benefits including health insurance...". That's a Benefits section. - Pay: there is salary ranges listed: "USA, CA, Cupertino - 173,900.00 - 235,200.00 USD annually" etc. So we have Pay info. - Schedule: not mentioned explicitly. No schedule info. So we should not create Schedule section. - Skills: maybe from qualifications? Could be separate Skills section? The posting has "Basic Qualifications" and "Preferred Qualifications". Those could be Requirements and Qualifications. We'll treat Basic Qualifications as Requirements, Preferred Qualifications as Qualifications (or Skills). The instructions: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We have: - Basic Qualifications: list of years experience etc. That's Requirements. - Preferred Qualifications: list of preferred experience etc. That could be Qualifications. - Skills: maybe not explicitly listed; but we could infer from responsibilities? Better not to create Skills unless there is explicit content. The posting does not have a separate "Skills" heading. So we should not create Skills section. - Benefits: we have benefits description. - Pay: salary ranges. - Schedule: none. - About the role: we have introductory paragraph. - Responsibilities: "What You Will Do" plus maybe "Key job responsibilities" etc. We'll combine. We need to ensure we preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, equal-opportunity, scam-warning, legal, cookie/navigation, application instructions. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, intro paragraph: "AWS runs the world's largest fleet of AI/ML accelerator servers. When a model with billions of parameters trains across a large scale of GPUs, every minute of downtime costs real progress. We are building the automation, diagnostics, and predictive intelligence that keeps this fleet running at peak. If you want to work at the intersection of hardware, software, and scale — where your code directly prevents customer-impacting failures — this is the role. We are seeking a Systems Development Engineer to build automation software, diagnostic tooling, and fleet health infrastructure for our accelerated compute platforms. You will work across multiple teams and organizations to design scalable, reliable systems for our accelerated compute fleet." That's the About the role. Next, "What You Will Do" section: bullet list? It's prose paragraphs. We'll capture as

maybe with

• for list of duties? The instructions: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we need to identify lists. In "What You Will Do": It says: "You will tackle problems no one has fully defined yet — spanning hardware, firmware, kernel, and software simultaneously. You will own systems end to end, writing code that prevents failures rather than reacts to them, and building automation that replaces manual toil with intelligent self-healing. You will work across PCIe topology, GPU diagnostics, Linux drivers, and telemetry pipelines to correlate signals and isolate faults at fleet scale. When your system catches a failing GPU before a training job crashes, that is your impact." That's prose, not a list. Could be left as

    . Then "Why You Will Love It": prose. Then "Key job responsibilities": there is a heading "Key job responsibilities" then bullet list? Actually after that heading, there are paragraphs each starting with bold? Let's see: "Key job responsibilities Fleet Health & Predictive Infrastructure Build and own the automation infrastructure for accelerator (AI/ML) fleet health at a large scale of servers, driving toward zero-touch operations that detect, diagnose, triage, and remediate faults without human intervention Design and develop test frameworks, test coverage strategies, and diagnostic tooling to validate hardware functionality, detect faults, and ensure qualification coverage across the platform lifecycle. Design predictive failure detection using telemetry, sensor data, error trending, and log correlation to identify degrading components before customer impact Develop monitoring dashboards and alerting for real-time fleet health visibility across manufacturing, lab, and production environments Define and track fleet health metrics: failure rates, mean time to detect and resolve issues, first-time fix rate, test dwell time, and predictive accuracy Debugging & Troubleshooting Debug complex system-level issues across compute, GPU, and networking in production — including Linux boot/runtime failures, PCIe, power, NIC, NVMe, and GPU subsystems on x86 and ARM Perform root cause analysis correlating across firmware, kernel, driver, and physical layer; feed findings into manufacturing quality and design improvements Systems Development & Automation Design scalable test automation for hardware bring-up, regression, and qualification — reducing manufacturing test cycle times without sacrificing coverage through intelligent test sequencing and parallel execution Build data pipelines correlating test results, sensor telemetry, and component-level data to identify systemic yield issues and drive upstream fixes Develop and maintain Linux device drivers on ARM and x86; work with OS internals and accelerator/GPU software stacks Build and manage tests covering all functional aspects of the system and CI/CD pipelines for rapid deployment to manufacturing lines and production fleet Cross-Team Collaboration Work across engineering teams and internal customers to ensure new accelerated compute hardware meets data path, control path, and onboarding requirements Engage with ODMs and design partners on testability, diagnostic coverage, and automation requirements during hardware design and bring-up phases — influencing functional and performance readiness of the platform Partner with datacenter operations to close the loop between field failures, manufacturing escapes, and design improvements Operational Excellence Participate in post-incident reviews, identify contributing causes and drive permanent fixes that eliminate whole classes of risk Produce clear, maintainable documentation for systems, runbooks, and automation to enable others to operate and extend your work Drive process improvements that increase team agility — reducing development friction, eliminating unnecessary gates, and improving delivery velocity May require occasional ( under a

    . But the instruction: Use
    • for any list of duties/requirements/benefits. So we should convert these groups into list items. Thus under Responsibilities we can have a
      with each group as
      • . However we also have the earlier "What You Will Do" prose; we could keep that as

        before the list. Alternatively we could treat the whole "What You Will Do" and "Key job responsibilities" as responsibilities; we could combine into a single

        list. But we need to preserve all substantive info; we can keep the prose as

        and then a

        for the detailed responsibilities. Now "Why You Will Love It": prose. Then "A day in the life": prose narrative; could be part of Responsibilities or maybe a separate section? Not a standard heading; we could include as part of Responsibilities or maybe as a separate section like "Typical Day". But instructions only allow certain headings; we should not create extra headings. Could embed as prose under Responsibilities or maybe under About the role? Probably better to include as part of Responsibilities (makes sense). But we must not lose that info. We'll add as a

        under Responsibilities. Now "About The Team": prose; could be part of About the role or separate? Could be "About the team" but not a standard heading. Could treat as part of About the role or maybe as a separate section like "About the team" but not allowed. We'll incorporate into About the role. Now Basic Qualifications: list of requirements. We'll output as

        • under Requirements heading. Preferred Qualifications: list under Qualifications heading. Benefits: we have paragraph about benefits; we can output as
          • for each benefit? The paragraph lists many benefits separated by commas. Could split into list items. But we need to preserve all substantive info; we can keep as

            but instruction says use

            • for any list of benefits. So we should convert to list. Pay: we have salary ranges for three locations. Could present as
              • each location range. Schedule: none, omit. Now we must remove boilerplate: EEO, equal opportunity, Los Angeles County specifics, criminal history, accommodation link, etc. Also remove "Company - Amazon Data Services, Inc. Job ID: A10537783". Also remove "Learn more about our benefits at https://...". Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Los Angeles County applicants:" etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "May require occasional (About the role

...

Responsibilities

What You Will Do ...

A day in the life ...

• Fleet Health & Predictive Infrastructure: Build and own the automation infrastructure for accelerator (AI/ML) fleet health at a large scale of servers, driving toward zero-touch operations that detect, diagnose, triage, and remediate faults without human intervention; Design and develop test frameworks, test coverage strategies, and diagnostic tooling to validate hardware functionality, detect faults, and ensure qualification coverage across the platform lifecycle; Design predictive failure detection using telemetry, sensor data, error trending, and log correlation to identify degrading components before customer impact; Develop monitoring dashboards and alerting for real-time fleet health visibility across manufacturing, lab, and production environments; Define and track fleet health metrics: failure rates, mean time to detect and resolve issues, first-time fix rate, test dwell time, and predictive accuracy.
• Debugging & Troubleshooting: Debug complex system-level issues across compute, GPU, and networking in production — including Linux boot/runtime failures, PCIe, power, NIC, NVMe, and GPU subsystems on x86 and ARM; Perform root cause analysis correlating across firmware, kernel, driver, and physical layer; feed findings into manufacturing quality and design improvements.
• Systems Development & Automation: Design scalable test automation for hardware bring-up, regression, and qualification — reducing manufacturing test cycle times without sacrificing coverage through intelligent test sequencing and parallel execution; Build data pipelines correlating test results, sensor telemetry, and component-level data to identify systemic yield issues and drive upstream fixes; Develop and maintain Linux device drivers on ARM and x86; work with OS internals and accelerator/GPU software stacks; Build and manage tests covering all functional aspects of the system and CI/CD pipelines for rapid deployment to manufacturing lines and production fleet.