Systems Development Engineer, AWS Generative AI & ML Servers

We need to output HTML fragment with sections: About the role? Actually description includes "What You Will Do", "Key job responsibilities", "A day in the life", "About The Team", "Basic Qualifications", "Preferred Qualifications". Also there is salary range info (Pay). Also benefits info (Benefits). Also schedule? Not present. So we include sections for Pay (salary range), Benefits (benefits, maybe responsibilities, qualifications, about the team, what you will do? But we need to avoid duplication. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include. The posting includes: "What You Will Do" (responsibilities), "Key job responsibilities" (list), "A day in the life" (maybe description), "About The Team", "Basic Qualifications", "Preferred Qualifications". Also salary range (Pay). Also benefits description (Benefits). Also maybe "Skills"? Not explicit. We could combine responsibilities and what you will do into Responsibilities section. Qualifications: Basic and Preferred could be combined into Requirements/Qualifications. Could separate Basic Qualifications and Preferred Qualifications as sub-sections? But we should prefer few substantive sections over many thin ones. So maybe we have sections: Responsibilities, Qualifications, About the Team, Pay, Benefits. Use

  for each. We need to preserve all substantive information. So we need to include the bullet points from responsibilities, qualifications, etc. Also include the description paragraphs. We must not include boilerplate like EEO, accommodation, etc. Also drop Job ID line. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, "What You Will Do" paragraph: "You will solve complex architectural problems that may not be well-defined in advance. You will own your team's systems, proactively identify deficiencies, and write scalable, robust code to solve issues before they impact customers. You will decompose large, difficult server testability, reliability, and diagnosis problems into straightforward tasks and components — delivering yourself and through others in parallel — using a combination of hardware, software, system design, processor architecture, diagnostics, and operations knowledge." Then "Key job responsibilities" with bullet list items: - Fleet Health & Predictive Infrastructure - Build and own the automation infrastructure responsible for the health of the accelerator (AI/ML) compute server fleet - Design and implement predictive failure detection systems using telemetry, sensor data, error trending, and log correlation to identify hardware issues before they cause customer impact - Drive toward zero-touch operations — building automation that detects, diagnoses, triages, and remediates hardware and software faults without human intervention - Develop monitoring tools, dashboards, and alerting systems to provide real-time visibility into fleet health across lab and production environments - Define and track fleet health metrics (failure rates, mean time to detect, mean time to repair, first-time fix rate, predictive accuracy) - Debugging & Troubleshooting - Debug and resolve complex system-level issues across compute, GPU, and networking in production environments - Troubleshoot Linux boot and runtime failures across x86 and ARM architectures, including PCIe, power, NIC, NVMe, and GPU subsystems - Perform root cause analysis on hardware failures — correlating across firmware, kernel, driver, and physical layer to isolate faults - Build diagnostic tooling that automates root cause identification and reduces reliance on manual triage - Improve manufacturing throughput and yield through test optimization - Systems Development & Automation - Define and develop software, automation, and enabling tools for server hardware programs; track and report progress - Design and build scalable system-level software with focus on durability, availability, security, and diagnostics - Develop and maintain device drivers for Linux on ARM and x86 architectures - Build automation solutions using modern programming languages (Python, Ruby, Java, C/C++, etc.) - Work with OS internals and accelerator/GPU software stacks in Linux-based environments - Build, manage, and deploy CI/CD pipelines for rapid deployment of code changes to org-owned and customer-owned systems - Cross-Team Collaboration - Work across internal HWEng teams to ensure new server hardware addresses data path and control path functionality needed by dependent service teams - Work closely with internal customers to identify early any potential problems onboarding new accelerated compute servers into their ecosystem - Engage with ODMs and design partners on testability, diagnostic, and automation requirements during hardware design and development (NPI) - Contribute to server design to improve robustness, testability, diagnosability, and reliability - Partner with datacenter operations teams to close the loop between field failures and design improvements Then "A day in the life" paragraph: "You will collaborate with a variety of roles (SDEs, SDETs, Mechanical/Electrical/Hardware Engineers, TPMs, Managers, Principals) and organizations through server conception, test validation, qualification, launch, and operations — driving high quality and reliability into current and future designs for AWS accelerated server solutions. From orchestration tooling development to hardware integration to kernel driver debugging, you dive deep into problems across the breadth of AWS." Then "About The Team": paragraph: "The Hardware Engineering AI/ML development team is a group of engineers and technical program managers directly responsible for launching and maintaining server hardware in the fleet — including AI/ML accelerator servers with GPUs. Located in Seattle, Cupertino, and Austin, we work with internal development teams, ODMs, and design partners to deliver servers deployed in datacenters worldwide." Then "Basic Qualifications": list: - 2+ years of non-internship professional software development experience - 1+ years of designing or architecting (design patterns, reliability and scaling) of new and existing systems experience - Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby Then "Preferred Qualifications": list: - Familiarity with server hardware architecture, BMC/IPMI, firmware, PCIe topology, and hardware diagnostics - Experience working with ODMs or hardware design partners - Exposure to zero-touch or self-healing automation concepts for large-scale infrastructure - Experience working in large-scale datacenter or cloud environments - Experience with hardware bring-up, validation, or fleet-wide deployment - Familiarity with telemetry pipelines, anomaly detection, or operational metrics at scale Then Pay: "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 specific ranges: - USA, CA, Cupertino - 148,700.00 - 201,200.00 USD annually - USA, TX, Austin - 129,200.00 - 174,800.00 USD annually - USA, WA, Seattle - 129,200.00 - 174,800.00 USD annually Then Benefits: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." We should include that as Benefits section. We need to avoid duplication: The "What You Will Do" and "Key job responsibilities" overlap; we can combine into Responsibilities section with prose and list. Qualifications: combine Basic and Preferred maybe as subheadings? But we should avoid many thin sections. Could have a Qualifications section with two sub-sections? But subheadings not allowed? Only h3 for section headings. Could use

  for Qualifications and then inside have

  ? Not allowed per instruction? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just have one Qualifications section and list both basic and preferred as bullet points, maybe differentiate with bold text? But we must preserve all substantive information; we can include both sets. We could have two sections: Requirements (Basic Qualifications) and Preferred Qualifications. But that would be thin? Might be okay. However instruction: Prefer a few substantive sections over many thin ones. Having many sections may be considered thin. But we have to include all info. Could combine Basic and Preferred into one Qualifications section, with headings inside? Not sure. Better to have sections: Responsibilities, Qualifications, About the Team, Pay, Benefits. That's 5 sections, each substantive. Within Qualifications we can have two sub-lists: Basic Qualifications and Preferred Qualifications, maybe using or just plain text. We must not repeat job title. No job ID. Now produce HTML. Structure:

  Responsibilities

  You will solve complex architectural problems that may not be well-defined in advance. You will own your team's systems, proactively identify deficiencies, and write scalable, robust code to solve issues before they impact customers. You will decompose large, difficult server testability, reliability, and diagnosis problems into straightforward tasks and components — delivering yourself and through others in parallel — using a combination of hardware, software, system design, processor architecture, diagnostics, and operations knowledge.

  • Fleet Health & Predictive Infrastructure
    • Build and own the automation infrastructure responsible for the health of the accelerator (AI/ML) compute server fleet
    • Design and implement predictive failure detection systems using telemetry, sensor data, error trending, and log correlation to identify hardware issues before they cause customer impact
    • Drive toward zero-touch operations — building automation that detects, diagnoses, triages, and remediates hardware and software faults without human intervention
    • Develop monitoring tools, dashboards, and alerting systems to provide real-time visibility into fleet health across lab and production environments
    • Define and track fleet health metrics (failure rates, mean time to detect, mean time to repair, first-time fix rate, predictive accuracy)
  • Debugging & Troubleshooting
    • Debug and resolve complex system-level issues across compute, GPU, and networking in production environments
    • Troubleshoot Linux boot and runtime failures across x86 and ARM architectures, including PCIe, power, NIC, NVMe, and GPU subsystems
    • Perform root cause analysis on hardware failures — correlating across firmware, kernel, driver, and physical layer to isolate faults
    • Build diagnostic tooling that automates root cause identification and reduces reliance on manual triage
    • Im