System Development Manager, AWS Manufacturing and Repair

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 content: - Description: AWS Manufacturing & Repair operations ... (intro paragraph). This is description. - This role directly supports physical manufacturing environments across multiple locations with travel expected up to 25% of the time. - Key job responsibilities: bullet list under "Lead & Develop the Team", "Establish Roadmap & Technical Vision", "Drive Automation, Uptime & Yield", "Own the Test Ecosystem", "Be an Operational Leader", "Collaborate Across Teams". Each bullet has subpoints. - About The Team: subpoints: Inclusive Team Culture, Work/Life Harmony, Mentorship and Career Growth, Diverse Experiences. - Basic Qualifications: list of bullet points. - Preferred Qualifications: list. - Salary ranges: listed for three locations: USA, KY, Florence - 166,300.00 - 225,000.00 USD annually; USA, TX, Austin - same; USA, WA, Bellevue - same. - Benefits: mention comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave. Also mention sign-on payments and RSUs. - Company: Amazon Data Services, Inc. - Job ID: A10561524 (should be folded into short p or dropped). We can include a short p with Job ID maybe. We must not include boilerplate like equal opportunity employer, accommodation link, etc. We need to decide sections. We have substantive content for: - About the role (intro description). Could be under "About the role" heading. - Responsibilities: we have "Key job responsibilities" with subpoints. - Requirements: could combine Basic Qualifications and Preferred Qualifications? Or separate "Qualifications" and "Skills"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content. We have qualifications (basic and preferred). Could put under "Qualifications". Skills could be derived from preferred qualifications (knowledge of software engineering best practices, etc.) but we might combine. We have benefits: mention comprehensive benefits, sign-on payments, RSUs, health insurance, 401(k) matching, paid time off, parental leave. So we can have Benefits section. Pay: we have salary ranges for three locations. So we can include Pay section. Schedule: we have travel expected up to 25% of the time. That's schedule-related? Could be considered schedule. But the instruction says only create Schedule section if posting actually states them. It does mention travel expected up to 25% of the time. That's schedule-related. So we could include Schedule section with that detail. We also have "About The Team" content. Could be part of About the role or separate? Could be under About the role or maybe under "About the Team" but not a prescribed heading. We could incorporate into About the role section. We need to avoid filler headings. So we will include sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly Skills? But we might not need separate Skills if we put skills under Qualifications. The instruction says we can use those headings but only if real content. We have content for skills (knowledge of professional software engineering best practices, etc.) which could go under Skills. But we also have qualifications. Might be better to have Qualifications (basic) and Skills (preferred). However we need to avoid thin sections. Let's see if we can combine basic and preferred into Qualifications and still have substantive content. The Qualifications section would contain both basic and preferred bullet lists. That's substantive. Thus we can have: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We must not repeat job title as heading. So no heading for "Systems Development Manager". Good. We need to format lists with

• . For prose, use

  . We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like travel up to 25%, salary ranges, benefits details, etc. We need to remove boilerplate: equal opportunity employer, accommodation link, etc. Also remove duplicated lines (like repeated "Experience in managing system or software development teams" appears twice in basic qualifications). We should keep only one instance? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should deduplicate repeated lines. The basic qualifications list includes: - 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 There's duplicate "Experience in managing system or software development teams". We should keep only one. Also "Experience in systems engineering and operations leadership for an Internet service or leading-edge IT organization" maybe similar to later? Not duplicate. We'll deduplicate. Preferred qualifications list includes many items; we should keep them. Now we need to ensure we don't lose any substantive info. Let's extract sections. **About the role** (intro paragraph plus maybe About The Team). We'll combine intro and About The Team bullet points. Intro paragraph: "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!" Then About The Team bullet points: Inclusive Team Culture, Work/Life Harmony, Mentorship and Career Growth, Diverse Experiences. We'll incorporate as prose or list? Probably list. We'll produce a

  for the intro paragraph(s) and then a

  • for the About The Team bullet points. **Responsibilities**: We have bullet points under "Key job responsibilities". We'll create a
    • for each main responsibility, and within each we may have subpoints. We could nest lists? The instruction says use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can flatten by using separate
      • with subpoints as separate sentences. However we need to preserve all substantive information. Could keep subpoints as separate
      • under a parent? Might be okay to nest
        inside
        • . But to keep simple, we can make each bullet a
        • and include subpoints as separate sentences within that
        • . That preserves info. Responsibilities list: - 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