Jobs · Ohio

Cyber - AI Engineer - Manager - Consulting

EY · Akron, OH · 1 mo ago
Hybrid$174k–$290k/yrFull-time
We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content. Given posting: location line, then intro paragraphs, then "The Opportunity" paragraph, then "Your Key Responsibilities" list, then "Skills And Attributes For Success" list, then "To Qualify for the Role, You Must Have" qualifications, then "Ideally, You'll Also Have" maybe part of qualifications/skills, then "What We Look For" maybe about role, then "What We Offer You" includes benefits and pay range, then more boilerplate. We need to preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "What We Look For" maybe not a standard heading but could be part of About the role? We'll decide. We need sections: About the role (intro + The Opportunity maybe). Responsibilities (Your Key Responsibilities). Requirements (maybe combine qualifications and ideally). Skills (Skills And Attributes For Success). Benefits (What We Offer You includes benefits). Pay (salary ranges). Schedule (maybe travel willingness? Not schedule but maybe not needed). The posting mentions willingness to travel 25-50% but not schedule. No explicit schedule. So we should not create Schedule section if no real content. Similarly Benefits: we have medical/dental, pension/401k, paid time off. That's substantive. Pay: salary ranges given. So include Pay. We must not include headings with filler like "commensurate with experience". Not present. We need to use
  • for any list of duties/requirements/benefits. For prose use

    . We need to preserve all substantive info; do not invent or summarize away detail. Let's extract. About the role: combine intro paragraphs and The Opportunity. Intro: "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." Then 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." We can combine into About the role section. Responsibilities: list from "Your Key Responsibilities". It includes multiple sentences, some are separate bullet-like but not formatted as list. We need to turn into

    • . 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 of bullet-like sentences. We'll turn into
      • . Text: "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 make each a
      • . Qualifications: "To Qualify for the Role, You Must Have" paragraph includes requirements. We'll treat as Requirements section? Actually we have Requirements heading. We'll put qualifications there. Also "Ideally, You'll Also Have" could be additional qualifications/skills but we can include in Requirements or Skills. Since we already have Skills section, we could put the "Ideally" items under Skills as additional. But we must not duplicate. Let's treat Requirements as the mandatory qualifications. And Skills as the Skills And Attributes For Success plus maybe the Ideally items? However the Ideally items are more like preferred qualifications, could go under Requirements as well. But we need to avoid thin sections. We could merge Ideally into Requirements as additional bullet points. Let's extract mandatory qualifications: "A bachelor's degree in Cybersecurity, Computer Science, Information Systems, Engineering, or a related field and 5+ years of relevant experience; or a graduate degree and 4+ years. 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: 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%." Now Ideally items: "Ideally, You'll Also Have 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 could add these as additional
      • under Requirements (or Skills). Since they are qualifications/preferred, I'll add them under Requirements as well, maybe after a note "Preferred qualifications". But we must not invent headings inside. We can just continue list. Thus Requirements section will have a
        • list combining mandatory and preferred. Now Benefits: from "What We Offer You": "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 range details, then "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 need Benefits section: medical/dental, pension/401k, paid time off. Also maybe professional growth etc but that's more generic. We'll include the tangible benefits. Pay: salary ranges: three tiers. We need to output Pay section with
          • for each range? Could be a

            with ranges. The rule: Use

            • for any list of duties/requirements/benefits. Pay is not a list but could be presented as

              . We'll use

              . Schedule: no explicit schedule, so omit. Now ensure we don't include boilerplate: remove lines like "Learn more at ey.com/us/careers." maybe keep as part of About? It's generic but maybe keep as it's part of What We Offer You. Could be considered boilerplate but it's a link to careers page; might be considered navigation? It's not EEO etc. Might keep but it's not substantive. Safer to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more at ey.com/us/careers." is not navigation? It's a link to careers page, maybe considered navigation. I'd remove it. 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 EEO paragraphs. Now construct HTML. We'll have:

              About the role

              ...combined intro and opportunity...

              Responsibilities

              • ...
              • ...

              Requirements

              • ...
              • ...

              Skills

              • ...
              • ...

              Benefits

              • Medical and dental coverage
              • Pension and 401(k) plans
              • Wide range of paid time off options

              Pay

              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.

              We need to ensure we didn't repeat job title. Good. Check for any duplicated lines: we removed. Now ensure we didn't miss any substantive info: The "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." This is substantive about role; could be included in About the role or Responsibilities. Since we already have About the role intro, we could add this paragraph there. Let's add to About the role after opportunity. Thus About the role p will contain: location line? We removed location line? The location line "Location: Anywhere in Country" maybe not needed as heading but could be kept as part of About. It's substantive location info. We'll include it in About the role p. Thus About the role p: "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

Similar jobs