Lead AI Security Engineer - Senior Manager

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to keep location? It says Location: Anywhere in Country. That's minor metadata; we can fold into short

maybe. Not a heading. We need to decide sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements/Qualifications (maybe combine?), Skills (maybe separate?), Benefits, Pay (salary ranges), Schedule? Not mentioned schedule. So we should not create Schedule section. We need to preserve all substantive info: location, description, responsibilities list, skills/attributes, qualifications (education, experience), benefits, pay ranges. We must not repeat job title as heading. The page already shows it, so we don't add heading for title. We need to output only HTML fragment, no /, no markdown fences. Let's parse content. First paragraph: "Location: Anywhere in Country 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 can combine location and intro into a

. Possibly separate location as part of same paragraph. Then "The opportunity We are seeking an AI Security Engineer to own the security posture of EY’s Agentic AI platform end to end." This is part of about the role. Then a long paragraph describing the role. We'll put under About the role. Then "Your Key Responsibilities" heading in original. We'll create

Responsibilities

and then a

• list of each responsibility bullet. We need to extract each bullet: The responsibilities list appears as sentences separated by periods but we need to break into list items. The text after "Your Key Responsibilities" includes many sentences each starting with a verb. We'll split them. Let's copy the responsibilities block: "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." We'll turn each line into
• . Next "Skills And Attributes For Success" heading. We'll create

  Skills

  maybe? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills section. We need to preserve the bullet list under Skills And Attributes For Success. It's a paragraph with bullet-like sentences separated by periods. We'll split into list items. Let's extract that block: "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." We'll make each a

  . Next "To qualify you must have" paragraph. This is qualifications/requirements. We'll create

  Requirements

  maybe also Qualifications. The instruction says we can have Requirements, Qualifications sections. We need to decide. Since the text includes education, experience, etc. We'll put under Requirements. We need to preserve all details: 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. We'll split into list items. Next "What We Offer You" section: benefits. We'll create

  Benefits

  . The paragraph: "At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal fulfillment and an inclusive culture. Learn more at ey.com/us/careers. 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 need to extract Pay section separately? The instruction says we should have Pay section if posting actually states them. The posting includes base salary ranges. So we should create a Pay section with that info. Benefits section can include other benefits (medical, dental, pension, 401k, paid time off, flexible vacation, holidays, etc.). We should not duplicate salary info in Benefits. Thus we will have:

  About the role

  ... (intro + opportunity description)

  Responsibilities

  ...

  Skills

  ...

  Requirements

  ...

  Benefits

  ...

  (maybe include medical, dental, pension, 401k, paid time off, flexible vacation,