Lead AI Security Engineer - Senior Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "The opportunity" paragraph describing role. Could treat as About the role. Then Responsibilities (Your Key Responsibilities). Then Skills (Skills And Attributes For Success). Then Qualifications (To qualify you must have...). Then Benefits (What We Offer You). Also Pay (salary ranges). Also maybe Schedule? Not present. So include Pay section with salary ranges. Benefits section with description of benefits. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove application instructions like "Apply today", "limit yourself to two applications", etc. Also remove navigation/legal/EEO etc. Also remove "Are you ready to shape your future with confidence? Apply today." etc. Also remove "To make the most of your application experience..." etc. Also remove "EY accepts applications..." etc. Also remove "For those living in California, please click here..." etc. Also remove values statements at end. We must preserve all substantive information: description of role, responsibilities, skills, qualifications, benefits, pay ranges. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. Thus sections: About the role (from "The opportunity" paragraph). Responsibilities (Your Key Responsibilities). Skills (Skills And Attributes For Success). Qualifications (To qualify you must have...). Benefits (What We Offer You). Pay (salary ranges). Possibly Requirements? Could combine Qualifications as Requirements. But we have both Skills and Qualifications. Use Skills for skills/attributes, Qualifications for education/experience requirements. We must not create sections with filler. So include those. Now craft HTML. Structure:

About the role

... (the opportunity paragraph)

Responsibilities

• ... each responsibility line
...

We need to preserve all responsibility bullet points. They are listed as sentences starting with verbs. We'll extract each bullet. List of 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 section: list bullet points from 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. Now Qualifications: list bullet points from "To qualify you must have ..." paragraph and subsequent bullet-like sentences. Paragraph: "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." Then "Ideally, you'll also have" list: - 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 include these as bullet list under Qualifications. Now Benefits: from "What We Offer You" paragraph. 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: ..." But we will separate Pay section for salary ranges. Benefits section should include description of benefits: professional growth, personal fulfillment, inclusive culture, comprehensive compensation and benefits package, medical and dental coverage, pension and 401(k) plans, wide range of paid time off options, flexible vacation policy, designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, other leaves of absence. We must not include the "Learn more at ey.com/us/careers." maybe considered boilerplate? It's a link but still part of offering. Might keep but it's not essential. Could keep as part of benefits description. However it's a URL; maybe okay. But we can keep. We must not include "Are you ready to shape your future with confidence? Apply today." etc. That's not benefits. Now Pay section: include salary ranges as given. We need to output only HTML fragment, no markdown fences. Let's craft. We'll have:

About the role

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. 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 EY’s agentic platform defensible in the most highly regulated client environments in the world, including tax, financial services, audit, and risk. It is the security engineering and assurance authority spanning the whole stack: from silicon-level attestation and Kubernetes hardening, through supply-chain integrity and sandboxed execution, to prompt-injection defense, agent authority containment, and audit-grade evidence. This is a deliberately broad mandate. It is ideal for a principal security engineer who has genuine depth in cloud-native and platform security, who has moved decisively into AI and agentic threat models, and who is equally comfortable writing a threat model, breaking a system in a red-team exercise, defining policy-as-code, and defending the resulting engineering to a client’s CISO or a regulator.

Note: The paragraph started with "The opportunity". We'll keep as is. Now Responsibilities ul. Now Skills ul. Now Qualifications ul. Now Benefits ul? Actually benefits description is prose; we can use

for prose. Could also use

for list of benefits. But rule: Use
• for any list of duties/requirements/benefits, and

  for prose. Benefits are a list; we can make ul