Cyber - SOAR (Security Orchestration, Automation and Response) Engineer - Senior - Consulting

We need to output HTML fragment with sections: About the role? The posting includes "The Opportunity", "Your Key Responsibilities", "Skills And Attributes For Success", "To Qualify for the Role, You Must Have:", "Ideally, You'll Also Have", "What We Look For", "What We Offer You". Also location line at top: "Location: Anywhere in Country". We need to not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out things like "Are you ready to shape your future with confidence? Apply today." and the lines about applications, etc. Also remove the EEO statement at end. Also remove the "EY | Building a better working world" etc. Also remove the "EY provides equal employment opportunities..." etc. We need to preserve all substantive information. So we need to include location, the introductory paragraph about EY, The Opportunity paragraph, responsibilities, skills, qualifications, ideal qualifications, what we look for, what we offer (salary ranges, total rewards). Also maybe include "What We Look For" as a section. We must not create sections for Pay/Benefits/Schedule unless posting actually states them. It does state salary ranges and total rewards (medical/dental, pension/401k, paid time off). So we can have a Benefits section (maybe "What We Offer You") includes salary and benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We need headings: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those specific headings if applicable. But we can also use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when we have those sections. However we have content like "The Opportunity" which could map to "About the role". "Your Key Responsibilities" maps to Responsibilities. "Skills And Attributes For Success" maps to Skills. "To Qualify for the Role, You Must Have:" maps to Requirements/Qualifications. "Ideally, You'll Also Have" could be additional qualifications. "What We Look For" maybe about culture fit. "What We Offer You" maps to Benefits/Pay. We need to decide which sections to include. Likely we will have: About the role (The Opportunity), Responsibilities, Skills, Requirements (Qualifications), Benefits (What We Offer You). Possibly also a section for "Preferred Qualifications" but we can merge into Requirements. We must not create sections with filler text. So we need to ensure each heading has substantive content. We need to preserve all substantive information: location, intro paragraph, opportunity paragraph, responsibilities bullet list (though they are in prose sentences, we can convert to

  • ). Skills list (also prose). Qualifications (must have) list. Ideal qualifications list. What we look for (maybe a paragraph). What we offer (salary ranges and total rewards). Also maybe include "Location: Anywhere in Country" as a short

    . We must not include duplicated lines. Ensure we don't repeat same content. Now produce HTML fragment. Let's extract content. Location: "Location: Anywhere in Country". We'll put

    Location: Anywhere in Country

    . 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." That's substantive. The Opportunity paragraph: Starting from "In a rapidly evolving cybersecurity landscape..." up to "...and maximize the value of their cybersecurity investments." We'll capture that. Responsibilities: The block under "Your Key Responsibilities". It's a long paragraph with many sentences. We need to break into list items. We can split by sentences that start with verbs. But we can also keep as
    • each responsibility. Let's parse: - designing, developing, and maintaining automated security workflows that enhance the effectiveness and efficiency of security operations. - implementing and optimizing SOAR platforms by integrating security tools, data sources, and operational processes across the cybersecurity ecosystem. - collaborating with Security Operations Center (SOC), Incident Response, Threat Intelligence, Detection Engineering, and Vulnerability Management teams to identify automation opportunities and translate operational requirements into scalable technical solutions. - design and develop playbooks that automate incident triage, enrichment, containment, remediation, and reporting activities while ensuring reliability, maintainability, and security of automation workflows. - leverage programming and scripting languages to develop custom integrations, APIs, connectors, and automation capabilities across cloud environments, security platforms, and enterprise applications. This may include integrating SIEM, EDR, IAM, cloud security, threat intelligence, ticketing, and collaboration platforms to facilitate seamless orchestration across complex security architectures. - contribute to the development of automation standards, reusable frameworks, and engineering best practices while assisting clients with SOAR platform deployments, upgrades, and operational enhancements. - Additionally, as a senior engineer, you will mentor junior team members, provide technical leadership on security automation initiatives, and contribute to the continued growth of the cybersecurity engineering practice. - In addition to these responsibilities, you will be expected to stay current on emerging cybersecurity threats, automation technologies, cloud-native security capabilities, and evolving SOAR solutions. - You will actively participate in professional development opportunities, industry forums, technical communities, and relevant training to maintain expertise in modern security operations and automation engineering. We'll make each a
    • . Skills And Attributes For Success: It's a paragraph with bullet-like statements separated by periods. We can split similarly: - Demonstrate advanced problem-solving and critical thinking skills. - Exhibit strong software engineering and automation development capabilities. - Foster a collaborative learning environment and mentor junior team members. - Possess the ability to identify and communicate opportunities to improve security operations through automation and orchestration. - Demonstrate experience designing scalable and maintainable integrations across complex technology environments. - The ability to create and deliver high-quality work products, technical documentation, client reports, and presentations. - Adherence to service quality standards and program management requirements. - The ability to work collaboratively in a cross-functional team environment that is culturally diverse and geographically dispersed. - Strong analytical and troubleshooting skills, with the ability to diagnose and resolve complex integration and workflow issues. - The ability to balance security, operational efficiency, and engineering best practices when developing automation solutions. We'll make each a
    • . Qualifications (Must Have): List items: - A Bachelor’s degree (4-year degree) in Computer Science, Computer Engineering, Cybersecurity, Information Technology, Management Information Systems, or a related field, along with 2-4 years of relevant experience in security automation, SOAR engineering, security operations, cybersecurity engineering, or a related discipline. - Hands-on experience implementing, administering, or developing solutions within enterprise SOAR platforms such as Palo Alto Cortex XSOAR, Microsoft Sentinel Automation, Splunk SOAR (Phantom), Google Security Operations (Chronicle SOAR), Tines, D3 Security, Swimlane, or similar technologies. - Strong software development and scripting experience using languages such as Python, PowerShell, JavaScript, or other automation-focused programming languages. - Experience developing and consuming REST APIs, web services, SDKs, and custom integrations. - Knowledge of security operations processes including alert triage, incident response, threat detection, vulnerability management, and case management workflows. - Experience integrating cybersecurity technologies such as SIEM, EDR/XDR, IAM, email security, network security, cloud security, vulnerability management, threat intelligence, and ticketing platforms. - Understanding of infrastructure, networking, operating systems, and cloud environments including Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP). - Experience designing, testing, troubleshooting, and maintaining automation workflows in production environments. - Knowledge of secure development principles and software engineering best practices including version control, testing methodologies, and CI/CD concepts. - Relevant industry certifications such as Microsoft Certified: Cybersecurity Architect Expert, Microsoft SC-200, Splunk Core Certified Power User, Security+, CySA+, GSEC, GCIH, Cortex XSOAR Engineer, or similar certifications, or the ability to acquire certification after employment. Ideal qualifications (Ideal, You'll Also Have): We'll make a subsection maybe under Requirements or separate "Preferred Qualifications". But we can incorporate as another list under same heading? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have "Qualifications" for must-have, and maybe "Preferred Qualifications" but not in list. However we could merge ideal into Qualifications as additional bullets, but that might dilute. Better to have a separate section "Preferred Qualifications" but not in the given examples. The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

      for section headings (e.g. ...)". Likely they expect those headings if applicable. We could treat "Ideally, You'll Also Have" as part of Qualifications (maybe as "Preferred Qualifications") but we could still use

      Qualifications

      and include both must-have and ideal under same list? Might be confusing. Perhaps we create two sections: "Requirements" for must-have, and "Preferred Qualifications" (though not in examples). But to be safe, we could include "Qualifications" for must-have and then another section "Additional Qualifications" but that may be considered thin. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine must-have and ideal into one Qualifications section, labeling them accordingly within the list (like "Must have:" and "Ideal:" subheadings). But we cannot add extra headings inside? We could use

      to label. Simplify: We'll have a single

      Qualifications

      and within it we can have two

      paragraphs: one for required qualifications, one for preferred qualifications, each followed by

      • . That keeps substantive content. What We Look For: paragraph about top performers etc. We'll make a section maybe "About the team" or "What We Look For". Not in examples but we could use

        What We Look For

        but not in list. Might be okay. But to follow instruction, maybe we incorporate into "About the role" or "Skills". However it's substantive about culture fit. Could be its own section but not in examples. The instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. We'll include a heading for "What We Look For". What We Offer You: includes salary ranges and total rewards. We'll make a

        Benefits

        (or "What We Offer"). We'll include salary ranges as

        and then benefits list. We must not include boilerplate like "Are you ready to shape your future with confidence? Apply today." etc. Also remove the lines about applications, EEO, etc. Now craft HTML. We'll start with location

        . Then intro

        . Then

        About the role