Software Dev Engineer II, AWS Builder Acceleration

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions. We need to preserve all substantive info. Let's extract content: Description paragraph: "Are you passionate about leveraging GenAI and advanced AWS technologies to simplify builder experience and accelerate innovations at AWS scale? We are building a new organization, AWS Builder Acceleration (AWSBA), focused on reducing toil and increasing building efficiency across AWS builders. Our mission is to accelerate AWS builder teams’ innovation by eliminating friction throughout the software development and operational lifecycle. Through AI based automated solutions and centralized service management, we address fundamental challenges including Keep The Light On (KTLO) service maintenance burden, launch readiness complexities, and recurring operational load. Through continuous collaboration with builder teams to identify emerging challenges, we shape our strategic roadmap to reinvent the development and operational ecosystem. We are seeking an SDE II to help AWSBA simplify and accelerate the software development experience for 20,000+ AWS engineers. You will shape AWS builder experience from the ground up with a singular mission: make software development, deployment and maintenance simpler across AWS. Success requires building services and tools that reduce friction, listening closely to what your internal customers tell you gets in the way of building, influencing the Amazon Software Builder Experience (ASBX) roadmap, and driving transformation for engineering teams. You will harness advanced technologies, including AI-powered tooling, agentic workflows, and innovative AWS solutions, to create next-generation software builder experience at AWS scale. This role requires ownership, autonomy, and an ability to deliver results. You should be a self-starter with a bias towards independent problem solving. Clear communication and prioritization will be important as you partner with stakeholders to plan, design, and deliver game changing builder experiences to accelerate innovation. Your passion for improving builder experiences, and proven experience managing complex technology projects, will help you make strong strategic judgments. Your expertise is deep and broad. You start with the customers (builders) and work backwards to develop a coherent vision for services and tools that support the efficiency, flexibility and scale that builders expect from us. You have built and operated systems that support high-end business complexity and scale with simple and elegant solutions that are highly decoupled. You will join a select team of innovators creating the next generation of AWS builder experiences that will shape the company's future." That's about the role. Key job responsibilities bullet list: "Identify and prioritize high-impact problems that impede AWS software development Decompose complex builder problems into simple, straightforward and scalable solutions. Collaborate with AWSBA, ASBX and AWS builder teams to build and operate the designed solutions. Deliver meaningful improvements weekly while working toward long-term transformation" Unique Opportunities bullet list: "Re-imagine how developers build and operate the software that underpins the world's largest cloud Drive significant transformation across AWS engineering Pioneer the use of cutting-edge generative AI technologies to create the next generation of builder experiences." A day in the life paragraph: "You should have deep expertise in the architecture and business use of AWS technologies. You recognize the transformative potential of generative AI in software development and are excited to pioneer AI-powered builder experiences that fundamentally change how developers write, debug, deploy and operate code at scale. You remain technically hands-on and close to the technology. You're passionate about developer experience and get frustrated by inefficiencies that make building software unnecessarily difficult. You understand the challenges AWS developers face today and collaborate with team members to simplify the AWS developer experience. You have experience contributing to complex software development initiatives. You’ll strive for simplicity and will demonstrate significant creativity." Basic Qualifications list: many lines. Let's extract them: - 3+ years of non-internship professional software development experience - 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience - 1+ years of software development engineer or related occupational experience - 1+ 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 - 1+ years of Object Oriented Design 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 - 3+ years of programming using a modern programming language such as Java, C++, or C#, including object-oriented design experience - 4+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience - 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 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 - Experience building services using AWS products - Experience with software development lifecycle - Experience developing, deploying and managing AI products at scale Benefits: paragraph: "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." 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. USA, WA, Seattle - 143,700.00 - 194,400.00 USD annually" Schedule: Not mentioned. So we should not include Schedule section. We also have "Company - Amazon Development Center U.S., Inc." maybe minor metadata; we can fold into a short p or drop. Probably include as a short p under About the role? But we can drop as minor metadata. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we need to decide what goes where. Typically: - About the role: description paragraph. - Responsibilities: Key job responsibilities + Unique Opportunities + A day in the life? Actually A day in the life could be part of responsibilities or maybe Skills? But we can treat as Responsibilities. - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe combine some skill statements? Could include "Experience building services using AWS products", "Experience with software development lifecycle", "Experience developing, deploying and managing AI products at scale". Those are preferred qualifications though. Might be better to put them under Skills. But we need to avoid duplication. Let's map: About the role: the initial description paragraph. Responsibilities: combine Key job responsibilities, Unique Opportunities, A day in the life (maybe as responsibilities). We'll list bullet points. Requirements: Basic Qualifications (list). Qualifications: Preferred Qualifications (list). Skills: maybe we can extract skill-specific statements not already covered: "You should have deep expertise in the architecture and business use of AWS technologies." "You recognize the transformative potential of generative AI..." etc. But those are more like responsibilities. Might be better to not create Skills if no distinct content. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if not enough distinct content. But we need to include sections only when posting has real specific content. We have content for Skills? There's "You should have deep expertise in the architecture and business use of AWS technologies." etc. That's more like qualifications. Could be part of Requirements or Qualifications. I'd rather not create Skills section. Benefits: we have benefits paragraph. Pay: we have salary range and sign-on payments. Schedule: none, omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now format:

About the role

...

Responsibilities

• Identify and prioritize high-impact problems that impede AWS software development
• Decompose complex builder problems into simple, straightforward and scalable solutions
• Collaborate with AWSBA, ASBX and AWS builder teams to build and operate the designed solutions
• Deliver meaningful improvements weekly while working toward long-term transformation
• Re-imagine how developers build and operate the software that underpins the world's largest cloud
• Drive significant transformation across AWS engineering
• Pioneer the use of cutting-edge generative AI technologies to create the next generation of builder experiences
• You should have deep expertise in the architecture and business use of AWS technologies
• Recognize the transformative potential of generative AI in software development and are excited to pioneer AI-powered builder experiences that fundamentally change how developers write, debug, deploy and operate code at scale
• Remain technically hands-on and close to the technology
• Be passionate about developer experience and get frustrated by inefficiencies that make building software unnecessarily difficult
• Understand the challenges AWS developers face today and collaborate with team members to simplify the AWS developer experience
• Have experience contributing to complex software development initiatives
• Strive for simplicity and demonstrate significant creativity

But some of those are more like qualifications. Might be too many. However we need to preserve all substantive info. The A day in the life paragraph contains many statements; we should preserve them. Could we keep them as a paragraph instead of list? The rule: Use

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

  for prose. The A day in the life is prose, not a list. So we could keep it as a

  under Responsibilities? But the rule says use

  • for any list of duties/requirements/benefits. It doesn't forbid using

    for prose within a section. So we could have a

    for the A day in the life paragraph, and a

    for the bullet lists. Thus Responsibilities section could contain:

    Key job responsibilities:

    ...

    Unique Opportunities:

    ...

    A day in the life:

    ...

    But we need to avoid repeating headings inside. It's okay. Now Requirements: Basic Qualifications list. We'll output as
    • each line. Qualifications: Preferred Qualifications list. Benefits:

      with benefits paragraph. Pay:

      with salary range and sign-on payments. We must not include boilerplate like EEO, accommodation, etc. Also remove "Learn more about our benefits at https://..." maybe that's okay as it's part of benefits? It's a link; we could keep but it's not substantive? Might be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly boilerplate but could be considered navigation? It's a link to learn more; maybe we can keep but it's not essential. Safer to omit the link and just keep the benefits description. Thus benefits paragraph: "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." Pay paragraph: "The base salary