Cyber - AI Engineer - Manager - Consulting
for each heading. Use - for lists. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must strip out things like "Apply today", "To make the most of your application experience...", "EY accepts applications...", "For those living in California...", "Any misrepresentation...", "EY | Building a better working world", etc. Also remove "Location: Anywhere in Country" maybe keep as metadata? It says fold minor metadata into a short
or drop it. Could include location in a short
. Probably include a short paragraph about location.
We need to preserve all substantive information. So we need to include:
- Intro 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."
- The Opportunity paragraph: "As a Cyber AI Engineer at the Manager level in EY's Cyber practice, you will work as a forward-deployed engineer, helping clients apply frontier AI cyber models to real security challenges. You will combine hands-on engineering with delivery leadership to build, evaluate, and deploy AI solutions—from prototype to production."
- Responsibilities: list of duties.
- Skills And Attributes For Success: list.
- Qualifications: "To Qualify for the Role, You Must Have" includes education/experience and list of required experience areas.
- Ideally, You'll Also Have: list of preferred qualifications.
- What We Look For: paragraph.
- What We Offer You: includes description of total rewards, salary ranges, benefits.
We need sections: About the role (maybe combine intro + opportunity?), Responsibilities, Requirements (maybe qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting does not mention Schedule explicitly. So we should not create a Schedule section. Pay: we have salary ranges, so include Pay section. Benefits: we have medical/dental, pension/401k, paid time off. So include Benefits.
We need to decide mapping:
- About the role: could contain the intro and opportunity paragraphs.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (education/experience and required experience areas). Could be called Requirements.
- Qualifications: maybe the preferred qualifications (Ideally, You'll Also Have). Or we could swap. But we need both Requirements and Qualifications sections if content exists. We'll put mandatory under Requirements, preferred under Qualifications.
- Skills: maybe the Skills And Attributes For Success.
- Benefits: benefits description.
- Pay: salary ranges.
We should not include Schedule.
We need to output only HTML fragment, no /. Use
headings.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as in posting, but we can format as list items.
Let's extract lists.
Responsibilities list (from "Your Key Responsibilities" paragraph includes multiple sentences; we can break into bullet points). The text:
"You will work with client security and engineering teams to deploy AI workflows for threat investigation, detection engineering, vulnerability analysis, and remediation support.
You will use retrieval, tool calling, and structured outputs, and build evaluation datasets and test harnesses to measure accuracy, false positives, task completion, latency, and cost.
As a Manager, you will own technical delivery, workstreams, timelines, and budgets while mentoring Senior Consultants and Consultants.
You will stay hands-on through architecture, pair programming, code reviews, and integration troubleshooting.
You will partner with frontier model providers and researchers to evaluate cyber capabilities and translate deployment findings into engineering requirements.
You will also support proposals, demonstrations, thought leadership, and account growth, and develop reusable components, evaluation suites, and delivery playbooks."
We'll make each sentence a
- .
Skills And Attributes For Success list: bullet points after that heading. Let's extract each line:
- Deep understanding of frontier AI models, LLMs, agentic architectures, and retrieval-augmented generation for cybersecurity.
- Ability to align Senior Managers, Partners, and client executives on use cases, scope, and engineering requirements.
- Strong software engineering skills to build, test, debug, and deploy production AI applications.
- Experience building model integrations, tool-calling agents, evaluation harnesses, and secure security-platform connections.
- Ability to deliver maintainable solutions on time and within budget, with clear acceptance criteria and documentation.
- Strong troubleshooting skills across cyber workflows, model behavior, data quality, and production issues.
- Ability to explain model behavior, evaluation results, and security trade-offs to technical and executive audiences.
- Strong client discovery, demonstration, stakeholder management, and collaboration skills.
- Experience developing engineering teams while remaining hands-on and accountable for quality.
- Commitment to secure engineering, experimentation, and emerging AI cyber capabilities.
We'll list each as
- .
Requirements (mandatory) list: from "To Qualify for the Role, You Must Have". It includes education/experience requirement sentence then a list of areas after "Experience must include hands-on software engineering and at least 1–2 years building or deploying AI/ML solutions. Proficiency in Python, APIs, Git, automated testing, and production delivery, plus experience in one or more of these areas:" then a bulleted list (though in text it's comma-separated lines). Let's extract:
- Deploying frontier AI models or LLM applications for cybersecurity
- Building agents, model tool integrations, retrieval pipelines, and evaluation harnesses
- Security operations, threat investigation, detection engineering, or incident response automation
- DevSecOps, CI/CD, containers, and infrastructure-as-code for AI services
- Cloud engineering and secure AI deployment on AWS, Azure, or GCP
- API integration with SIEM, SOAR, EDR, vulnerability management, or code security platforms
- Application security, vulnerability analysis, secure code review, or automated remediation
- Understanding of prompt injection, data leakage, unsafe tool use, and safeguards informed by OWASP Top 10 for LLMs and MITRE ATLAS.
- Working knowledge of security architecture, identity and access management, data protection, and secure AI operations.
- Experience leading client-facing delivery or cross-functional engineering from requirements through deployment and handover.
- Strong writing, presentation, and technical documentation skills.
- Willingness to travel based on client and business needs; estimated at 25–50%.
We'll list each as
- .
Preferred qualifications (Ideally, You'll Also Have) list:
- Cybersecurity (e.g., CISSP, CCSP), cloud, engineering, or AI/ML certifications.
- Experience with frontier model providers or cyber-focused model selection, adaptation, and evaluation.
- Experience with agent orchestration, model serving, LLM observability, and CI/CD evaluation gates.
- Knowledge of adversarial testing, AI red teaming, sandboxing, and safeguards for authorized dual-use cyber work.
- Experience with data residency, privacy, model access, and deployment in regulated or restricted environments.
- Experience leading engineering workshops, live prototyping, architecture reviews, and executive demos.
- Experience building cyber evaluation datasets, fine-tuning models, or contributing to open-source AI or security projects.
- Forward-deployed engineering or consulting experience delivering production solutions and managing client relationships.
We'll list each as
- .
What We Look For paragraph: "We seek hands-on engineers who pair cybersecurity expertise with practical AI delivery. You can build with client teams, improve solutions through testing, and balance model capability with safety and reliability. You bring the leadership to develop teams, own delivery, and build client trust while growing EY's Cyber AI engineering practice."
We'll put as
maybe under a section? Could be part of About the role or separate? Since we have About the role already, maybe we can incorporate this into About the role as additional paragraph. But we need to avoid filler. We'll keep it as part of About the role.
What We Offer You: includes description: "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." Then salary ranges bullet? Actually salary ranges are in paragraph: "The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $173,900 to $290,100 Bay Area California offices – $181,200 to $302,100 All other offices locations in the US, including Sacramento – $144,900 to $265,800 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."
We'll put Benefits as list: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options.
Pay section: include the salary ranges paragraph (maybe as
). We'll keep the details.
We must not include boilerplate like "Learn more at ey.com/us/careers." That's maybe okay as it's part of offer. But it's not boilerplate? It's a link; maybe we keep it as part of About? It's not required but we can keep.
We must not include application instructions, EEO, etc. So we strip all that after "What We Offer You" paragraph.
Now construct HTML.
We'll start with a
for location? Could include location line as short
. Location: Anywhere in Country. We'll include as
Location: Anywhere in Country
.
Then About the role: About the role
then 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.
then The Opportunity As a Cyber AI Engineer at the Manager level in EY's Cyber practice, you will work as a forward-deployed engineer, helping clients apply frontier AI cyber models to real security challenges. You will combine hands-on engineering with delivery leadership to build, evaluate, and deploy AI solutions—from prototype to production.
then maybe also include What We Look For paragraph? Could add another after that.
But we need to avoid duplication. We'll put What We Look For as separate
under About the role? Might be okay.
Better: After About the role, we could have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We'll put What We Look For as a
under About the role after the opportunity paragraph.
Now Responsibilities:
Responsibilities
with each - .
Requirements:
Requirements
with mandatory list.
Qualifications: Qualifications
with preferred list.
Skills: Skills
with skills list.
Benef
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must strip out things like "Apply today", "To make the most of your application experience...", "EY accepts applications...", "For those living in California...", "Any misrepresentation...", "EY | Building a better working world", etc. Also remove "Location: Anywhere in Country" maybe keep as metadata? It says fold minor metadata into a short
or drop it. Could include location in a short
. Probably include a short paragraph about location. We need to preserve all substantive information. So we need to include: - Intro 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." - The Opportunity paragraph: "As a Cyber AI Engineer at the Manager level in EY's Cyber practice, you will work as a forward-deployed engineer, helping clients apply frontier AI cyber models to real security challenges. You will combine hands-on engineering with delivery leadership to build, evaluate, and deploy AI solutions—from prototype to production." - Responsibilities: list of duties. - Skills And Attributes For Success: list. - Qualifications: "To Qualify for the Role, You Must Have" includes education/experience and list of required experience areas. - Ideally, You'll Also Have: list of preferred qualifications. - What We Look For: paragraph. - What We Offer You: includes description of total rewards, salary ranges, benefits. We need sections: About the role (maybe combine intro + opportunity?), Responsibilities, Requirements (maybe qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting does not mention Schedule explicitly. So we should not create a Schedule section. Pay: we have salary ranges, so include Pay section. Benefits: we have medical/dental, pension/401k, paid time off. So include Benefits. We need to decide mapping: - About the role: could contain the intro and opportunity paragraphs. - Responsibilities: list of duties. - Requirements: maybe the mandatory qualifications (education/experience and required experience areas). Could be called Requirements. - Qualifications: maybe the preferred qualifications (Ideally, You'll Also Have). Or we could swap. But we need both Requirements and Qualifications sections if content exists. We'll put mandatory under Requirements, preferred under Qualifications. - Skills: maybe the Skills And Attributes For Success. - Benefits: benefits description. - Pay: salary ranges. We should not include Schedule. We need to output only HTML fragment, no /. Use
headings.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as in posting, but we can format as list items.
Let's extract lists.
Responsibilities list (from "Your Key Responsibilities" paragraph includes multiple sentences; we can break into bullet points). The text:
"You will work with client security and engineering teams to deploy AI workflows for threat investigation, detection engineering, vulnerability analysis, and remediation support.
You will use retrieval, tool calling, and structured outputs, and build evaluation datasets and test harnesses to measure accuracy, false positives, task completion, latency, and cost.
As a Manager, you will own technical delivery, workstreams, timelines, and budgets while mentoring Senior Consultants and Consultants.
You will stay hands-on through architecture, pair programming, code reviews, and integration troubleshooting.
You will partner with frontier model providers and researchers to evaluate cyber capabilities and translate deployment findings into engineering requirements.
You will also support proposals, demonstrations, thought leadership, and account growth, and develop reusable components, evaluation suites, and delivery playbooks."
We'll make each sentence a
- .
Skills And Attributes For Success list: bullet points after that heading. Let's extract each line:
- Deep understanding of frontier AI models, LLMs, agentic architectures, and retrieval-augmented generation for cybersecurity.
- Ability to align Senior Managers, Partners, and client executives on use cases, scope, and engineering requirements.
- Strong software engineering skills to build, test, debug, and deploy production AI applications.
- Experience building model integrations, tool-calling agents, evaluation harnesses, and secure security-platform connections.
- Ability to deliver maintainable solutions on time and within budget, with clear acceptance criteria and documentation.
- Strong troubleshooting skills across cyber workflows, model behavior, data quality, and production issues.
- Ability to explain model behavior, evaluation results, and security trade-offs to technical and executive audiences.
- Strong client discovery, demonstration, stakeholder management, and collaboration skills.
- Experience developing engineering teams while remaining hands-on and accountable for quality.
- Commitment to secure engineering, experimentation, and emerging AI cyber capabilities.
We'll list each as
- .
Requirements (mandatory) list: from "To Qualify for the Role, You Must Have". It includes education/experience requirement sentence then a list of areas after "Experience must include hands-on software engineering and at least 1–2 years building or deploying AI/ML solutions. Proficiency in Python, APIs, Git, automated testing, and production delivery, plus experience in one or more of these areas:" then a bulleted list (though in text it's comma-separated lines). Let's extract:
- Deploying frontier AI models or LLM applications for cybersecurity
- Building agents, model tool integrations, retrieval pipelines, and evaluation harnesses
- Security operations, threat investigation, detection engineering, or incident response automation
- DevSecOps, CI/CD, containers, and infrastructure-as-code for AI services
- Cloud engineering and secure AI deployment on AWS, Azure, or GCP
- API integration with SIEM, SOAR, EDR, vulnerability management, or code security platforms
- Application security, vulnerability analysis, secure code review, or automated remediation
- Understanding of prompt injection, data leakage, unsafe tool use, and safeguards informed by OWASP Top 10 for LLMs and MITRE ATLAS.
- Working knowledge of security architecture, identity and access management, data protection, and secure AI operations.
- Experience leading client-facing delivery or cross-functional engineering from requirements through deployment and handover.
- Strong writing, presentation, and technical documentation skills.
- Willingness to travel based on client and business needs; estimated at 25–50%.
We'll list each as
- .
Preferred qualifications (Ideally, You'll Also Have) list:
- Cybersecurity (e.g., CISSP, CCSP), cloud, engineering, or AI/ML certifications.
- Experience with frontier model providers or cyber-focused model selection, adaptation, and evaluation.
- Experience with agent orchestration, model serving, LLM observability, and CI/CD evaluation gates.
- Knowledge of adversarial testing, AI red teaming, sandboxing, and safeguards for authorized dual-use cyber work.
- Experience with data residency, privacy, model access, and deployment in regulated or restricted environments.
- Experience leading engineering workshops, live prototyping, architecture reviews, and executive demos.
- Experience building cyber evaluation datasets, fine-tuning models, or contributing to open-source AI or security projects.
- Forward-deployed engineering or consulting experience delivering production solutions and managing client relationships.
We'll list each as
- .
What We Look For paragraph: "We seek hands-on engineers who pair cybersecurity expertise with practical AI delivery. You can build with client teams, improve solutions through testing, and balance model capability with safety and reliability. You bring the leadership to develop teams, own delivery, and build client trust while growing EY's Cyber AI engineering practice."
We'll put as
maybe under a section? Could be part of About the role or separate? Since we have About the role already, maybe we can incorporate this into About the role as additional paragraph. But we need to avoid filler. We'll keep it as part of About the role.
What We Offer You: includes description: "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." Then salary ranges bullet? Actually salary ranges are in paragraph: "The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $173,900 to $290,100 Bay Area California offices – $181,200 to $302,100 All other offices locations in the US, including Sacramento – $144,900 to $265,800 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."
We'll put Benefits as list: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options.
Pay section: include the salary ranges paragraph (maybe as
). We'll keep the details.
We must not include boilerplate like "Learn more at ey.com/us/careers." That's maybe okay as it's part of offer. But it's not boilerplate? It's a link; maybe we keep it as part of About? It's not required but we can keep.
We must not include application instructions, EEO, etc. So we strip all that after "What We Offer You" paragraph.
Now construct HTML.
We'll start with a
for location? Could include location line as short
. Location: Anywhere in Country. We'll include as
Location: Anywhere in Country
.
Then About the role: About the role
then 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.
then The Opportunity As a Cyber AI Engineer at the Manager level in EY's Cyber practice, you will work as a forward-deployed engineer, helping clients apply frontier AI cyber models to real security challenges. You will combine hands-on engineering with delivery leadership to build, evaluate, and deploy AI solutions—from prototype to production.
then maybe also include What We Look For paragraph? Could add another after that.
But we need to avoid duplication. We'll put What We Look For as separate
under About the role? Might be okay.
Better: After About the role, we could have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We'll put What We Look For as a
under About the role after the opportunity paragraph.
Now Responsibilities:
Responsibilities
with each - .
Requirements:
Requirements
with mandatory list.
Qualifications: Qualifications
with preferred list.
Skills: Skills
with skills list.
Benef
. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as in posting, but we can format as list items. Let's extract lists. Responsibilities list (from "Your Key Responsibilities" paragraph includes multiple sentences; we can break into bullet points). The text: "You will work with client security and engineering teams to deploy AI workflows for threat investigation, detection engineering, vulnerability analysis, and remediation support. You will use retrieval, tool calling, and structured outputs, and build evaluation datasets and test harnesses to measure accuracy, false positives, task completion, latency, and cost. As a Manager, you will own technical delivery, workstreams, timelines, and budgets while mentoring Senior Consultants and Consultants. You will stay hands-on through architecture, pair programming, code reviews, and integration troubleshooting. You will partner with frontier model providers and researchers to evaluate cyber capabilities and translate deployment findings into engineering requirements. You will also support proposals, demonstrations, thought leadership, and account growth, and develop reusable components, evaluation suites, and delivery playbooks." We'll make each sentence a
maybe under a section? Could be part of About the role or separate? Since we have About the role already, maybe we can incorporate this into About the role as additional paragraph. But we need to avoid filler. We'll keep it as part of About the role. What We Offer You: includes description: "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." Then salary ranges bullet? Actually salary ranges are in paragraph: "The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $173,900 to $290,100 Bay Area California offices – $181,200 to $302,100 All other offices locations in the US, including Sacramento – $144,900 to $265,800 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." We'll put Benefits as list: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. Pay section: include the salary ranges paragraph (maybe as
). We'll keep the details. We must not include boilerplate like "Learn more at ey.com/us/careers." That's maybe okay as it's part of offer. But it's not boilerplate? It's a link; maybe we keep it as part of About? It's not required but we can keep. We must not include application instructions, EEO, etc. So we strip all that after "What We Offer You" paragraph. Now construct HTML. We'll start with a
for location? Could include location line as short
. Location: Anywhere in Country. We'll include as
Location: Anywhere in Country
. Then About the role:About the role
thenAt 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.
thenThe Opportunity As a Cyber AI Engineer at the Manager level in EY's Cyber practice, you will work as a forward-deployed engineer, helping clients apply frontier AI cyber models to real security challenges. You will combine hands-on engineering with delivery leadership to build, evaluate, and deploy AI solutions—from prototype to production.
then maybe also include What We Look For paragraph? Could add anotherafter that. But we need to avoid duplication. We'll put What We Look For as separate
under About the role? Might be okay. Better: After About the role, we could have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll put What We Look For as a
under About the role after the opportunity paragraph. Now Responsibilities:
Responsibilities
- with each
- .
Requirements:
Requirements
- with mandatory list.
Qualifications:
Qualifications
- with preferred list.
Skills:
Skills
- with skills list.
Benef