Systems Development Engineer II, US Amazon Dedicated Cloud Security Engineering

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 that have real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Amazon is an equal opportunity employer..." 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 "Learn more about our benefits at ..."? That's benefits info; we can keep benefits but not the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep benefits description but maybe drop the URL? The URL is part of benefits info; but it's a link; maybe we can keep as plain text? It's not substantive? Might be considered boilerplate? It's a link to benefits page; maybe we can keep but it's not essential. Safer to keep benefits description without the URL. Also remove "Company - Amazon Web Services, Inc." maybe not needed. Also remove "Job ID: A10551991". Also remove "USA, VA, Herndon - 129,200.00 - 174,800.00 USD annually" - that's pay range, we need Pay section. So we need Pay section with that range. Also location maybe not needed. The posting includes location but not required as a section; we could embed in a short p maybe. But we should not create Schedule unless present; not present. Benefits: we have description of benefits. So include Benefits section with that description. Also we have "About The Team" which could be About the role? Actually "About The Team" is a section; we could map to About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role heading for the team description. Responsibilities: we have "Key job responsibilities" list and also "A day in the life". We'll combine into Responsibilities. Requirements: we have Basic Qualifications and Preferred Qualifications. Could split into Requirements (basic) and Qualifications (preferred) or Skills. The instruction says we can use Requirements, Qualifications, Skills. We need to decide. Probably Requirements = Basic Qualifications, Qualifications = Preferred Qualifications, Skills maybe not needed separately. Could also put Skills under Qualifications. We'll include Requirements (Basic Qualifications) and Qualifications (Preferred Qualifications). Also we have "Experience programming with at least one modern language such as Python, Ruby, Golang, Java, C++, C#, Rust" etc. That's skills. Could also have Skills section but we can incorporate into Requirements/Qualifications. To follow instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info: So we need to include all responsibilities list items, all basic qualifications, preferred qualifications, benefits description, pay range, location? Location maybe not needed as a section but we could include as a short p under About the role? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So location could be minor metadata; we could fold into a short p under About the role or maybe drop it. But we should preserve all substantive information; location is substantive? Might be considered metadata but still info. We'll include a short p after About the role heading: "Location: Herndon, VA, USA." That preserves. Now we need to format lists: use

