System Development Manager, AWS Manufacturing and Repair

for prose. So we can have nested lists? Probably okay to have

• with further
  inside? Might be okay but we can keep simple: each bullet as
  • with its content as prose (maybe using

    inside?). But they said use

    for prose. So maybe each responsibility as

  • ...

  . That satisfies. - Requirements: Basic Qualifications list. Those are bullet points: 5+ years..., Bachelor's degree..., Experience..., Experience..., Experience..., Experience... . We'll output as
  • each. - Qualifications: Preferred Qualifications list. We'll output similarly. - Skills: Not explicitly listed but could be derived from Preferred Qualifications? Might be considered skills. But we can include a Skills section if there is explicit skill list. The posting includes "Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby" etc. That's more like qualifications. Could treat as Skills. But we need to only include sections when posting has real specific content. There's no explicit "Skills" heading, but we could infer from Preferred Qualifications. However instruction: "Prefer a few substantive sections over many thin ones." Might combine Skills into Qualifications? But they ask to use sections like Skills if present. Since not explicit, maybe omit Skills. - Benefits: The paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance...". Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also mention 401(k) matching, paid time off, parental leave. So we have benefits content. So include Benefits section with
    • items. - Pay: The base salary range listed: "USA, KY, Florence - 166,300.00 - 225,000.00 USD annually" etc multiple locations. So we have pay info. Include Pay section with maybe a

      containing the ranges. - Schedule: Travel expected up to 25% of the time. Also maybe mention physical manufacturing environments across multiple locations with travel expected up to 25% of the time. That's schedule info. So include Schedule section with

      . We must not include boilerplate like EEO, accommodation link, etc. Also remove duplicated lines. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like responsibilities details exactly as given? We can paraphrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the text as is, maybe copy sentences. We need to output only HTML fragment, no markdown fences. Let's construct:

      About the role

      AWS Manufacturing & Repair operations is focused on automated assembly solutions where innovative approaches are needed to accelerate overall manufacturing time for AI/ML platforms. We work backwards from customers to increase critical capacity for AWS services by improving yield and reliability while reducing cycle time. This highly cross-functional initiative brings together critical expertise from across Amazon teams dedicated to meeting and exceeding customer expectations through innovative validation processes and Amazon operational excellence. We are seeking a Systems Development Manager to lead and grow a team of System Development Engineers and Manufacturing Test Engineers who own the operational execution of the end-to-end manufacturing test ecosystem for AI server hardware — from early NPI builds through high-volume production and sustaining — across server (L10) and rack-level (L11/L12) integration. This is an opportunity to work with internal partner teams across Software and Hardware Engineering to shape manufacturing test strategy from the ground up, build a world-class engineering team, and directly impact the speed and quality at which AI infrastructure reaches customers. This role sits at the intersection of hardware, software, production operations, and people leadership. This role will support the development of the technical vision and also hire, mentor, and develop the engineers who bring it to life. You'll establish the team's roadmap, drive automation and self-remedy capabilities across the production line, and relentlessly pursue uptime, yield, and operational excellence. You'll be a hands-on leader who dives deep into the details on business, operations, and engineering while simultaneously growing the next generation of technical leaders on your team. AWS Manufacturing & Repair is part of the broader AWS Infrastructure Services team, which owns the design, planning, delivery, and operation of all AWS global infrastructure. We are the teams who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we're looking for talented people who want to help. You'll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You'll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you'll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion. Come join our team and be a part of history as we deliver results for the largest cloud services company on Earth! This role directly supports physical manufacturing environments across multiple locations with travel expected up to 25% of the time.

      But note travel sentence is schedule; maybe we should move that to Schedule section. However it's also part of About the role description. We could keep it there but then Schedule would be duplicate. Better to keep About the role without travel sentence, and put travel in Schedule. Let's extract travel sentence: "This role directly supports physical manufacturing environments across multiple locations with travel expected up to 25% of the time." We'll put that in Schedule. Thus About the role paragraph ends before that sentence. Now Responsibilities: We'll list each bullet. We need to capture subpoints. Could embed as
      • with

        and maybe nested

        . Let's do nested lists for clarity. Responsibilities: - Lead & Develop the Team * Hire, motivate, mentor, and develop a team of System Development and Manufacturing Test Engineers, promoting growth and opportunity at every level. * Define the structure and strategy for the team, determining the right mix of engineers and where they need to be allocated to meet business goals across multiple manufacturing sites. * Develop senior engineers by promoting growth and providing opportunities to demonstrate higher-level scope, impact, complexity, and leadership. * Foster a culture of ownership, curiosity, and operational excellence where engineers take end-to-end responsibility for the systems they build and support. - Establish Roadmap & Technical Vision * Establish and own the manufacturing test engineering roadmap, successfully delivering engineering solutions that execute that vision. * Your roadmap influences organizational goals and you are involved in the yearly planning process. * In partnership with internal Software and Hardware Engineering teams, define modular test strategies, pass/fail limits, and statistical process controls (GR&R, Cp/Cpk, correlation analysis) to ensure product quality at scale. * Architect the manufacturing test infrastructure for AI server hardware products, spanning board-level validation through full rack integration and networking. - Drive Automation, Uptime & Yield * Lead the development of automated test processes and self-healing capabilities that reduce manual intervention, increase throughput, and improve first-pass yield across the production line. * Own functional test yield across shifts, lead triage efforts for test-station failures, and drive weekly production quality reviews with cross-functional partners. - Own the Test Ecosystem * Oversee the design and maintenance of production test software and automation frameworks using Python, Bash, and related tooling, including test sequencing, equipment control, data collection, and reporting pipelines. * Guide test fixture design and procurement, ensuring alignment to cost, scalability, and schedule requirements; engage in RFQ processes for optimal end-to-end test solutions. * Provide ongoing support for deployed test systems, implement configuration changes for new product variants, and maintain comprehensive documentation of test procedures, specifications, and infrastructure. - Be an Operational Leader * Take a data-driven approach, consistently utilizing metrics to measure performance gaps and increase productivity by improving processes at the local level while driving improvements on the global scale. * Compile and analyze test data using both automated reporting systems and exploratory analysis techniques to identify trends, root-cause failures, and drive corrective actions. * Support New Product Introduction (NPI) by partnering with hardware engineering and NPI test teams to develop test solutions from concept prototypes through production ramp, ensuring readiness at each phase gate. - Collaborate Across Teams * Work cross-functionally with hardware design, firmware, process engineering, quality, and operations teams to ensure test requirements are aligned and products are designed for efficient, high-quality manufacturing. * Foster constructive dialogue, harmonize discordant views, and lead the resolution of contentious issues across partner organizations. * Deliver actionable design-for-test (DFT) feedback to hardware and firmware development teams to improve testability and manufacturing efficiency for future platforms. We'll output as

        • Lead & Develop the Team

          ... etc. But maybe simpler: each responsibility as

          • ...

          where the paragraph includes the subpoints separated by semicolons. However that may lose detail. Better to keep subpoints. We'll do nested lists. Now Requirements (Basic Qualifications): - 5+ years of managing system or software development teams experience - Bachelor's degree in Computer Science, Engineering, Mathematics, or a related field - Experience in systems engineering and operations leadership for an Internet service or leading-edge IT organization - Experience in managing system or software development teams - Experience (hands-on) in systems engineering and administrative work in networking, storage systems, and operating systems - Experience in agile software development methodology We'll output as
          • each. Now Qualifications (Preferred Qualifications): - Knowledge of professional software engineering & best practices for full software development life cycle, including coding standards, software architectures, code reviews, source control management, continuous deployments, testing, and operational excellence - Knowledge of systems engineering fundamentals (networking, storage, operating systems) - Experience with Agile engineering practices (Kanban, continuous delivery, etc.) - Experience with AWS platforms, services, and design patterns - Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby - Experience in automating, deploying, and supporting large-scale infrastructure Now Benefits: We need to list benefits: 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, sign-on payments, restricted stock units (RSUs). Also mention comprehensive benefits. We'll output as
            • each. Now Pay: We have multiple location salary