Lead AI Security Engineer - Senior Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description about role (overview), responsibilities (Your Key Responsibilities), skills and attributes (Skills And Attributes For Success), qualifications (To qualify you must have...), benefits (What We Offer You includes compensation and benefits, base salary range, total rewards, vacation policy). Pay: they gave salary ranges. Schedule: not mentioned (no schedule info). So we should include sections: About the role (maybe the introductory paragraph after "The opportunity"? Actually "The opportunity" is a heading but we should not repeat job title; we can treat that as About the role). Use

for each section heading. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there is EEO statement; we should drop that. Also drop "Are you ready to shape your future with confidence? Apply today..." etc (application instructions). Also drop "To make the most of your application experience..." etc. Also drop "EY | Building a better working world" etc. Also drop "EY provides equal employment opportunities..." etc. We need to include Pay section with salary ranges. Benefits section with medical/dental, pension/401k, paid time off, flexible vacation policy, holidays, etc. Schedule: none, so omit. We need to use

• for any list of duties/requirements/benefits. For responsibilities list, we have many bullet-like sentences each starting with a verb. We should convert each to
• . Similarly for Skills and Attributes list, qualifications list, benefits list. We need to preserve all substantive information; we should not lose details. We'll need to parse the responsibilities paragraph: It's a long paragraph with many sentences separated by periods. We'll split into items. Let's extract responsibilities: "Own the platform threat model: covering agent autonomy, tool invocation, delegated authority, model and data supply chain, multi-tenancy, and every deployment target from cloud to air-gapped, and keep it current as the platform evolves through each build phase." "Define the security engineering and control set for every platform layer: infrastructure and boot chain, Kubernetes and cluster fabric, identity and secrets, secure execution and sandboxing, gateway and egress, data and state, delivery pipeline, and telemetry." "Set the secure-by-default contract so that platform capabilities arrive hardened, including agent templates, Helm charts, sandbox profiles, and network policy ship with correct controls rather than requiring teams to add them." "Own defense against agentic threat classes including direct and indirect prompt injection, jailbreak and instruction hijacking, excessive agency, confused-deputy and authority-escalation attacks, tool and function-call abuse, memory and context poisoning, and retrieval-augmented data exfiltration." "Work with the architecture team to help define the agent authority model: delegated and on-behalf-of authority, scope and delegation-depth limits, consent boundaries, and the non-escalation invariant that an agent never exceeds the authority of its initiating principal at any hop." "Own the sandboxing security standard for agent-generated code execution: isolation boundaries, filesystem and credential scope, egress restriction, resource containment, and the escape-test suite that proves the boundary holds." "Secure the model and knowledge supply chain: model provenance and integrity, upstream registry governance, poisoning and backdoor risk, embedding and vector-store integrity." "Secure agent-to-agent and tool protocols including MCP and A2A surfaces: discovery trust, tool registration and approval, schema validation, and authorization of inter-agent calls." "Lead AI red teaming and adversarial testing: build the offensive capability and the recurring exercise cadence that tests guardrails, sandboxes, and authority boundaries before adversaries and auditors do." "Own supply-chain integrity end to end: artifact signing and verification (Sigstore/Cosign, Notation), SBOM generation and attestation, provenance and SLSA-aligned build integrity, CVE management, dependency and license governance." "Own admission and runtime policy: policy-as-code across Kyverno and OPA, signature-verification enforcement, Pod Security Standards, and the guardrails that make non-compliant workloads unschedulable rather than merely reported." "Define Kubernetes and infrastructure hardening baselines: CIS-aligned cluster configuration, network default-deny and segmentation, node and boot-chain integrity, GPU and DPU isolation, and secrets-handling standards." "Own tenant isolation assurance: the security definition of a tenant boundary across compute, network, storage, secrets, telemetry, and evidence, and the testing that proves cross-tenant leakage is not possible." "Serve as the security authority in client engagements: lead security engineering reviews, respond to client CISO and regulator scrutiny, and produce the assurance artefacts that unblock deployment into regulated environments." "Drive security detection and response for the platform: detection engineering for agentic misbehavior, security telemetry requirements, alerting, incident response playbooks, and post-incident review." Now Skills and Attributes For Success list: "Deep cloud-native security expertise: Kubernetes, container, and infrastructure security at production scale, with real operational experience rather than assessment-only exposure." "Genuine command of AI and agentic threat models, with the judgement to distinguish novel risk from familiar risk wearing new vocabulary." "Strong zero-trust and workload-identity foundations: SPIFFE/SPIRE, PKI and certificate lifecycle, secrets management, and delegated authorization patterns." "Fluency in policy-as-code, with the instinct to encode controls as enforced policy rather than documented expectation." "Software supply-chain security depth: signing, provenance, SBOM, and build integrity." "Offensive-security instinct: able to think like an attacker against systems that generate their own code and act autonomously." "Pragmatism about risk: able to distinguish controls that must exist before the first client workload from those that can follow, and to defend both decisions." "Exceptional communication: able to move between a deep technical design review, an executive risk conversation, and a regulator or client CISO discussion without losing precision." "Security-as-enablement mindset: measured by how much safe delivery velocity the controls unlock, not by how much they prevent." Qualifications (To qualify you must have ...): "Bachelor’s or Master’s degree in Computer Science, Security, or a related technical field, or demonstrably equivalent depth." "10+ years in security engineering, security engineering, or offensive security, including hands-on production ownership." "Demonstrable depth in cloud-native and Kubernetes security: admission control, network policy, workload isolation, and runtime security in production." "Hands-on experience with workload identity and secrets management (SPIFFE/SPIRE, Vault/OpenBao or equivalents) and with PKI and certificate lifecycle." "Practical experience securing AI or ML systems in production, including familiarity with LLM and agentic attack surfaces, such as prompt injection, tool abuse, excessive agency, and model or data supply-chain risk." "Threat modelling capability applied to real systems, with evidence that the resulting controls were built and verified." "A track record delivering under compliance, security, or regulatory constraint with audit-grade evidence requirements." "Experience defining ownership boundaries and control contracts with platform, data, runtime, and delivery teams." "Ideally, you'll also have Software supply-chain security experience: artifact signing, SBOM, provenance, and vulnerability management embedded in delivery pipelines." "Policy-as-code experience with OPA, Kyverno, or equivalent admission and authorisation engines." "Experience building or leading an AI red team, or running adversarial testing against LLM and agentic systems." "Familiarity with confidential computing and hardware attestation (Intel TDX, AMD SEV-SNP, SGX, NVIDIA CC) and secure boot / measured boot designs." "Working knowledge of the OWASP Top 10 for LLM Applications, MITRE ATLAS, NIST AI RMF, and the EU AI Act as applied to real engineering." "Experience with LLM guardrail and defense tooling (NeMo Guardrails, LLM Guard, LlamaFirewall, Guardrails AI, or equivalents) in production paths." "Experience securing multi-tenant platforms across cloud, on-prem, edge, client-managed, and air-gapped deployment modes." "Detection engineering and incident response experience, particularly for novel or behavioral threat classes." "Client-facing or consulting background, with credibility in front of CISOs, auditors, and regulators." "Relevant certifications (CISSP, OSCP, GIAC, cloud security specialties) or demonstrable equivalent depth." "Exposure to regulated industries: financial services, tax, audit, healthcare, or public sector." "Contribution to open-source security tooling, research, or public standards work in AI security." Benefits (What We Offer You): "We offer a comprehensive compensation and benefits package where you’ll be rewarded based on your performance and recognized for the value you bring to the business." "The base salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $150,700 to $251,200 Bay Area California offices – $157,100 to $261,600 All other offices locations in the US, including Sacramento – $125,500 to $230,200 Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography." "In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options." "Under our flexible vacation policy, you’ll decide how much vacation time you need based on your own personal circumstances. You’ll also be granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being." We could also include "Learn more at ey.com/us/careers." but that's maybe a link; but it's not boilerplate? It's a link to careers; could be considered part of benefits? Might be okay to keep as a sentence. We should not include application instructions like "Are you ready to shape your future with confidence? Apply today." etc. Now we need to output HTML fragment only. Structure:

  About the role

  ... maybe a paragraph summarizing the opportunity? The posting includes: "At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. The opportunity We are seeking an AI Security Engineer to own the security posture of EY’s Agentic AI platform end to end. Agentic AI breaks the assumptions most enterprise security programs are built on...." That's a lot of prose. We should keep that as paragraph(s). Could split into multiple

  but we can keep as one

  with the content. However we need to avoid repeating the job title as heading; we already have About the role heading. We'll include the introductory paragraphs up to "This role exists to make EY’s agentic platform defensible..." Actually that's part of responsibilities? It's more description. We'll keep as About the role. Let's craft About the role paragraph: "At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. We are seeking an AI Security Engineer to own the security posture of EY’s Agentic AI platform end to end. Agentic AI breaks the assumptions most enterprise security programs are built on. Systems now generate and execute their own code, invoke tools and external APIs autonomously, act on behalf of human principals across long delegation chains, and can be manipulated through the same channel that carries legitimate instructions. Perimeter controls, static code review, and human-in-the-loop approval do not contain any of this on their own. This role exists to make