• for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (Basic Qualifications) list. For Qualifications (Preferred Qualifications) list. For Benefits list? Benefits description is prose; we could keep as

  . Could also list bullet points but it's a paragraph; we can keep as

  . For Pay we can have

  with the range. Now we need to ensure we don't include boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove "Diverse Experiences" repeated sections. Also remove "Why Amazon Security?" etc. Also remove "Inclusive Team Culture", "Training & Career Growth", "Work/Life Balance". Those are boilerplate; we should drop them. Also remove "About The Team" heading? We'll convert to About the role. Now let's extract the substantive content. From description: First paragraph: "AWS Security is looking for a driven professional to join its high-security systems engineering team to manage the operation of our physical access control system (PACS), as well as help us automate a sustainable and robust architecture for future growth. As an SysDev, you will be responsible for the overall health and security of our critical service, providing excellent customer service to our partners in a classified environment. Engineers on this team play an integral role in the future of physical security. You will own the integration with enterprise and commodity hardware through proprietary and open source protocols, build extensible management tooling by which customers are delighted, produce infrastructure as code and robust operational monitoring that scales with our growing infrastructure. You will make sure the entire deployment process is performant, automated, and well tested to keep development iteration fast and unhindered by unnecessary operational misses. This position requires that the candidate selected be a US Citizen and must currently possess and maintain an active TS/SCI security clearance with polygraph." That's About the role content. Then "Key job responsibilities" list: - Develop and operate the physical access control system (PACS), ensuring its overall health, availability, and security - Build integrations with enterprise and commodity hardware through proprietary and open source protocols - Develop extensible management tooling and custom APIs for security system integration - Build automation frameworks for infrastructure as code (IaC) deployment and configuration management - Create monitoring and alerting systems to track service health and detect anomalies - Implement secure communication and authentication between distributed systems - Write high-quality, maintainable code and perform peer code reviews - Partner with internal customers to understand operational challenges and deliver solutions Then "A day in the life" paragraph: "You'll spend your day operating and improving the physical access control systems that secure our classified environments. Expect hands-on coding, peer code reviews, and diving into distributed systems to improve reliability, scalability, and security. You'll build infrastructure as code, integrate enterprise and commodity hardware, and develop monitoring and alerting to keep the PACS healthy. You'll automate routine operational work so the team stays fast and agile, and partner directly with internal customers to understand their challenges and deliver practical solutions in a classified environment." We could incorporate that into responsibilities as prose or maybe keep as a separate paragraph under Responsibilities. Since it's descriptive, we can add as a

  after the list. Then "About The Team" paragraph: "The AWS US ADC Security Engineering team builds and operates the high-security systems that protect our classified environments, including the physical access control systems (PACS) at the heart of this role. We work in a fast-paced, multi-disciplinary environment, collaborating with other AWS teams to deliver reliable, secure services for our customers, and we care deeply about security, customer experience, and operational excellence." Then "Amazon Security values diverse experiences, so even if you don't meet every qualification listed, we encourage you to apply. We value work-life harmony and offer flexible arrangements, ongoing learning, and real opportunities for career growth." That's somewhat boilerplate but includes flexible arrangements etc. Might be considered benefits? But we already have Benefits section. Could incorporate flexible arrangements etc into Benefits? But the instruction says only include sections when posting has real, specific content. This is somewhat generic but still specific about flexible arrangements, ongoing learning, career growth. Could be part of Benefits. However we already have a Benefits section with detailed benefits. Might be redundant. Safer to drop that paragraph as it's more generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those but still maybe considered boilerplate. I'd drop it. Then "Diverse Experiences" repeated; drop. "Why Amazon Security?" drop. "Inclusive Team Culture" drop. "Training & Career Growth" drop. "Work/Life Balance" drop. Then "Basic Qualifications" list: - Experience in automating, deploying, and supporting large-scale infrastructure - Experience programming with at least one modern language such as Python, Ruby, Golang, Java, C++, C#, Rust - Experience with Linux/Unix - Experience with CI/CD pipelines build processes - Current, active US Government Security Clearance of TS/SCI with Polygraph Then "Preferred Qualifications" list: - Experience designing, building, operating, and managing large-scale distributed systems or web services - Experience integrating enterprise or commodity hardware through proprietary or open source protocols - Experience building monitoring, alerting, and operational tooling for production systems - Experience with infrastructure as code (IaC) and configuration management Then "Amazon is an equal opportunity employer..." drop. Then "If you have a disability..." drop. Then "If the country/region you’re applying in isn’t listed..." drop. Then "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. Learn more about our benefits at https://amazon.jobs/en/benefits." We need to preserve benefits description: health insurance etc, 401(k) matching, paid time off, parental leave. Also mention sign-on payments and RSUs. Also mention base salary range. Thus Benefits section: we can list those items as a

  • . Also we can mention sign-on payments and RSUs as part of benefits. Pay section: base salary range: USA, VA, Herndon - 129,200.00 - 174,800.00 USD annually. Also mention sign-on payments and RSUs? Those are part of compensation but could be in Benefits. We'll keep Pay as just the range. Now location: we can include a short p under About the role: "Location: Herndon, VA, USA." Now we need to ensure we don't repeat content. Let's craft HTML. Structure:

    About the role

    [first paragraph about AWS Security looking... plus maybe the TS/SCI requirement]

    Location: Herndon, VA, USA.

    Responsibilities

    • Develop and operate the physical access control system (PACS), ensuring its overall health, availability, and security
    • Build integrations with enterprise and commodity hardware through proprietary and open source protocols
    • Develop extensible management tooling and custom APIs for security system integration
    • Build automation frameworks for infrastructure as code (IaC) deployment and configuration management
    • Create monitoring and alerting systems to track service health and detect anomalies
    • Implement secure communication and authentication between distributed systems
    • Write high-quality, maintainable code and perform peer code reviews
    • Partner with internal customers to understand operational challenges and deliver solutions

    You'll spend your