Software Dev Engineer II, AWS Infra Supply Chain Automation, AWS Infra Supply Chain Automation

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse description. First, we need to remove boilerplate: EEO, accommodation, etc. Also remove Job ID line. We need to keep substantive info. Let's extract sections. The description starts: "Description AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. ..." This is about the role. So we can put under

About the role

a paragraph with that description. Then later: "As part of AWS Supply Chain Management Team, you'll be a key part of developing next-generation supply chain solutions, produce manufacturing plans for data center capacity, and you'll have the chance to design and create enterprise-class products from scratch. You'll architect, design, and implement federated and highly scalable distributed systems with high availability, low latency, and high throughput. You'll get the chance to use AWS' latest technologies to build and deploy enterprise-class products. We are looking for creative and motivated software developers that want to work on challenging and high-impact problems." That's also about role/responsibilities. Could be responsibilities. Then: "To be successful in this role, you must have a thorough understanding of algorithms and data structures, as well as the ability to produce bulletproof code. You must be passionate about delivering high-quality designs, inventive in problem-solving, and unafraid to think outside the box." That's qualifications/requirements. Then "Key job responsibilities" list bullet points. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then benefits and pay info: "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. 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." Then location: "USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually" Thus we have Pay and Benefits sections. Schedule not mentioned, so omit. Skills maybe not explicit; but we could include under Requirements or Qualifications. The instruction: Use sections only when posting has real specific content. We could have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills if we extract from qualifications (algorithms, data structures, bulletproof code, etc.) but we can incorporate into Requirements. We need to avoid repeating job title as heading. No Job ID. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given. Let's extract bullet points. Key job responsibilities: - Design and deliver enhancements to existing features as well as entirely new features independently, producing workable technical solutions that earn positive feedback in design and code reviews. - Apply domain knowledge fulfillment systems and concepts to clearly communicate requirements, system constraints, and proposals with stakeholders across teams. - Operate effectively in a high-ambiguity domain where requirements often arrive underspecified, translating vague business problems into concrete technical designs. - Lead projects independently — collaborating with SDEs within the team and across teams, defining the project plan, and assisting with task estimation and execution. - Mentor teammates both implicitly, through code and design reviews, and explicitly, by providing guidance to more junior engineers. - Proactively identify, improve, and streamline the team's engineering processes. Basic Qualifications: - 3+ years of non-internship professional software development experience - 3+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience - 3+ years of software development engineer or related occupational experience - 3+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience - Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field - Experience programming with at least one software programming language Preferred Qualifications: - 3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience - Bachelor's degree in computer science or equivalent Benefits: health insurance details, 401(k) matching, paid time off, parental leave. Pay: base salary range: USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually. Also mention sign-on payments and RSUs. We need to include Pay section with that info. We should not include "The base salary range for this position is listed below." as filler; we need to keep the actual range. We also need to keep mention of sign-on payments and RSUs. Thus Pay section could be a

  containing: The base salary range for this position is $143,700.00 - $194,400.00 USD annually (USA, WA, Seattle). The Amazon package includes sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on experience, qualifications, and location. But we must not invent; we can keep the sentences as is but rephrase? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid rephrasing, but we should keep the info. Safer to keep the exact sentences but maybe combine. We can keep: "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. USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually" But "The base salary range for this position is listed below." is a bit filler but it's part of the posting; we can keep it. Now Benefits: we need to list the benefits as a 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, and parental leave. We can put as

  • each item? The instruction: Use
    • for any list of duties/requirements/benefits. So we should break into list items. Thus Benefits section:
      • 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
      Now About the role: we need a paragraph summarizing the initial description. Let's combine the first paragraph and maybe the later motivational sentences. We need to preserve all substantive information; we can't omit details. So we need to include everything from the description: The first paragraph about AWS Infrastructure Services, the team description, the part about enjoying building systems, passion about setting standards, working with latest native AWS technologies, developing systems that can grow to AWS scale, being part of AWS Supply Chain Management Team, developing next-gen supply chain solutions, produce manufacturing plans for data center capacity, design and create enterprise-class products from scratch, architect, design, implement federated and highly scalable distributed systems with high availability, low latency, high throughput, use AWS' latest technologies to build and deploy enterprise-class products, looking for creative and motivated software developers that want to work on challenging and high-impact problems. That's a lot. We'll put that in a

      under About the role. Then Responsibilities: we have the "Key job responsibilities" list. Then Requirements: maybe combine the "To be successful in this role" paragraph (algorithms, data structures, bulletproof code, etc.) plus Basic Qualifications? But we have separate Qualifications section. The instruction: Use sections only when posting has real specific content. We have both Basic and Preferred Qualifications. Could combine into Qualifications section with subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put Requirements for the "To be successful..." paragraph, and Qualifications for Basic and Preferred. Thus:

      About the role

      ... (all descriptive text)

      Responsibilities

      ... list items ...

      Requirements

      To be successful in this role, you must have a thorough understanding of algorithms and data structures, as well as the ability to produce bulletproof code. You must be passionate about delivering high-quality designs, inventive in problem-solving, and unafraid to think outside the box.

      Qualifications

      ... Basic Qualifications items ...
      ... Preferred Qualifications items ...
      But we need to differentiate? Could combine all into one list but that would lose distinction. However we could keep two lists with headings inside? Not allowed; only those headings. Could we embed a

      before each list indicating Basic vs Preferred? That would be extra text but permissible as prose. The instruction: Use

      for prose. So we can have a

      Basic Qualifications:

      then
      ... then

      Preferred Qualifications:

      then
      ... That seems okay. Now Benefits and Pay sections. Benefits: as described. Pay: include the salary range and sign-on/RSU. We must not include Schedule. Now ensure we don't include boilerplate: EEO, accommodation, etc. Also remove "Amazon is an equal opportunity employer..." lines. Also remove "Learn more about our benefits at https://..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Company - Amazon Data Services, Inc." maybe keep? It's metadata but not a heading; could be included in a short paragraph? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could include company name in a short p maybe under About the role? But it's minor metadata; we could drop it. Safer to drop. Also drop "Job ID: A10557187". Drop. Now ensure we keep all substantive info: The description about AWS Infrastructure Services, team, motivations, responsibilities, requirements, qualifications, benefits, pay. Let's craft the About the role paragraph. We need to combine: "AWS Infrastructure 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