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. Only include sections if posting has real specific content. We need to extract content. From description: It's a job posting. Let's parse. First paragraph: Description about team. Could be "About the role". We'll put that as prose

. Then "The Opportunity" maybe part of description. Could be included in About the role. Then "Key job responsibilities" list bullet points. We'll create

Responsibilities

with

• each. Then "Basic Qualifications" list bullet points. We'll create

  Requirements

  maybe. Also "Preferred Qualifications" could be

  Qualifications

  or Skills. We need to decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have content for About the role (description). Responsibilities (key job responsibilities). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills maybe not explicit separate; could combine with qualifications. Benefits: there is mention of benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also mention sign-on payments and RSUs. So we have benefits content. Pay: there is base salary range listed for multiple locations. So we have pay content. Schedule: not mentioned explicitly. There's "operating with flexible hours to support global customers". That's schedule info? Could be considered schedule. But it's vague. The instruction: never create Schedule section unless posting actually states them. It says "operating with flexible hours to support global customers and distributed stakeholders." That's about flexible hours. Might be considered schedule. But it's not explicit schedule like "full-time", "shift". Might be considered schedule info. However it's not a clear schedule; but we could include Schedule section with that sentence. However the rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Flexible hours is not placeholder. So we could include Schedule. But we need to decide if we want to include Schedule. The posting says: "Collaborate across science, engineering, partner, and field teams, operating with flexible hours to support global customers and distributed stakeholders." That's about flexible hours. So we can put that under Schedule. Now Benefits: we have description of benefits. Also mention sign-on payments and RSUs. We'll include. Now Pay: we have base salary ranges for multiple locations. We'll list them. Now we need to avoid repeating job title as heading. Not needed. We must not include boilerplate like EEO, equal opportunity, scam warning, legal, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can reformat into HTML. We need to ensure we don't lose any substantive info. Let's extract. About the role: The first paragraph(s) up to "The Opportunity". Let's capture: "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 "The 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 these into About the role section. Now Responsibilities: "Key job responsibilities" bullet 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. Note the last bullet includes flexible hours; we might move that to Schedule. But it's part of responsibilities list. However we could keep it there and also have Schedule section referencing flexible hours? Might duplicate. Better to keep flexible hours under Responsibilities as it's part of collaboration. Then Schedule section maybe not needed. But we have no explicit schedule info besides flexible hours. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state flexible hours, which is schedule-related. So we could create Schedule section with that sentence. However that sentence also appears in responsibilities. If we move it to Schedule, we would be removing from responsibilities, losing content. We could keep it in responsibilities and also have Schedule section referencing flexible hours? That would duplicate content. The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to keep it only once. Since it's part of responsibilities, we could keep it there and not create Schedule section. But then we would not have a Schedule section despite having schedule-related content. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must create them if they exist; we can choose not to create them if we prefer fewer sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Schedule section and keep flexible hours under Responsibilities. That seems acceptable. Now Requirements: Basic Qualifications bullet list (some duplicated). Let's extract unique points: - 3+ years of scripting, programming, and security code review in a common programming language (non-internship) experience - 3+ years of troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non-internship) experience - 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 - Experience in scripting, programming, and security code reviewing in a common programming language (non-internship) (duplicate of first) - Experience in troubleshooting systems issues, analyzing logs, or automating basic tasks using command line tools (non-internship experience) (duplicate) We should preserve all substantive information; duplicates are part of posting. We could keep them as is, but maybe we can deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing duplicates could be considered summarizing away detail? It's removing redundant info, which could be considered summarizing. Safer to keep duplicates as they appear. However we can keep them but note they are duplicated; but we could keep both lines. It's okay. Now Preferred Qualifications bullet list: - 3+ years of any combination of the following: threat modeling experience, secure coding, identity management and authentication, software development, cryptography, system administration and network security experience - 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 Now Benefits: paragraph after "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 should keep that. Now Pay: 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. Then list: USA, CA, Santa Clara - 166,600.00 - 212,800.00 USD annually USA, TX, Austin - 159,300.00 - 202,400.00 USD annually USA, VA, Arlington - 159,300.00 - 202,400.00 USD annually USA, WA, Bellevue - 159,300.00 - 202,400.00 USD annually USA, WA, Seattle - 159,300.00 - 202,400.00 USD annually We need to include Pay section. Now we need to output HTML fragment with headings

  and appropriate

  • for lists,

    for prose. We must not include any extra text like explanations. Let's craft. Structure:

    About the role

    ... (combined description)

    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