Senior Software Development Engineer, AWS Quick

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the description. Key sections: - Description: AWS Context description, team, etc. Could be "About the role" maybe. - About The Team: details about team, mentorship, etc. - Diverse Experiences: statement about encouraging applicants. - About AWS: description of AWS. - Inclusive Team Culture: details. - Work/Life Balance: details. - Mentorship & Career Growth: details. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: description of benefits (health insurance, 401k, PTO, parental leave). Also mention base salary range. - Pay: base salary range. - Schedule: not mentioned. We need to decide which sections to include. We have content for: - About the role: Could be the initial description about AWS Context, team, mission, etc. That seems appropriate. - Responsibilities: Not explicitly listed. There's no bullet list of duties. Might not include. - Requirements: Could be Basic Qualifications? But they ask separate sections: Requirements, Qualifications, Skills. Usually Requirements = basic qualifications. Qualifications = preferred qualifications. Skills maybe not separate. We could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. Skills maybe not present; we could omit. - Benefits: we have benefits description. - Pay: base salary range. - Schedule: not present, omit. We also have sections like About The Team, About AWS, Inclusive Team Culture, Work/Life Balance, Mentorship & Career Growth, Diverse Experiences. Those could be part of About the role or separate sections? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should use those headings only. So we must map content to those headings. Not allowed to create other headings like About The Team etc. So we need to fit all substantive info under those headings. Thus we need to decide which headings to include based on content. We have content for About the role (description of role, team, mission). Could include details about team, AWS, inclusive culture, work-life balance, mentorship, diverse experiences. All could go under About the role. Responsibilities: none specific, so omit. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Skills: maybe not present; we could omit if no specific skills listed. Could we extract skills from qualifications? But better to omit if no explicit skills. Benefits: we have benefits description. Pay: base salary range. Schedule: none. Thus output HTML with sections: About the role, Requirements, Qualifications, Benefits, Pay. We need to use

• for any list of duties/requirements/benefits. So for Requirements and Qualifications we need lists. For Benefits also list. We need to preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, accommodation link, etc. Must remove duplicated lines. We need to include the base salary range: "USA, WA, Bellevue - 168,100.00 - 227,400.00 USD annually". Also mention sign-on payments and RSUs? That's part of compensation but not base salary; could be included in Pay section maybe. The instruction: include Pay section only if posting actually states them. It does state base salary range. Also mentions sign-on payments and RSUs. We could include that as part of Pay. We must not include Job ID. We must not include application instructions. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Thus we need to strip those. Let's extract substantive paragraphs: From description: "AWS Context is a new AWS service that gives AI agents access to an organization's context through a governed knowledge graph. It is the foundational layer that enables enterprise AI systems to reason over business data — connecting agents to the right context, at the right time, with the right governance controls. AWS Context sits at the heart of Amazon's AI strategy: without grounding in real organizational data, AI agents are generic. With it, they become genuinely useful. The team is working towards launching the first release of AWS Context. We move fast, ship often, and iterate fast on customer feedback. You won't wait for quarterly planning cycles to make decisions — the team ships, learns, and adjusts in days, not months. We value engineering leaders who thrive in ambiguity, bias strongly toward action, and build a culture where failing fast is a feature, not a bug. If you've run a scrappy team that punched above its weight, you'll feel at home here. This is a high-visibility engineering leadership role at the intersection of frontier AI, large-scale data systems, and customer-facing agentic products. You will lead a team of SDEs in Seattle/Bellevue building systems that process billions of queries, ship agentic features used by AWS customers globally." That's role description. About The Team: "Our team is dedicated to supporting new members. We have a broad mix of experience levels and tenures, and we’re building an environment that celebrates knowledge-sharing and mentorship. Our senior members enjoy one-on-one mentoring and thorough, but kind, code reviews. We care about your career growth and strive to assign projects that help our team members develop your engineering expertise so you feel empowered to take on more complex tasks in the future." Diverse Experiences: "AWS values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." About AWS: "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." Inclusive Team Culture: "Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences, inspire us to never stop embracing our uniqueness." Work/Life Balance: "We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud." Mentorship & Career Growth: "We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional." Basic Qualifications: "5+ years of non-internship professional software development experience 5+ years of programming with at least one software programming language experience 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience Experience as a mentor, tech lead or leading an engineering team" Preferred Qualifications: "5+ 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: "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, Bellevue - 168,100.00 - 227,400.00 USD annually" We need to include all that. We must not include the link to benefits (maybe we can keep as part of benefits description? It's a link; but it's not boilerplate? It's a reference. Might be okay to keep but it's not substantive detail; but it's part of benefits description. Might keep but it's a URL. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is not substantive but it's part of the posting. Might be okay to keep. However, it's not a list item; it's just a sentence. We could keep as part of benefits paragraph. We must not include EEO etc. Already removed. Now construct HTML. We'll have:

  About the role

  ... (combined paragraphs from role description, team, diverse experiences, AWS, inclusive culture, work-life balance, mentorship)

  But we need to avoid too long paragraph? It's okay. We could split into multiple

  for readability but not required. We must use

  • for any list of duties/requirements/benefits. So for Requirements and Qualifications and Benefits we need lists. Thus:

    Requirements

    • 5+ years of non-internship professional software development experience
    • 5+ years of programming with at least one software programming language experience
    • 5+ years of leading design or architecture (design patterns, reliability and scaling) of new and existing systems experience
    • Experience as a mentor, tech lead or leading an engineering team

    Qualifications

    • 5+ 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 (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

    Learn more about our benefits at https://amazon.jobs/en/benefits

    But the instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. So we can have a

      for the learn more sentence. Pay section:

      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, Bellevue - 168,100.00 - 227,400.00 USD annually

      We should not include schedule. Now About the role section: we need to include all the prose about role, team, diverse experiences, AWS, inclusive culture, work-life balance, mentorship. We'll combine