Hardware Dev Engineer, OEM Solid State Drives Team

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. Remove boilerplate like EEO, legal, application instructions, etc. Keep all substantive info. We need to parse the description. Key parts: - Description: Application deadline: Sep 23, 2026 (maybe metadata, could be short p). Not a heading. - AWS Compute & ML Services description (intro). Could be "About the role" or "About the team"? The posting includes sections: "What you will do:", "Why it matters:", "Why you will love it:", "Key job responsibilities", "About The Team", "Basic Qualifications", "Preferred Qualifications", "Meets/exceeds Amazon’s leadership principles requirements for this role" (maybe part of qualifications). Also salary ranges and benefits. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: could include intro about AWS Compute & ML Services, HWEng team, mission, etc. Could be a paragraph. - Responsibilities: "What you will do:" and "Key job responsibilities" and maybe "Why it matters"? Actually "Why it matters" is more about impact, could be part of About the role or separate but not a standard heading. We'll put responsibilities under

Responsibilities

with list items. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications (maybe also leadership principles). Could be under Qualifications. - Skills: maybe combine some skills from preferred qualifications (coding, scripting, etc.) Could be separate Skills section. - Benefits: The paragraph about benefits (health insurance, 401k, etc.) plus mention of sign-on payments and RSUs. - Pay: Salary ranges for locations. - Schedule: Not mentioned; we should not create Schedule section if no content. We must not create sections with filler like "not specified". So omit Schedule. We need to preserve all substantive info; do not invent or summarize away detail. Must not lose details. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings,

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

  for prose. We need to decide what to put in lists. Responsibilities: we have bullet-like sentences: "design and build infrastructure to operate our storage platforms at massive scale.", "lead the integration and delivery of SSD from OEM suppliers, and support the development of automated monitoring and failure analysis services to operate, debug, and scale these devices.", "work closely with other AWS software teams to tailor and operate storage solutions for the AWS environment.", "provide leadership in the application of new technologies to large scale server deployments in a continuous effort to deliver a world-class customer experience.", "have high standards for yourself and everyone you work with, and you’ll be constantly looking for ways to improve your products performance, quality and cost." Also from "Key job responsibilities": "bring new storage (SSD) technology to our systems & products as well as scaling how we operate our massive existing & rapidly growing fleet.", "work closely with software engineers in your and other AWS teams to drive operational excellence - building software services for optimizing SSD performance and health at scale, including faster detection, prevention and root-cause of issues.", "lead the integration and delivery of SSD from OEM suppliers, and support the rollout of new drives for new & existing platforms." We can combine them, avoid duplication. We'll produce a list. Requirements (Basic Qualifications): list items: "5+ years of hardware design and validation of components, subsystems and systems experience", "Bachelor's degree in electrical engineering, computer engineering, or equivalent", "Experience with root-cause, debug and resolution of issues on storage systems in Linux environment", "Experience with system integration and operation of SSDs." Qualifications (Preferred Qualifications): list items: "Proficient coding, scripting and debug abilities in Linux environment", "Experience working with interdisciplinary teams to execute product design from concept to production", "Expertise in server technologies such as, thermal, mechanical, power, and signal integrity.", "Experience in developing technical documentation such as functional specifications, design verification plans and functional test procedures", "Meets/exceeds Amazon’s leadership principles requirements for this role". (The last is maybe a requirement but we can include.) Skills: Could extract from preferred qualifications: coding, scripting, debugging, interdisciplinary teamwork, server tech expertise, documentation. Could make a list. Benefits: list items: "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 maybe mention "Learn more about our benefits at https://amazon.jobs/en/benefits." but that's a link; we could keep as prose? Might be considered boilerplate? It's a link to benefits; but it's part of benefits description. We'll keep as a sentence maybe. Pay: list of salary ranges per location: "USA, CA, Cupertino - 157,300.00 - 212,800.00 USD annually", "USA, CO, Denver - 136,000.00 - 184,000.00 USD annually", "USA, WA, Seattle - 136,000.00 - 184,000.00 USD annually". Could be a list. We also have "Application deadline: Sep 23, 2026". Could be a short p at top. We need to avoid repeating job title as heading. Not needed. We need to discard boilerplate: EEO, equal opportunity, legal, scam warning, etc. Also discard "Los Angeles County applicants:" etc. Also discard "If you have a disability..." etc. Also discard "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also discard "Company - Amazon Development Center U.S., Inc. Job ID: A10423860". Also discard "Amazon is an equal opportunity employer..." etc. We need to keep all substantive info: intro paragraphs about AWS Compute & ML Services, HWEng team, mission, etc. Also "Why it matters:" and "Why you will love it:" maybe we can incorporate into About the role or separate sections? Since we have limited headings, we could put them under About the role as prose. We must not invent or summarize away detail. So we need to keep the exact sentences? We can paraphrase but must preserve all substantive information. Safer to keep the sentences as they are, maybe split into

  paragraphs. We'll produce:

  Application deadline: Sep 23, 2026

  About the role

  [intro paragraphs about AWS Compute & ML Services, HWEng team, mission, etc.]

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  • ...
  ...
  We must not include Schedule. Check that we haven't missed any substantive info: The "Why it matters:" and "Why you will love it:" paragraphs. We could incorporate them into About the role as additional paragraphs. Let's extract the relevant paragraphs: From description: "AWS Compute & ML Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people 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." Next paragraph: "Amazon Web Services (AWS) Hardware Engineering (HWEng) team creates compute, accelerator, edge and storage server designs for Amazon’s innovative web services. Our designs are industry-leading in performance, frugality and operational excellence, and are critical to the success of the AWS business and the more than one million customers who use AWS today. Our Hardware Engineers solve challenging technology problems, and build architecturally sound, high-quality server systems and components to enable AWS to realize critical business strategies." Next: "We are seeking experienced Hardware Design Engineers to lead integration and operations of next generation storage (SSD) for our cloud systems. Our success depends on our highly respected server infrastructure; we’re handling massive scale and rapid integration of emergent technologies." Then "What you will do:" bullet-ish sentences. Then "Why it matters:" paragraph: "Public cloud IT services represent the majority of growth in the overall IT services market and will continue to do so for several years to come. The scale of AWS, combined with an understanding of how our hardware is used, creates a unique opportunity for hardware customizations that will directly benefit AWS customers." Then "Why you will love it:" paragraph: "You will work directly with engineers across the company to build next-generation hardware. You will have a direct impact on our bottom line and the ability to deliver improvements for our customers. You will be part of a growing, fast paced, and fun team. You will have ownership for the implementation of your work." Then "AWS Hardware Engineering team is seeking experienced hardware design engineers to design and build next-generation server systems, and AWS specific hardware component." (somewhat repetitive) Then "Key job responsibilities As a hardware engineer of the OEM Solid State Drives engineering team, you will be responsible for bringing new storage (SSD) technology to our systems & products as well as scaling how we operate our massive existing & rapidly growing fleet. You will work closely with software engineers in your and other AWS teams to drive operational excellence - building software services for optimizing SSD performance and health at scale, including faster detection, prevention and root-cause of issues. You will lead the integration and delivery of SSD from OEM suppliers, and support the rollout of new drives for new & existing platforms." Then "About The Team" paragraph: "Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." Then Basic Qualifications list. Then Preferred Qualifications list. Then "Meets/exceeds Amazon’s leadership principles requirements for this role" (maybe a line). Then benefits and pay paragraphs. We need to ensure we don't lose any of these. We'll structure: - About the role: combine the introductory paragraphs (AWS Compute & ML Services, HWEng team, mission, seeking experienced HW Design Engineers, etc.) plus maybe "About The Team" paragraph? Actually "About The Team" is about AWS generally; could be part of About the role. We'll include all those paragraphs as