Cyber - Attack & Penetration Testing - Senior - Consulting

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content: Location: Anywhere in Country (maybe ignore). At EY, we’re all in to shape your future with confidence... This is about the role? Could be "About the role". We'll treat that as About the role. Then "The Opportunity Cyber threats..." maybe part of About the role. Then "Your Key Responsibilities As a Senior on the Attack & Penetration Testing team, you will plan, lead, and execute complex penetration testing..." That's responsibilities. Then "Skills And Attributes For Success ..." That's skills. Then "To qualify for the role, you must have:" That's qualifications/requirements. Could be Requirements. Then list of qualifications: bachelor's degree, experience etc. Then "Ideally, you’ll also have ..." maybe additional qualifications/skills. Then "What We Look For" maybe not needed. Then "What We Offer You At EY, we harness our collective strength..." That's benefits. Then salary range details: Pay. Schedule? Not mentioned. No schedule info. So we should not include Schedule section. Also maybe "Benefits" includes medical, dental, pension, 401(k), paid time off. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must not include boilerplate like cookie/navigation/legal/EEO etc. The posting includes some like "Are you ready to shape your future with confidence? Apply today..." That's application instruction; we should remove application instructions. Also "To make the most of your application experience..." etc. Remove. Also "For those living in California, please click here for additional informati" truncated; remove. Thus we need to extract: - About the role: The introductory paragraph(s) about EY and the opportunity. Let's capture: "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. The Opportunity Cyber threats, social media, artificial intelligence, privacy requirements, and continuity of the business as usual require heavy information security measures. As a Senior Attack & Penetration Tester, you will contribute to our client’s resilience through the execution of sophisticated offensive security operations." We can combine into prose. - Responsibilities: The bullet list under "Your Key Responsibilities". It includes many sentences; we can turn each sentence into

