Cyber - Enterprise Security Architect - Senior - Consulting
for section headings like 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: maybe the intro paragraphs (Location, At EY... The Opportunity). Could be "About the role". Use About the role
then
with that content. - Responsibilities: "Your Key Responsibilities" ->
Responsibilities
then- each bullet.
- Requirements / Qualifications: There's "To Qualify for the Role, You Must Have" and "Ideally, You'll Also Have". Could combine into Requirements/Qualifications. Use
Qualifications
maybe. Or separate: Requirements and Preferred Qualifications. But we prefer few substantive sections. Could haveQualifications
containing both required and preferred as lists. - Skills: There's "Skills And Attributes For Success". Could beSkills
with list. - Benefits: "What We Offer You" includes salary range and total rewards. So we can haveBenefits
withdescribing salary ranges and total rewards. - Pay: Could be separate but we already included salary in Benefits. The instruction: only include Pay section if posting actually states them. It does state salary ranges. Could make a Pay section separate from Benefits. But we can combine? The instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section that includes salary and total rewards. That seems okay. - Schedule: Not mentioned (travel 25-50% maybe schedule? Not explicit schedule like full-time/part-time). Travel is mentioned but not schedule. So we omit Schedule. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines, navigation, cookie, etc. Also remove application instructions like "Apply today", "limit yourself to two applications", etc. Also remove "What We Look For" maybe could be part of Skills? But it's a separate paragraph about desired traits. Could incorporate into Skills or Qualifications. But we already have Skills section; we could add that paragraph there. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the posting, but we can reformat into HTML. Must not omit any substantive info. That includes the intro paragraphs, the opportunity paragraph, responsibilities bullet list, skills and attributes list, qualification requirements, ideal qualifications, what we look for, what we offer (salary ranges, total rewards), maybe also the location line "Location: Anywhere in Country". That's substantive. Should we keep it? Yes. Could be part of About the role. We must not include boilerplate like "EY provides equal employment opportunities..." etc. Also remove the long EEO statement at end. Also remove the "EY | Building a better working world" etc. Also remove the "Are you ready to shape your future with confidence? Apply today." etc. Also remove the "To make the most of your application experience..." etc. Also remove the "Any misrepresentation..." etc. Also remove the "EY is building a better working world..." paragraph. Also remove the "EY provides equal employment opportunities..." etc. Also remove the accommodation paragraph. We must keep location line, intro about EY shaping future, The Opportunity paragraph, responsibilities, skills, qualifications, ideal qualifications, what we look for, what we offer (salary and total rewards). Also maybe the "We are seeking professionals..." paragraph (What We Look For) is substantive; keep. We need to ensure we don't repeat job title as heading. No job title given explicitly; but we can ignore. Now craft HTML. Structure:
About the role
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 As organizations undertake large-scale digital transformation, cloud migration, and technology modernization initiatives, the need for robust, scalable security architecture has never been greater. Security architecture decisions made today define an organization's risk posture for years to come—shaping how data is protected, how systems are connected, and how threats are detected and contained. As a Senior Consultant within EY's Cyber practice focused on Enterprise Security Architecture, you will work with clients to assess existing security architectures, design future-state security frameworks, and develop practical roadmaps that align security capabilities with enterprise strategy. This role offers the opportunity to engage in technically hands-on architecture work alongside strategic advisory engagements across diverse industries.
Then Responsibilities:Responsibilities
- ... each bullet from "Your Key Responsibilities" list.
- for any list of duties/requirements/benefits. The responsibilities are listed as sentences; we can treat each sentence as a list item. Let's parse:
"You will evaluate existing security architectures, identify gaps and risks across network, cloud, application, data, and identity domains, and develop actionable recommendations grounded in industry frameworks and leading practices."
"You will design and document future-state security architectures, reference models, and security patterns that address client-specific risk profiles and business objectives, and support clients in defining technology roadmaps that guide security investment and capability development."
"In addition, as a Senior Consultant, you will contribute to the development of enterprise security architecture standards, policies, and governance frameworks that embed security requirements into technology and business change programs."
"You will support clients in applying Zero Trust principles, securing hybrid and multi-cloud environments, and aligning architecture decisions to established frameworks such as SABSA, TOGAF, and NIST."
"You will prepare client deliverables, architecture documentation, and executive-level presentations that communicate complex technical concepts to both technical and non-technical audiences."
"You will collaborate with multidisciplinary teams to deliver high-quality work products, support project planning and management activities, mentor junior team members, and contribute to business development initiatives, thought leadership, and practice-building efforts within EY's Cyber practice."
That's six bullets.
Now Skills And Attributes For Success: It's a long paragraph with many sentences separated by periods. We'll turn each sentence into a list item under Skills.
Let's extract sentences:
"Strong understanding of enterprise security architecture principles, patterns, and frameworks, with the ability to design solutions across network, cloud, application, data, identity, and endpoint security domains."
"Hands-on experience conducting security architecture assessments, threat modeling, and architecture risk analysis across complex enterprise environments."
"Ability to design and document security reference architectures, technology blueprints, and security patterns that align to business objectives and risk appetite."
"Experience applying Zero Trust architecture principles and translating them into practical, implementable security designs."
"Knowledge of cloud security architecture across major cloud platforms (AWS, Azure, GCP), including hybrid and multi-cloud environments."
"Familiarity with enterprise architecture frameworks such as SABSA, TOGAF, or Zachman as applied to security architecture engagements."
"Strong critical thinking, analytical, and problem-solving skills applied to complex security architecture challenges."
"Ability to communicate technical architecture concepts effectively to both engineering teams and executive stakeholders."
"Experience developing architecture documentation, executive presentations, and client-facing deliverables."
"Strong verbal and written communication skills."
"Ability to manage competing priorities in a fast-paced consulting environment."
"Strong attention to detail and commitment to high-quality client service."
"Ability to build relationships and collaborate effectively across multidisciplinary teams and client organizations."
"Demonstrated initiative, adaptability, and a commitment to continuous learning across an evolving technology and threat landscape."
That's 15 bullets.
Now Qualifications: We have "To Qualify for the Role, You Must Have" paragraph with bullet-like sentences separated by semicolons? Actually it's a paragraph with multiple items separated by semicolons? Let's parse:
"A bachelor's degree in Cybersecurity, Computer Science, Information Systems, Engineering, or a related field, and approximately 3–5 years of relevant experience; or a graduate degree and 2–4 years of relevant experience."
"Experience in one or more of the following areas:" then a list.
We need to capture all substantive info. We'll treat each distinct requirement as a list item.
First item: "A bachelor's degree in Cybersecurity, Computer Science, Information Systems, Engineering, or a related field, and approximately 3–5 years of relevant experience; or a graduate degree and 2–4 years of relevant experience."
Then the list of areas:
"Enterprise security architecture assessments and future-state architecture design"
"Network security architecture, including segmentation, secure access, and perimeter design"
"Cloud security architecture across AWS, Azure, or GCP, including IaaS, PaaS, and SaaS security"
"Identity and access management architecture, including Zero Trust and privileged access design"
"Application security architecture, secure SDLC, and DevSecOps integration"
"Data protection architecture, including encryption, data classification, and data loss prevention"
"Security architecture governance, standards development, and architecture review processes"
"Knowledge of cybersecurity frameworks and standards, including NIST CSF, NIST 800-53, ISO 27001/27002, CIS Controls, and SABSA."
"Experience conducting security architecture reviews, threat modeling, and risk assessments in complex enterprise environments."
"Strong Microsoft PowerPoint, Excel, and Word skills."
"Willingness to travel based on client and business needs; travel estimated at 25–50%"
That's many items.
Then "Ideally, You'll Also Have" list:
"Professional certifications such as CISSP, CCSP, SABSA Chartered Architect (SCF/SCM), TOGAF, or other relevant security architecture credentials."
"Hands-on experience with security architecture tooling, including architecture modeling platforms, threat modeling tools, and cloud-native security services."
"Experience designing and implementing Zero Trust architectures, including microsegmentation, identity-centric access, and continuous verification models."
"Knowledge of security technology domains including SIEM, SOAR, EDR/XDR, PAM, IAM, CNAPP, and CASB, with the ability to assess their architectural fit within enterprise environments."
"Exposure to regulatory and compliance requirements—such as HIPAA, PCI DSS, FISMA, GDPR, or NYDFS—and their implications for security architecture decisions."
"Experience facilitating client workshops, technical design sessions, and architecture review board engagements."
"Background in software development, infrastructure engineering, or network engineering that informs deep technical architecture credibility."
"Experience within a consulting, professional services, or advisory environment."
"Knowledge of regulated industries such as financial services, healthcare, life sciences, government, or critical infrastructure."
We'll treat each as list item under Qualifications (maybe separate Required and Preferred but we can combine). To avoid too many sections, we can have one Qualifications section with subheadings? But we cannot use other headings besides h3. Could we embed inside? Probably okay but not required. We'll just list all items as
- under Qualifications. Now "What We Look For" paragraph: "We are seeking professionals who combine deep technical security architecture expertise with the advisory skills needed to translate complex design decisions into clear, actionable client guidance. Successful candidates bring hands-on architecture experience across multiple security domains alongside strong business judgment and the ability to engage confidently with both engineering teams and executive stakeholders. The ideal candidate is passionate about designing security that enables business outcomes, committed to delivering exceptional client service, and eager to contribute to the growth and innovation of EY's Cyber practice." We