Security Engineer, Field Innovation, Security Search and Observability (SSO)
for each section. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which content is list vs prose.
Sections:
- About the role: prose (maybe multiple paragraphs). We'll put in
.
- Responsibilities: list of duties (the bullet points). We'll make
- each.
- Requirements: could be Basic Qualifications (maybe call Requirements). We'll list as
- .
- Qualifications: Preferred Qualifications list.
- Skills: maybe combine some? But we have no explicit skills section; we could skip if no specific content. The instruction: prefer a few substantive sections over many thin ones. We could merge Basic and Preferred into Requirements and Qualifications. Skills maybe not needed.
- Benefits: list.
- Pay: list of salary ranges (maybe
- each location).
- Schedule: prose about flexible hours.
We must not repeat job title as heading. Not include Job ID.
We must not include boilerplate like EEO, accommodation, Los Angeles County details, etc.
We must not include duplicated lines.
Now craft HTML.
Let's write:
About the role
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.
Responsibilities
- 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.
Requirements
- 3+ years of scripting, programming, and security code review in a common programming language (non-internship)
- 3+ years of troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non-internship)
- Bachelor's degree in a STEM field (Science, Technology, Engineering, Mathematics), or 3+ years of IT Security experience
- Knowledge of industry-based security vulnerabilities and remediation techniques
Qualifications
- 3+ years of any combination of: threat modeling experience, secure coding, identity management and authentication, software development, cryptography, system administration and network security
- Experience with AWS products and services
- Experience in scripting, programming, or security code reviewing in a common language, such as Python, Java, or C++
- Experience performing security activities across one or more phases of the software development lifecycle (SDLC), such as security design review, threat modeling, secure code review, and security testing
- Experience working in a customer-facing role
for prose. We need to decide which content is list vs prose. Sections: - About the role: prose (maybe multiple paragraphs). We'll put in
. - Responsibilities: list of duties (the bullet points). We'll make
- each.
- Requirements: could be Basic Qualifications (maybe call Requirements). We'll list as
- .
- Qualifications: Preferred Qualifications list.
- Skills: maybe combine some? But we have no explicit skills section; we could skip if no specific content. The instruction: prefer a few substantive sections over many thin ones. We could merge Basic and Preferred into Requirements and Qualifications. Skills maybe not needed.
- Benefits: list.
- Pay: list of salary ranges (maybe
- each location).
- Schedule: prose about flexible hours.
We must not repeat job title as heading. Not include Job ID.
We must not include boilerplate like EEO, accommodation, Los Angeles County details, etc.
We must not include duplicated lines.
Now craft HTML.
Let's write:
About the role
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.
Responsibilities
- 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.
Requirements
- 3+ years of scripting, programming, and security code review in a common programming language (non-internship)
- 3+ years of troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non-internship)
- Bachelor's degree in a STEM field (Science, Technology, Engineering, Mathematics), or 3+ years of IT Security experience
- Knowledge of industry-based security vulnerabilities and remediation techniques
Qualifications
- 3+ years of any combination of: threat modeling experience, secure coding, identity management and authentication, software development, cryptography, system administration and network security
- Experience with AWS products and services
- Experience in scripting, programming, or security code reviewing in a common language, such as Python, Java, or C++
- Experience performing security activities across one or more phases of the software development lifecycle (SDLC), such as security design review, threat modeling, secure code review, and security testing
- Experience working in a customer-facing role
- each location).
- Schedule: prose about flexible hours.
We must not repeat job title as heading. Not include Job ID.
We must not include boilerplate like EEO, accommodation, Los Angeles County details, etc.
We must not include duplicated lines.
Now craft HTML.
Let's write:
- .
- Qualifications: Preferred Qualifications list.
- Skills: maybe combine some? But we have no explicit skills section; we could skip if no specific content. The instruction: prefer a few substantive sections over many thin ones. We could merge Basic and Preferred into Requirements and Qualifications. Skills maybe not needed.
- Benefits: list.
- Pay: list of salary ranges (maybe