• . Let's list them: 1. plan, lead, and execute complex penetration testing and advanced red team engagements across diverse client environments. 2. apply an intelligence-led, threat-informed approach to emulate realistic adversary behaviors, identify exploitable attack paths, and evaluate preventive, detective, and responsive security controls. 3. work will span external and internal networks, Active Directory, Microsoft Entra ID, web and mobile applications, application programming interfaces (APIs), cloud environments, wireless networks, social engineering, and physical security scenarios, as permitted by the rules of engagement. 4. translate technical testing results into clear, actionable insights for technical and executive audiences. 5. work collaboratively with client technical teams to validate identified weaknesses and develop practical remediation or mitigation strategies, including Active Directory security improvements, system-hardening measures, and compensating controls aligned with the client environment and operational constraints. 6. lead technical workstreams, coordinate testing activities, mentor junior team members, contribute to methodology and capability development, and remain current on emerging vulnerabilities, adversary tactics, offensive security tooling, and industry research. We need to preserve all detail; maybe split into separate
• for each sentence. - Skills And Attributes For Success: This is a list of skills. We can treat as Skills section. List items: - Demonstrate advanced problem-solving and critical-thinking skills when developing and executing attack paths. - Plan and conduct penetration tests and advanced red team engagements within defined scopes, rules of engagement, and safety constraints. - Identify, validate, and exploit vulnerabilities across external and internal networks, Active Directory, Microsoft Entra ID, cloud, wireless, web, mobile, and API environments. - Apply threat-informed testing techniques aligned with the MITRE ATT&CK framework and relevant adversary tactics, techniques, and procedures. - Lead technical testers, coordinate distributed workstreams, and provide hands-on coaching and quality review for junior team members. - Recognize when to escalate risks, issues, testing impacts, and opportunities to appropriate client and EY leadership. - Produce high-quality technical work products, evidence, client reports, and executive-ready presentations that clearly explain risk and remediation priorities. - Communicate complex offensive security concepts clearly to technical stakeholders, business leaders, and executives. - Work collaboratively in cross-functional, culturally diverse, and geographically dispersed teams while adhering to service quality and engagement management requirements. We could also include the "To qualify for the role, you must have:" as Requirements/Qualifications. Let's decide: Use Requirements for mandatory qualifications, and Skills for desired skills? The posting has both "To qualify for the role, you must have:" and then a long list of qualifications. Then "Ideally, you’ll also have ..." which are preferred qualifications. We could combine into Requirements (mandatory) and maybe Skills (preferred). But we already have Skills section for attributes. Might be overlapping. Better: Use Requirements for the mandatory qualifications (bullet list after "To qualify for the role, you must have:"). Use Skills for the "Skills And Attributes For Success" list. Optionally also include a "Preferred Qualifications" section for the "Ideally, you’ll also have" list. But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Qualifications for the mandatory, and Skills for the attributes. Or we could treat Requirements as mandatory and Qualifications as preferred. Let's map: - Requirements: mandatory qualifications (degree, experience, certifications, driver's license, travel willingness). - Qualifications: maybe the "Ideally, you’ll also have" list (preferred). But the heading list includes both Requirements and Qualifications; we can use both. Thus: Requirements (mandatory): - A bachelor's degree in Computer Science, Computer Engineering, Cybersecurity, Management Information Systems, Information Technology, Engineering, or a related field, and at least five years of relevant offensive security experience. - Hands-on experience planning and executing advanced red team engagements, including adversary emulation, objective-based operations, attack-path development, and testing against mature security monitoring and response capabilities. - Advanced experience conducting external and internal network penetration testing, including host and service enumeration, exploitation, privilege escalation, lateral movement, and post-exploitation activities. - Experience assessing Active Directory environments, including domain and trust configurations, privileged access, authentication protocols, delegation, Group Policy, credential exposure, certificate services, security configurations, and other identity-based attack paths. - Experience performing cloud security testing, including identity and access management, exposed services, configuration weaknesses, privilege escalation, and attack-path analysis. - Experience conducting wireless security assessments, including enterprise and guest wireless configurations, authentication controls, segmentation, and authorized wireless attack techniques. - Experience testing web applications, mobile applications, and APIs using manual techniques and industry-recognized testing methodologies. - Experience evaluating security configurations and system-hardening requirements and working with client technical teams to develop practical remediations, mitigations, compensating controls, and validation approaches for identified findings. - Experience with scripting or programming languages used to automate testing, analyze data, or develop offensive security tooling, such as Python, PowerShell, Bash, C#, Go, Rust, or Java. - Experience using commercial and open-source penetration testing tools while adapting techniques to client-specific environments and constraints. - Familiarity with endpoint detection and response (EDR), security information and event management (SIEM), network monitoring, and other defensive controls, including how those controls influence authorized stealth and evasion testing. - Experience with red team command-and-control (C2) platforms and associated operational infrastructure, payload development, redirectors, logging, and campaign management. - Experience evaluating and bypassing EDR and other defensive controls during explicitly authorized engagements, including memory, execution, credential access, lateral movement, and persistence techniques designed for stealth testing against mature client environments. - Working knowledge of the MITRE ATT&CK framework, current vulnerabilities, exploits, adversary tactics, techniques, and procedures, and security remediation practices. - Experience leading remote and on-site technical teams, managing testing activities within approved rules of engagement, and communicating testing risks or potential operational impacts. - The ability to develop clear technical findings that describe evidence, exploitation paths, business risk, and actionable remediation guidance. - Any two relevant offensive security certifications, such as OSCP, OSWP, OSEP, OSCE, OSEE, GPEN, GWAPT, GMOB, GCPN, GXPN, GRTP, GDAT, CRTO, CRTP, CRTE, CREST CRT, or CCSAS. - A valid U.S. driver's license and the willingness and flexibility to travel up to 80 percent, domestically and internationally, to meet client needs. Qualifications (preferred) from "Ideally, you’ll also have": - Hands-on cloud penetration testing and identity security assessment experience across AWS, Microsoft Azure, Microsoft Entra ID, and GCP, including cloud-native identity, privileged access, service, configuration, and privilege-escalation attack paths in hybrid and fully cloud-based environments. - Experience assessing Microsoft Entra ID environments, including identity and access management, privileged roles, authentication controls, application registrations, service principals, conditional access, external identities, and cloud-based attack paths for clients operating fully in the cloud without on-premises Active Directory infrastructure. - Experience applying artificial intelligence (AI) and machine learning capabilities to support testing, including developing automation for reconnaissance, analysis, evidence processing, repeatable test execution, and offensive security workflows. - Advanced experience with API and application security testing, including authentication, authorization, business logic, data exposure, injection, and platform-specific attack paths. - Experience evaluating security baselines and hardening standards for Windows, Linux, cloud, and identity environments and helping clients prioritize remediation activities based on risk, feasibility, and operational impact. - Experience conducting authorized social engineering and physical penetration testing to evaluate personnel, facility, and access-control risks. This includes direct interaction with targeted personnel to assess susceptibility to credential disclosure, unauthorized access requests, and controlled execution of remote access tooling used for command-and-control testing, as well as evaluating physical security controls through lock bypass, access-control evasion, automated security system testing, tailgating, and radio-frequency identification (RFID) badge cloning techniques. - The ability to develop custom tooling, modify public exploits, build proof-of-concept code, and safely operationalize new offensive techniques. - Contributions to the security community through research, public vulnerability disclosures, bug bounty acknowledgments, open-source projects, conference presentations, publications, or technical blogs. - Strong knowledge of Windows, Linux, Unix, TCP/IP networking, common enterprise protocols, and modern identity and security architectures. - Exemplary verbal and written communication skills, including the ability to facilitate workshops and translate complex technical information into concise, executive-level deliverables. - Proficiency with consulting engagement methodologies, including estimating effort, prioritizing activities, managing dependencies, and aligning technical testing to client objectives. But note some of these overlap with Skills section; but we already have Skills section for attributes. Might be duplication. However we must preserve all substantive information; duplication is okay as long as we don't invent. But we should avoid repeating same content in multiple sections if it's already covered elsewhere? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However the posted content has overlapping items; we