Systems Development Engineer I

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 extract content. From description: There's a lot of prose about role, responsibilities, etc. We need to map. We must not repeat job title as heading. No Job ID etc. We need to include sections only if content present. We have: - About the role: The description includes introductory paragraphs about designing cloud solutions, etc. Could be considered About the role. - Responsibilities: "Key job responsibilities" section with bullet points: improving lives through tools, processes, documentation; learning SRE fundamentals; etc. Also "A day in the life" maybe responsibilities. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: Could be extracted from qualifications? Might combine but we need separate sections if content. - Benefits: The posting mentions benefits: comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also sign-on payments and RSUs. So we have benefits. - Pay: Salary ranges listed for multiple locations. So we have Pay. - Schedule: Not mentioned. No schedule info. So omit Schedule. We must not include placeholder like "commensurate with experience". The pay section includes specific ranges, good. We must not include boilerplate like EEO etc. Remove those. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep the details as given, but we can format as lists. We need to use

for section headings. Use

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

  for prose. We must output only HTML fragment. Let's craft sections:

  About the role

  ... prose describing role ...

  We need to include the introductory paragraphs that describe the role: "Would you like to design, develop, and implement innovative cloud computing solutions...". Also mention AWS specialized group, etc. We'll combine into a paragraph. We must not repeat job title. We need to ensure we keep all substantive info: mention TS/SCI clearance requirement, etc. That could be in Requirements or Qualifications. Let's extract: About the role: The first few paragraphs up to "Key job responsibilities". Let's capture: "Would you like to design, develop, and implement innovative cloud computing solutions and solve the world's most complex technical problems? Do you have a deep passion and desire to engineer and operate the world's largest cloud computing infrastructure to build a better world for future generations? This is an exciting opportunity to use the latest cloud computing technologies to help US government agencies implement innovative cloud computing solutions and solve technical problems. AWS established a specialized group of service teams responsible for the work we are doing with the US Intelligence Community. We are building some of the largest and most complex distributed systems in the world, and we need adaptable people to help us implement and operate them, and expand capabilities with the speed of relevance. You'd work with some of the best and brightest engineers in the industry, while also developing your skills and furthering your career within one of the most innovative and progressive technology companies anywhere. Amazon Web Services is seeking top industry technical experts to grow our team dedicated to expanding our Elastic Compute Cloud (EC2) to government customers. We are seeking a talented engineer skilled in the art of integration who understands the Agile mindset and DevOps philosophies, yet is not constrained by how "things are usually done" and is willing to decompose and reinvent systems, processes, and tools. We're looking for a technical practitioner for one of the largest compute services on the planet; if you possess that rare mix of skills in Operations, Networking, and Systems Engineering, then we are waiting for your application. We are looking for smart, enthusiastic, and creative engineers with a solid background in solving hard problems that span the software development, systems engineering, and systems security disciplines. As a member of this team, you will be charged with identifying ways to improve the lives of our customers through improvements to tools, processes, and documentation. You will be a member of a team of highly motivated and talented systems developers and systems engineers improving the use of tools in both isolated AWS regions and in the AWS GovCloud regions. This position requires that the candidate selected must currently possess and maintain an active TS/SCI security clearance. The position further requires that, after start, the selected candidate obtain and maintain an active TS/SCI security clearance with polygraph or commensurate clearance for each government agency for which they perform AWS work." That is a lot; we can keep as prose. Responsibilities: The "Key job responsibilities" section: "As a member of this team, you will be charged with identifying ways to improve the lives of our customers through improvements to tools, processes, and documentation, while working alongside talented systems developers and systems engineers across isolated AWS regions and the AWS GovCloud regions. You will also be learning site reliability engineering fundamentals: recognizing toil, the manual, repetitive work that produces no lasting improvement, contributing code and automation that removes it, and coming to understand your systems' normal performance envelope well enough to tune alarms that catch real problems." Also "A day in the life" maybe part of responsibilities but could be separate? But we can include as responsibilities. We could also include "A day in the life" description: "Amazon has a fast-paced environment where we "Work Hard, Have Fun, Make History." On a "typical" day, engineers might deep dive to root cause a customer issue, investigate why a metric is trending the wrong way, consult with the top engineers at Amazon, or discuss radical new approaches to automate operational issues." We can include that as responsibilities. Thus responsibilities list: bullet points? The text is prose; we can keep as

  . But rule: Use

  • for any list of duties/requirements/benefits. If not a list, we can use

    . The responsibilities are not explicitly a list; we can keep as paragraphs. Requirements: Basic Qualifications list: - Associate's degree or above, or CND (Certified Network Defender) or GSEC (GIAC Security Essentials) - Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby - 1+ years of working in a Linux/Unix environment - Experience with automating and simplifying team development, test, and operations processes - Current, active US Government Security Clearance of TS/SCI with Polygraph We should keep as

    • . Qualifications: Preferred Qualifications list: - 3+ years of programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby - 3+ years of cloud computing technologies experience - 3+ years of Linux/Unix systems experience - 3+ years of multithreaded, distributed development experience - Working knowledge of TCP/IP networking and core web technologies, such as DNS, HTTP, TLS/SSL certificates, and session and cookie handling - Working knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems We'll put as
      • . Skills: Could be derived from qualifications? Might be redundant. But we could create a Skills section summarizing technical skills: programming languages, Linux/Unix, networking, config management, etc. However we must not invent or summarize away detail; we could just repeat the qualifications as skills? Might be duplication but allowed? The instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Qualifications? But they asked to use sections if posting has real specific content for it. The posting does not have a separate "Skills" heading; but we could still create a Skills section if we have content. However we risk creating thin section. Better to omit Skills if not explicitly present. The posting includes qualifications but not a separate Skills heading. We'll omit Skills. Benefits: The posting mentions: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." We need to preserve all substantive info. We'll put as
        • list. Pay: Salary ranges for multiple locations. We'll list each location with range. Could be a
          • each. Schedule: Not present, omit. We must not include boilerplate like EEO, accommodation links, etc. Remove those. We also need to remove duplicated lines, navigation, cookie, legal, etc. We'll ignore. Now craft HTML. We need to ensure we don't include markdown fences. Let's produce:

            About the role

            ... (the paragraph) ...

            Responsibilities

            ... (maybe two paragraphs) ...

            Requirements

            • Associate's degree or above, or CND (Certified Network Defender) or GSEC (GIAC Security Essentials)
            • Experience programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
            • 1+ years of working in a Linux/Unix environment
            • Experience with automating and simplifying team development, test, and operations processes
            • Current, active US Government Security Clearance of TS/SCI with Polygraph

            Qualifications

            • 3+ years of programming with at least one modern language such as C++, C#, Java, Python, Golang, PowerShell, Ruby
            • 3+ years of cloud computing technologies experience
            • 3+ years of Linux/Unix systems experience
            • 3+ years of multithreaded, distributed development experience
            • Working knowledge of TCP/IP networking and core web technologies, such as DNS, HTTP, TLS/SSL certificates, and session and cookie handling
            • Working knowledge of configuration management systems, such as Puppet, Chef, Ansible, or related systems

            Benefits

            • Sign-on payments and restricted stock units (RSUs)
            • Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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

            Pay

            • USA, CO, Denver: $99,100.00 - $160,000.00 USD annually
            • USA, MD, Annapolis Junction: $99,100.00 - $160,000.00 USD annually
            • USA, VA, Arlington: $99,100.00 - $160,000.00 USD annually
            • USA, VA, Herndon: $99,100.00 - $160,000.00 USD annually
            • USA, WA, Bellevue: $99,100.00 - $160,000.00 USD annually
            • USA, WA, Seattle: $99,100.00 - $160