Cyber - Data Protection Zscaler Architect - Senior - Consulting
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - Location: Anywhere in Country (but location is metadata; we can fold into a short
maybe). - Intro paragraph about EY. - The opportunity paragraph describing role. - "Your Key Responsibilities" list. - "Skills And Attributes For Success" paragraph. - "To qualify for the role, you must have:" list of qualifications. - "Ideally, you’ll also have" list (preferred qualifications). - "What We Look For" paragraph. - "What We Offer You" includes salary ranges and benefits description. - Then application instructions etc which we should remove. We need to decide sections: About the role (intro + opportunity?), Responsibilities (Your Key Responsibilities), Requirements (maybe qualifications?), Qualifications (maybe same as Requirements?), Skills (Skills And Attributes For Success), Benefits (What We Offer You includes benefits), Pay (salary range), Schedule (none). We should not create empty sections. We need to preserve all substantive info, not invent. We must not repeat job title as heading. No Job ID. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove "Are you ready to shape your future with confidence? Apply today..." and the lines about limiting applications, etc. Also remove the EY values paragraph at end? That might be considered boilerplate? It's about EY building a better working world; could be considered generic but maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EY values paragraph is not exactly those, but could be considered boilerplate? It's more about company mission. Might be okay to keep? However it's somewhat generic; but not explicitly prohibited. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can keep the mission statement. But we also need to not create sections with filler.
We need to decide which sections to include.
Let's extract content:
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."
Opportunity paragraph: "The opportunity In a rapidly changing technology, data, privacy, and cybersecurity landscape, clients across industries look to us for trusted guidance on designing secure, resilient, and well-governed zero trust environments. As a Senior within the Data Protection and Privacy team, you will serve as a developing Zscaler Architect with experience across secure access service edge, zero trust network access, secure internet access, digital experience, and data protection. Zscaler experience is required, and the role is intended for a senior consulting professional who can lead defined solution areas while supporting broader architecture across identity, endpoint, network, cloud, security operations, data governance, and relevant third-party technologies. The Senior is expected to lead defined workstreams, facilitate client discussions, develop solution designs, guide implementation activities, and produce high-quality architecture and delivery artifacts while working under the direction of a Manager or senior architect for complex or enterprise-wide decisions. You will help clients translate business, security, privacy, legal, regulatory, and technology requirements into practical zero trust designs, roadmaps, governance approaches, and implementation plans."
Then "Your Key Responsibilities As a Senior on the Data Protection and Privacy team, your key responsibilities would include:" followed by a long sentence with many responsibilities separated by periods? Actually it's a long paragraph with many items separated by periods. We need to treat as list? The instruction: use
- for any list of duties/requirements/benefits. The responsibilities are enumerated via commas and periods; we could split into list items. Better to make each responsibility as
- . We'll need to parse.
Responsibilities list (from text):
- Lead defined Zscaler security and data protection workstreams, including discovery, requirements gathering, design, configuration guidance, testing, deployment planning, and operational transition.
- Design and support solutions across the Zscaler Zero Trust Exchange, with particular emphasis on Zscaler Internet Access, Zscaler Private Access, Zscaler Digital Experience, Zscaler Client Connector, and related data protection capabilities.
- Develop secure internet and SaaS access designs covering secure web gateway, cloud access security broker, cloud firewall, sandboxing, SSL inspection, browser isolation, threat protection, and policy enforcement patterns.
- Develop zero trust private application access designs covering application segmentation, access policies, App Connector placement, third-party access, privileged remote access, and migration from legacy VPN approaches.
- Incorporate data protection requirements into Zscaler designs, including cloud DLP, SaaS security, inline inspection, policy configuration, incident workflows, and integration with enterprise data protection controls.
- Support zero trust, secure access, data protection, cloud, branch, workload, identity, endpoint, and digital experience assessments, roadmaps, and architecture activities.
- Facilitate client workshops and stakeholder interviews across security, privacy, legal, compliance, network, infrastructure, cloud, identity, endpoint, application, data governance, and security operations teams.
- Translate requirements into architecture diagrams, traffic-flow designs, policy models, integration requirements, user stories, migration plans, test scenarios, operational procedures, and measurable outcomes.
- Create clear reference patterns, configuration standards, design decisions, executive presentations, and technical implementation guidance.
- Support integrations with identity providers, endpoint and device management platforms, SIEM and SOAR technologies, IT service management tools, network infrastructure, cloud platforms, data security tools, and other third-party controls.
- Track workstream scope, activities, risks, issues, dependencies, decisions, and status, escalating material concerns to engagement leadership when appropriate.
- Provide technical direction to junior resources, review work products for quality, and contribute to an inclusive and collaborative delivery environment.
- Support proposals, statements of work, estimates, demonstrations, and client presentations for Zscaler and zero trust opportunities.
- Develop reusable design artifacts and delivery accelerators while maintaining awareness of Zscaler platform developments and emerging zero trust, cloud, data, and AI security risks.
That's a list.
Next: "Skills And Attributes For Success To thrive in this role, you will need a blend of consulting, architecture, technical, and business skills, together with the judgment to operate independently within a defined scope and seek senior architect guidance when appropriate." Then bullet-like sentences (but not list). We could treat as
prose.
Then "To qualify for the role, you must have:" followed by list of qualifications.
Qualifications list:
- A bachelor’s degree in Computer Science, Computer Engineering, Cybersecurity, Information Systems, Network Engineering, Data Science, Privacy, or a related field, or equivalent relevant experience.
- Approximately 3-6 years of relevant experience in cybersecurity, network security, zero trust, data protection, identity, endpoint, cloud security, privacy, compliance, or related technology consulting.
- Required hands-on implementation, engineering, or architecture experience with Zscaler, including experience with Zscaler Internet Access or Zscaler Private Access.
- Working knowledge of additional Zscaler capabilities such as Zscaler Digital Experience, Zscaler Client Connector, data protection, browser security, cloud and workload security, or branch and campus use cases.
- Experience supporting requirements, design, integration, configuration, testing, migration, deployment, or operational transition activities for enterprise Zscaler solutions.
- Knowledge of secure web gateway, zero trust network access, cloud access security broker, cloud firewall, SSL inspection, threat protection, application segmentation, or data loss prevention use cases.
- Ability to communicate effectively through client conversations, workshops, interviews, written deliverables, presentations, and technical documentation.
- Experience supporting projects in large or complex enterprise environments involving multiple security, network, cloud, identity, endpoint, privacy, and business stakeholders.
- Understanding of zero trust, security, or privacy frameworks and regulations such as NIST, ISO 27001, CIS Controls, GDPR, CCPA/CPRA, HIPAA, or other applicable requirements.
- Ability to travel as required by client and engagement needs.
Then "Ideally, you’ll also have" list (preferred qualifications):
- Current or planned Zscaler certifications aligned to administration, engineering, architecture, or implementation responsibilities, together with relevant industry certifications in security, networking, cloud, or zero trust.
- Experience with Zscaler Digital Experience, Client Connector, cloud and workload security, branch and campus use cases, browser security, privileged remote access, and data protection capabilities.
- Experience integrating Zscaler with identity providers, endpoint management, SIEM and SOAR, IT service management, cloud platforms, security operations, network services, or third-party data security technologies.
- Experience supporting enterprise zero trust, secure access service edge, data protection, cloud security, identity, endpoint, branch, or network transformation initiatives.
- Experience producing architecture deliverables such as current- and target-state diagrams, traffic-flow diagrams, reference designs, control mappings, design decision records, migration plans, and transition architectures.
- Strong PowerPoint and architecture diagramming skills, including the ability to communicate complex concepts to executive, business, and technical audiences.
- Proficiency with consulting engagement methods, work planning, estimation, status reporting, risk management, and quality review.
- Experience mentoring junior resources or coordinating work across technical and functional teams.
Then "What We Look For" paragraph.
Then "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. The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $125,800 to $209,700 Bay Area California offices – $131,100 to $218,500 All other offices locations in the US, including Sacramento – $104,800 to $192,200 Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. 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."
Thus we have Pay (salary range) and Benefits (medical/dental, pension/401k, PTO). Also maybe "Learn more at ey.com/us/careers" is a link but we can keep as prose.
Schedule: none.
Thus sections: About the role (intro + opportunity), Responsibilities, Skills (Skills And Attributes For Success), Requirements (qualifications), Preferred Qualifications (maybe we can combine into Requirements? But we have both required and preferred; we could have Requirements section for required, and maybe an Additional Qualifications or Preferred Qualifications. The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They list Qualifications as a possible heading. So we could have Requirements for required qualifications, and Qualifications for preferred? Or we could combine both under Qualifications. But we need to avoid thin sections. Perhaps we have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (skills). The posting also has "Skills And Attributes For Success" which is skills.
Thus sections:
- About the role (intro + opportunity)
- Responsibilities
- Skills And Attributes For Success (Skills)
- Requirements (required qualifications)
- Qualifications (preferred qualifications) maybe.
- Benefits
- Pay
We need to ensure we don't create sections with filler. All have
for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove "Are you ready to shape your future with confidence? Apply today..." and the lines about limiting applications, etc. Also remove the EY values paragraph at end? That might be considered boilerplate? It's about EY building a better working world; could be considered generic but maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EY values paragraph is not exactly those, but could be considered boilerplate? It's more about company mission. Might be okay to keep? However it's somewhat generic; but not explicitly prohibited. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can keep the mission statement. But we also need to not create sections with filler. We need to decide which sections to include. Let's extract content: 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." Opportunity paragraph: "The opportunity In a rapidly changing technology, data, privacy, and cybersecurity landscape, clients across industries look to us for trusted guidance on designing secure, resilient, and well-governed zero trust environments. As a Senior within the Data Protection and Privacy team, you will serve as a developing Zscaler Architect with experience across secure access service edge, zero trust network access, secure internet access, digital experience, and data protection. Zscaler experience is required, and the role is intended for a senior consulting professional who can lead defined solution areas while supporting broader architecture across identity, endpoint, network, cloud, security operations, data governance, and relevant third-party technologies. The Senior is expected to lead defined workstreams, facilitate client discussions, develop solution designs, guide implementation activities, and produce high-quality architecture and delivery artifacts while working under the direction of a Manager or senior architect for complex or enterprise-wide decisions. You will help clients translate business, security, privacy, legal, regulatory, and technology requirements into practical zero trust designs, roadmaps, governance approaches, and implementation plans." Then "Your Key Responsibilities As a Senior on the Data Protection and Privacy team, your key responsibilities would include:" followed by a long sentence with many responsibilities separated by periods? Actually it's a long paragraph with many items separated by periods. We need to treat as list? The instruction: use
- for any list of duties/requirements/benefits. The responsibilities are enumerated via commas and periods; we could split into list items. Better to make each responsibility as
- . We'll need to parse.
Responsibilities list (from text):
- Lead defined Zscaler security and data protection workstreams, including discovery, requirements gathering, design, configuration guidance, testing, deployment planning, and operational transition.
- Design and support solutions across the Zscaler Zero Trust Exchange, with particular emphasis on Zscaler Internet Access, Zscaler Private Access, Zscaler Digital Experience, Zscaler Client Connector, and related data protection capabilities.
- Develop secure internet and SaaS access designs covering secure web gateway, cloud access security broker, cloud firewall, sandboxing, SSL inspection, browser isolation, threat protection, and policy enforcement patterns.
- Develop zero trust private application access designs covering application segmentation, access policies, App Connector placement, third-party access, privileged remote access, and migration from legacy VPN approaches.
- Incorporate data protection requirements into Zscaler designs, including cloud DLP, SaaS security, inline inspection, policy configuration, incident workflows, and integration with enterprise data protection controls.
- Support zero trust, secure access, data protection, cloud, branch, workload, identity, endpoint, and digital experience assessments, roadmaps, and architecture activities.
- Facilitate client workshops and stakeholder interviews across security, privacy, legal, compliance, network, infrastructure, cloud, identity, endpoint, application, data governance, and security operations teams.
- Translate requirements into architecture diagrams, traffic-flow designs, policy models, integration requirements, user stories, migration plans, test scenarios, operational procedures, and measurable outcomes.
- Create clear reference patterns, configuration standards, design decisions, executive presentations, and technical implementation guidance.
- Support integrations with identity providers, endpoint and device management platforms, SIEM and SOAR technologies, IT service management tools, network infrastructure, cloud platforms, data security tools, and other third-party controls.
- Track workstream scope, activities, risks, issues, dependencies, decisions, and status, escalating material concerns to engagement leadership when appropriate.
- Provide technical direction to junior resources, review work products for quality, and contribute to an inclusive and collaborative delivery environment.
- Support proposals, statements of work, estimates, demonstrations, and client presentations for Zscaler and zero trust opportunities.
- Develop reusable design artifacts and delivery accelerators while maintaining awareness of Zscaler platform developments and emerging zero trust, cloud, data, and AI security risks.
That's a list.
Next: "Skills And Attributes For Success To thrive in this role, you will need a blend of consulting, architecture, technical, and business skills, together with the judgment to operate independently within a defined scope and seek senior architect guidance when appropriate." Then bullet-like sentences (but not list). We could treat as
prose. Then "To qualify for the role, you must have:" followed by list of qualifications. Qualifications list: - A bachelor’s degree in Computer Science, Computer Engineering, Cybersecurity, Information Systems, Network Engineering, Data Science, Privacy, or a related field, or equivalent relevant experience. - Approximately 3-6 years of relevant experience in cybersecurity, network security, zero trust, data protection, identity, endpoint, cloud security, privacy, compliance, or related technology consulting. - Required hands-on implementation, engineering, or architecture experience with Zscaler, including experience with Zscaler Internet Access or Zscaler Private Access. - Working knowledge of additional Zscaler capabilities such as Zscaler Digital Experience, Zscaler Client Connector, data protection, browser security, cloud and workload security, or branch and campus use cases. - Experience supporting requirements, design, integration, configuration, testing, migration, deployment, or operational transition activities for enterprise Zscaler solutions. - Knowledge of secure web gateway, zero trust network access, cloud access security broker, cloud firewall, SSL inspection, threat protection, application segmentation, or data loss prevention use cases. - Ability to communicate effectively through client conversations, workshops, interviews, written deliverables, presentations, and technical documentation. - Experience supporting projects in large or complex enterprise environments involving multiple security, network, cloud, identity, endpoint, privacy, and business stakeholders. - Understanding of zero trust, security, or privacy frameworks and regulations such as NIST, ISO 27001, CIS Controls, GDPR, CCPA/CPRA, HIPAA, or other applicable requirements. - Ability to travel as required by client and engagement needs. Then "Ideally, you’ll also have" list (preferred qualifications): - Current or planned Zscaler certifications aligned to administration, engineering, architecture, or implementation responsibilities, together with relevant industry certifications in security, networking, cloud, or zero trust. - Experience with Zscaler Digital Experience, Client Connector, cloud and workload security, branch and campus use cases, browser security, privileged remote access, and data protection capabilities. - Experience integrating Zscaler with identity providers, endpoint management, SIEM and SOAR, IT service management, cloud platforms, security operations, network services, or third-party data security technologies. - Experience supporting enterprise zero trust, secure access service edge, data protection, cloud security, identity, endpoint, branch, or network transformation initiatives. - Experience producing architecture deliverables such as current- and target-state diagrams, traffic-flow diagrams, reference designs, control mappings, design decision records, migration plans, and transition architectures. - Strong PowerPoint and architecture diagramming skills, including the ability to communicate complex concepts to executive, business, and technical audiences. - Proficiency with consulting engagement methods, work planning, estimation, status reporting, risk management, and quality review. - Experience mentoring junior resources or coordinating work across technical and functional teams. Then "What We Look For" paragraph. Then "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. The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $125,800 to $209,700 Bay Area California offices – $131,100 to $218,500 All other offices locations in the US, including Sacramento – $104,800 to $192,200 Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. 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." Thus we have Pay (salary range) and Benefits (medical/dental, pension/401k, PTO). Also maybe "Learn more at ey.com/us/careers" is a link but we can keep as prose. Schedule: none. Thus sections: About the role (intro + opportunity), Responsibilities, Skills (Skills And Attributes For Success), Requirements (qualifications), Preferred Qualifications (maybe we can combine into Requirements? But we have both required and preferred; we could have Requirements section for required, and maybe an Additional Qualifications or Preferred Qualifications. The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They list Qualifications as a possible heading. So we could have Requirements for required qualifications, and Qualifications for preferred? Or we could combine both under Qualifications. But we need to avoid thin sections. Perhaps we have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (skills). The posting also has "Skills And Attributes For Success" which is skills. Thus sections: - About the role (intro + opportunity) - Responsibilities - Skills And Attributes For Success (Skills) - Requirements (required qualifications) - Qualifications (preferred qualifications) maybe. - Benefits - Pay We need to ensure we don't create sections with filler. All have