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

We need to output HTML fragment with headings

for 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 need to extract: - About the role: description of team, mission, etc. - Responsibilities: list of key job responsibilities. - Requirements: Basic Qualifications? Possibly separate Basic Qualifications and Preferred Qualifications. The instruction: Use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We have Basic Qualifications (mandatory) and Preferred Qualifications (nice-to-have). Could map Basic Qualifications to "Requirements" and Preferred Qualifications to "Qualifications" or "Skills". Also we have knowledge of programming languages etc. We also have Benefits: described in paragraph about benefits (health insurance, 401k, PTO, parental leave). Also mention sign-on payments and RSUs. Pay: salary ranges listed for various locations. Should we include Pay section? Yes, we have specific salary ranges. So include Pay. Schedule: Not mentioned explicitly; maybe flexible hours to support global customers. There's phrase: "Collaborate across ... operating with flexible hours to support global customers and distributed stakeholders." That indicates schedule flexibility. Could include Schedule section with that detail. We must not include boilerplate like EEO, equal opportunity, scam warning, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove Job ID, requisition numbers as headings; we can fold minor metadata into short p or drop it. So we can maybe include a short p with Job ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a

with Job ID: A10564102 maybe. But it's minor metadata; we could drop it. Safer to drop. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications details, benefits details, pay ranges, schedule note. We must not create sections with filler like "commensurate with experience". We have actual content. Thus sections: - About the role: paragraph(s) describing team, mission, impact. - Responsibilities: ul li list of responsibilities. - Requirements: Basic Qualifications (list). Could be ul li. - Qualifications: Preferred Qualifications (list). Could be ul li. - Skills: maybe programming languages knowledge? Could be part of Requirements. But we already have programming languages in Basic Qualifications. Could create Skills section for "Knowledge of at least two of the following programming languages: Scala, Java, Python, C/C++, or Go". But that's already in Basic Qualifications. Might be redundant. Better to keep Basic Qualifications as Requirements, and Preferred Qualifications as Qualifications. Skills maybe not needed. - Benefits: paragraph describing benefits. - Pay: list of salary ranges per location. - Schedule: note about flexible hours. We must not repeat job title as heading. The job title is Senior Security Engineer; we don't add heading for that. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine first paragraphs: "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." Then Opportunity paragraph: "The Opportunity 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." We could combine About the role and Opportunity into one section "About the role". Probably fine. Responsibilities: list from "Key job responsibilities": 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. We'll put each as

. Requirements (Basic Qualifications): list each bullet: - 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 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 We'll put as

• . Qualifications (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 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 We'll put as
  • . Skills: maybe not needed; we could omit. Benefits: paragraph: "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'll put as

    . Pay: list salary ranges: - USA, CA, Santa Clara - 183,000.00 - 247,600.00 USD annually - USA, TX, Austin - 178,400.00 - 226,700.00 USD annually - USA, VA, Arlington - 178,400.00 - 226,700.00 USD annually - USA, WA, Bellevue - 178,400.00 - 226,700.00 USD annually - USA, WA, Seattle - 178,400.00 - 226,700.00 USD annually We'll put as

    • . Schedule: note about flexible hours: "Collaborate across science, engineering, partner, and field teams, operating with flexible hours to support global customers and distributed stakeholders." Already in responsibilities but we can still have schedule section: maybe just that sentence. We'll put as

      . We must not repeat content unnecessarily but it's okay. Now ensure we don't include boilerplate: remove EEO, Los Angeles County specifics, accommodation links, etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10564102". We can drop Job ID. Now produce HTML. Let's craft:

      About the role

      ... combined paragraphs ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Qualifications

      • ...
      ...

      Benefits

      ...

      Pay

      • ...
      ...

      Schedule

      Collaborate across science, engineering, partner, and field teams, operating with flexible hours to support global customers and distributed stakeholders.

      Make sure no extra whitespace issues. Now craft the About the role paragraph: combine the initial description and Opportunity paragraph. Let's write succinctly but preserve all details. 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. The Opportunity 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