Sr. Security Engineer, Field Innovation, Security Search and Observability (SSO)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Use

for headings. Use

• for lists. Use

  for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. Include only sections with real content. We need to parse the description. First paragraph: Description: The Field Innovation team is a Forward Deployed Engineering (FDE) group inside the AWS Security, Search, Observability, and Governance service team. We work directly with customers to build next-generation security capabilities that help the world's largest enterprises get faster return on value from security, search, observability, and governance services. We are hiring a Senior Security Engineer to work at the intersection of customer impact and AI. Our team builds and operates the detection, correlation, and vulnerability-management capabilities behind security services such as AWS Security Hub, AWS CloudTrail, and AWS GuardDuty, as well as our newest AI-powered offering, AWS Continuum, which manages the full lifecycle of code vulnerabilities at machine speed. You'll work with customers to understand how they operate, then partner with service teams to design and ship commercial-grade security products powered by modern AI, including large language models, AI-assisted development tools, security agents, and emerging frameworks. Your code ships to real customers, and your architectural decisions will shape how Fortune 500 companies operate. That's about the role. Then "The Opportunity" paragraph: Your impact here will be immediate and visible. You'll ship features that directly change how customers run their businesses, and you'll see the impact of your work in weeks, not years. The team is small enough that your decisions carry real weight and large enough that you'll always have someone to learn from. This is a dual-facing role. On the field side, you'll work directly with customers to implement the latest features of our security services, leading threat-modeling sessions, performing vulnerability assessments with security agents, and guiding remediation. On the partner side, you'll work with leading third-party security providers to identify their highest-signal findings and turn them into correlated, high-fidelity detections. Across both, you'll design and implement detection content, reduce false positives at scale, and expand coverage across cloud resources, runtime, and AI/ML workloads. Everything you learn in the field feeds back into the product. AI is not a side experiment on this team. It's a core part of the stack. You'll build with large language models, AI-assisted development tools, security agents, agent frameworks, and retrieval-augmented generation as everyday engineering primitives. That's also about role. Then "Key job responsibilities" list: bullet points: - Run early-access and gated previews of our newest AI-powered capabilities with customers, including threat modeling, vulnerability assessment using security agents, and remediation guidance. - Work backwards from customers to shape detection coverage and influence service roadmaps, feeding field and partner insights back to science and engineering teams. - Drive detection engineering best practices, including security-value evaluation, false-positive reduction, and coverage measurement. - Stay current with the evolving cloud security and threat landscape, including emerging threats targeting agentic AI and ML applications. - Collaborate across science, engineering, partner, and field teams, operating with flexible hours to support global customers and distributed stakeholders. That's responsibilities. Then "Basic Qualifications" list: each line seems a qualification. Let's extract: - 5+ years of non-internship background in troubleshooting systems issues, analyzing logs, or automating complex tasks using command line tools experience - 5+ years of work in identifying security issues and risks, and developing mitigation plans experience - 5+ years of (non-internship) scripting, programming, and security code review in common programming languages experience - Knowledge of at least two of the following programming languages: Scala, Java, Python, C/C++, or Go - Experience (non-internship) in industry-based security vulnerabilities identification, attack patterns, and remediation techniques - Experience as a mentor, tech lead or leading an engineering team - Bachelor's degree in Computer Science or a related field These are qualifications. Then "Preferred Qualifications" list: - 5+ years of any combination of the following: application security frameworks, identity and access controls, incident response, mobile security, cloud computing and security, AI security, threat intelligence, and penetration testing experience - Experience architecting, securing, and operating Amazon Web Services - Experience in the full secure software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations - Experience working in a customer-facing role These could be considered "Skills" or "Preferred Qualifications". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to map. We have "Basic Qualifications" and "Preferred Qualifications". Could combine into "Qualifications" (basic) and "Preferred Qualifications" maybe as "Skills"? But we have separate "Skills" section possible. However we should not create thin sections. Perhaps we can have "Qualifications" covering both basic and preferred? Or we could have "Requirements" for basic qualifications and "Preferred Qualifications" as "Skills". The instruction: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Qualifications (including basic and preferred), Benefits, Pay, Schedule. But we need to include Benefits and Pay only if posting actually states them. The posting includes salary ranges for various locations and mentions benefits: "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." Thus we have Pay (salary ranges) and Benefits (description). So we should include Pay and Benefits sections. Schedule: Not mentioned explicitly except "operating with flexible hours to support global customers and distributed stakeholders." That's a mention of flexible hours but not a defined schedule. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention flexible hours but not a specific schedule. Might be considered schedule info? It's vague. Probably we should not create a Schedule section because no explicit schedule like "Full-time", "Part-time", "Shift work". The phrase "operating with flexible hours" is not a defined schedule. Safer to omit Schedule. Thus sections: About the role, Responsibilities, Qualifications (maybe split into Requirements and Preferred Qualifications?), Benefits, Pay. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have basic qualifications (requirements) and preferred qualifications (maybe skills). Could map: - Requirements: Basic Qualifications - Skills: Preferred Qualifications (or maybe combine with Qualifications). But we have both Qualifications and Skills headings available. Could put Requirements for basic, Skills for preferred. Or Qualifications for basic and Skills for preferred. Let's decide. We have "Requirements" heading: could be used for basic qualifications (must-have). "Skills" heading: could be used for preferred qualifications (nice-to-have). "Qualifications" heading maybe redundant. But we can include both Requirements and Skills. Thus:

  About the role

  with paragraphs from description.

  Responsibilities

  with
  • list.

    Requirements

    with
    • list of basic qualifications.

      Skills

      with
      • list of preferred qualifications.

        Benefits

        with

        describing benefits.

        Pay

        with

        showing salary ranges (maybe list locations). Could present as

        • each location range. We must not include boilerplate like EEO, etc. Also remove duplicated lines. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from basic qualifications, preferred qualifications, responsibilities, about the role, benefits, pay. We must not repeat job title as heading. Not include Job ID. We must not include navigation etc. Now craft HTML. We need to ensure we use

          for each section heading. Use

          • for lists. Use

            for prose. We must not include markdown code fences. Let's extract the About the role text: combine the first two paragraphs (Description and The Opportunity) maybe as one section. We'll write:

            The Field Innovation team is a Forward Deployed Engineering (FDE) group inside the AWS Security, Search, Observability, and Governance service team. We work directly with customers to build next-generation security capabilities that help the world's largest enterprises get faster return on value from security, search, observability, and governance services. We are hiring a Senior Security Engineer to work at the intersection of customer impact and AI. Our team builds and operates the detection, correlation, and vulnerability-management capabilities behind security services such as AWS Security Hub, AWS CloudTrail, and AWS GuardDuty, as well as our newest AI-powered offering, AWS Continuum, which manages the full lifecycle of code vulnerabilities at machine speed. You'll work with customers to understand how they operate, then partner with service teams to design and ship commercial-grade security products powered by modern AI, including large language models, AI-assisted development tools, security agents, and emerging frameworks. Your code ships to real customers, and your architectural decisions will shape how Fortune 500 companies operate.

            Your impact here will be immediate and visible. You'll ship features that directly change how customers run their businesses, and you'll see the impact of your work in weeks, not years. The team is small enough that your decisions carry real weight and large enough that you'll always have someone to learn from. This is a dual-facing role. On the field side, you'll work directly with customers to implement the latest features of our security services, leading threat-modeling sessions, performing vulnerability assessments with security agents, and guiding remediation. On the partner side, you'll work with leading third-party security providers to identify their highest-signal findings and turn them into correlated, high-fidelity detections. Across both, you'll design and implement detection content, reduce false positives at scale, and expand coverage across cloud resources, runtime, and AI/ML workloads. Everything you learn in the field feeds back into the product. AI is not a side experiment on this team. It's a core part of the stack. You'll build with large language models, AI-assisted development tools, security agents, agent frameworks, and retrieval-augmented generation as everyday engineering primitives.

            That seems fine. Now Responsibilities list: - Run early-access and gated previews of our newest AI-powered capabilities with customers, including threat modeling, vulnerability assessment using security agents, and remediation guidance. - Work backwards from customers to shape detection coverage and influence service roadmaps, feeding field and partner insights back to science and engineering teams. - Drive detection engineering best practices, including security-value evaluation, false-positive reduction, and coverage measurement. - Stay current with the evolving cloud security and threat landscape, including emerging threats targeting agentic AI and ML applications. - Collaborate across science, engineering, partner, and field teams, operating with flexible hours to support global customers and distributed stakeholders. Make
            • . Now Requirements (basic qualifications) list: - 5+ years of non-internship background in troubleshooting systems issues, analyzing logs, or automating complex tasks using command line tools - 5+ years of work in identifying security issues and risks, and developing mitigation plans - 5+ years of (non-internship) scripting, programming, and security code review in common programming languages - Knowledge of at least two of