Cyber - Enterprise Security Architect - Senior Manager - Consulting

We need to output HTML fragment with sections: About the role? The posting includes location line, intro paragraphs, 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, etc. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: The Opportunity paragraph maybe qualifies as about the role. Could be "About the role" heading. - Responsibilities: "Your Key Responsibilities" section. - Requirements: Could be "To Qualify for the Role, You Must Have" (qualifications). Also "Ideally, You'll Also Have" could be additional qualifications/preferred. - Skills: "Skills And Attributes For Success" could be Skills. - Benefits: "What We Offer You" includes benefits description (medical, dental, pension, 401(k), PTO). Also maybe mention salary range (Pay). So we need Pay section if salary present. Yes salary ranges given. So Pay section. - Schedule: Not mentioned (travel 25-50% maybe schedule? Not exactly schedule. No explicit schedule like full-time/part-time. So we should not create Schedule section. We must not create sections with placeholder text. So include only those with real content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each bullet into
• . The responsibilities paragraph is a long paragraph with multiple sentences; we could split into list items per duty. The text includes multiple responsibilities separated by periods. We should parse them into list items. Similarly for Skills And Attributes For Success: list of bullet-like sentences separated by periods. We'll make list. For Qualifications: "To Qualify for the Role, You Must Have" includes a paragraph with multiple requirements; we can split into list. "Ideally, You'll Also Have" also list. For Benefits: "What We Offer You" includes description: professional growth, personal fulfillment, inclusive culture, plus Total Rewards package includes medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. We'll make list. Pay: salary ranges: we need to present as maybe a

  with the ranges. Could also be a list? Probably just

  . We must not include boilerplate like EEO, legal, application instructions, etc. So we need to strip those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. We must not repeat job title as heading. Not needed. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, location line: "Location: Anywhere in Country". Might be considered metadata; we could fold into a short

  or drop. Probably we can include a short

  for location. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So location is minor metadata; we can include a

  at top. Then intro paragraphs: "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 about the company; could be part of About the role? Might be considered generic; but we can include under About the role. "The Opportunity As digital transformation accelerates..." That's also about role. We'll combine. Thus About the role section will contain those paragraphs. Now Responsibilities: "Your Key Responsibilities As a Senior Manager on the Enterprise Security Architecture team, you will direct and oversee complex security architecture engagements across a range of industries, serving as the primary point of accountability for engagement quality, client satisfaction, and delivery of high-quality work products within budget and established deadlines. You will lead architecture assessments, Zero Trust transformation programs, cloud security architecture initiatives, and security governance engagements—bringing strategic direction and technical depth to each. You will engage at the executive level with client stakeholders—including CISOs, CIOs, Chief Architects, and Boards—to frame security architecture challenges, present findings and recommendations, and build the trusted advisor relationships that drive long-term client value. You will ensure that engagement teams produce technically rigorous, business-aligned deliverables that translate complex architecture decisions into clear, actionable guidance. As a Senior Manager, you will play a leading role in business development—identifying and pursuing new opportunities, shaping proposals, leading client presentations, and expanding relationships within existing accounts. You will contribute to the strategic direction and growth of EY's Cyber practice by developing service offerings, producing thought leadership, and representing EY at industry forums and client events. You will lead, mentor, and develop teams of Managers, Senior Consultants, and Consultants, fostering a culture of technical excellence, continuous learning, and collaborative client service. You will also collaborate across EY's Cyber and broader technology capabilities to bring integrated, cross-disciplinary solutions to clients facing complex enterprise challenges." We need to split into list items. Each sentence seems a duty. Let's split by periods that end a sentence. We'll produce

• for each. Now Skills And Attributes For Success: "Deep expertise in enterprise security architecture principles, patterns, and frameworks, with the authority to set architectural direction across network, cloud, application, data, identity, and endpoint security domains.Demonstrated ability to build and sustain trusted, executive-level client relationships and serve as a strategic advisor to CISOs, CIOs, and enterprise technology leadership.Experience leading and shaping security architecture strategy, Zero Trust program design, cloud security architecture, and enterprise security governance at scale.Strong business development instincts, with experience identifying opportunities, developing proposals, and contributing to account growth strategies.Ability to translate complex security architecture concepts into compelling narratives for executive and board-level audiences.Track record of leading high-performing teams, developing talent, and managing multiple concurrent engagement workstreams.Strong presentation, facilitation, and executive stakeholder management skills, with experience presenting to C-suite and senior leadership audiences.Demonstrated contribution to thought leadership, market positioning, and practice-building within a consulting or enterprise environment.Commitment to quality, innovation, and the continuous development of both people and practice capabilities." We need to split into list items. Note there are no spaces after periods in some places (like "...domains.Demonstrated"). We'll need to handle that. We'll split by period followed by capital letter or start of new sentence. We'll just manually split. Now Qualifications: "To Qualify for the Role, You Must Have A bachelor's degree in Cybersecurity, Computer Science, Information Systems, Engineering, or a related field, and approximately 8+ years of relevant experience; or a graduate degree and approximately 7+ years of relevant experience.Experience in one or more of the following areas:Enterprise security architecture strategy, assessment, and future-state designNetwork security architecture, including segmentation, secure access, and perimeter designCloud security architecture across AWS, Azure, or GCP, including IaaS, PaaS, and SaaS securityIdentity and access management architecture, including Zero Trust and privileged access designApplication security architecture, secure SDLC, and DevSecOps integrationData protection architecture, including encryption, data classification, and data loss preventionSecurity architecture governance, standards development, and enterprise architecture review processesKnowledge of cybersecurity frameworks and standards, including NIST CSF, NIST 800-53, ISO 27001/27002, CIS Controls, and SABSA.A track record of leading client-facing security architecture engagements, managing senior client relationships, and driving successful delivery outcomes.Experience contributing to business development efforts, including proposal development, opportunity pursuit, and account growth.Strong written, verbal, and executive presentation skills.Willingness to travel based on client and business needs; travel estimated at 25–50%." We need to split into list items. Note there are some missing spaces after colons and periods. We'll parse. Then "Ideally, You'll Also Have Professional certifications such as CISSP, CCSP, SABSA Chartered Architect (SCF/SCM), TOGAF, or other relevant security architecture credentials.Experience shaping and growing a security architecture practice, service line, or center of excellence within a consulting or enterprise environment.Established presence in the security architecture community, including contributions to thought leadership, industry publications, conference presentations, or advisory roles.Experience designing and overseeing implementation of Zero Trust architectures, including microsegmentation, identity-centric access, and continuous verification at enterprise scale.Knowledge of security technology domains—including SIEM, SOAR, EDR/XDR, PAM, IAM, CNAPP, and CASB—with the ability to advise on strategic architecture fit and technology roadmap decisions.Deep familiarity with regulatory and compliance requirements—such as HIPAA, PCI DSS, FISMA, GDPR, or NYDFS—and the ability to advise clients on their implications for enterprise security architecture strategy.Experience managing senior executive relationships and serving in a trusted advisor capacity across complex, multi-year client engagements.Background in software development, infrastructure engineering, or network engineering that informs technical credibility and depth in architecture discussions.Knowledge of regulated industries such as financial services, healthcare, life sciences, government, or critical infrastructure." We'll split similarly. Now What We Look For: "We seek senior professionals who bring both the technical authority to shape enterprise security architecture and the leadership presence to build enduring client relationships and contribute meaningfully to practice growth. The ideal candidate has a demonstrated track record of leading complex architecture engagements, developing high-performing teams, and driving business outcomes through trusted advisory relationships at the executive level. Successful candidates combine deep security architecture expertise with strong business acumen, a passion for thought leadership and innovation, and the drive to help EY build and sustain a market-leading Enterprise Security Architecture practice." This could be part of About the role or maybe a separate section like "What We Look For". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "What We Look For" could be considered Requirements or Qualifications? It's more about desired attributes; could be part of Skills or Qualifications. But we already have Skills and Qualifications sections. Might be redundant. However we must not create sections with filler. If we already covered similar content in Skills and Qualifications, we could omit this section to avoid duplication. But we need to preserve ALL substantive information; we cannot omit details. However the content in "What We Look For" is somewhat similar to Skills and Qualifications but not identical; it adds nuance: "technical authority to shape enterprise security architecture and leadership presence to build enduring client relationships", "demonstrated track record of leading complex architecture engagements, developing high-performing teams, and driving business outcomes through trusted advisory relationships at the executive level", "combine deep security architecture expertise with strong business acumen, a passion for thought leadership and innovation, and the drive to help EY build and sustain a market-leading Enterprise Security Architecture practice." This is not covered elsewhere exactly. We could incorporate into Skills or Qualifications but we must not lose detail. Perhaps we can add a section "What We Look For" but the instruction only lists allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It 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 an exhaustive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.