Cyber - Data Protection Zscaler Architect - Senior - 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", "What We Look For", "What We Offer You". Also salary range info. No Pay/Schedule/Benefits unless explicitly present. There's salary range and total rewards mention (medical, dental, pension, 401k, PTO). That's benefits. So we can include Benefits section. Pay section: we have salary range details, so we can include Pay. Schedule not present, so omit. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes some legal at end: "EY provides equal e" truncated; we should drop that. We need to include sections only when there is real specific content. Let's extract content: Location: Anywhere in Country (maybe we can include as a short paragraph? It's metadata; we can fold into a short

  or drop. Probably include as a short p. 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 prose. "The opportunity" paragraph: "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" heading followed by bullet list (actually sentences separated by periods). We need to convert to

  • . Each bullet is a sentence starting with a verb. We'll split. List items: - 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. Then "Skills And Attributes For Success" heading with prose paragraphs and then bullet list of qualifications? Actually after that heading there is prose: "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 a list of bullet-like sentences (starting with Strong understanding..., Ability..., etc). Those are skills. We'll treat as
    • . List: - Strong understanding of zero trust, secure access, network security, cloud security, and data protection concepts. - Practical experience designing or implementing Zscaler capabilities in an enterprise environment. - Ability to understand trust boundaries, traffic flows, dependencies, integration patterns, policy requirements, and control responsibilities. - Ability to connect Zscaler platform capabilities to business, legal, privacy, regulatory, security, and operational outcomes. - Ability to lead discovery sessions, workshops, design discussions, demonstrations, and working sessions with technical and non-technical stakeholders. - Ability to create high-quality client deliverables, reports, roadmaps, presentations, traffic-flow diagrams, architecture designs, and implementation guidance. - Strong analytical and problem-solving skills, including the ability to evaluate options, document tradeoffs, and make well-supported recommendations. - Ability to recognize and escalate risks, issues, dependencies, and opportunities to appropriate client and engagement leadership. - Ability to work collaboratively in culturally diverse, cross-functional, and geographically dispersed teams. - Commitment to service quality, project management disciplines, documentation standards, and continuous learning. Then "To qualify for the role, you must have:" followed by bullet list of requirements. That could be considered Requirements section. We'll create a Requirements section with
      • . 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" bullet list of preferred qualifications. Could be part of Requirements or separate "Preferred Qualifications". We'll include as part of Requirements maybe as a sublist? But spec says use
        • for any list of duties/requirements/benefits. We can keep as same Requirements section, but maybe separate "Preferred Qualifications". However we need to avoid too many thin sections. Could combine into Requirements with note "Preferred". But better to keep as Requirements (must have) and then maybe "Preferred Qualifications". However we need to decide if we want separate section. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine both must-have and ideal into one Requirements section, but we could separate into two subheadings? Not allowed because only

          for section headings. Could have two

          sections: Requirements and Preferred Qualifications. That's two sections, still okay. But we need to see if there is enough content for each. There is a decent list for both. We'll make Requirements (must have) and Preferred Qualifications. Then "What We Look For" heading with prose. That's a section. Then "What We Offer You" heading with prose about total rewards and salary range. We'll split into Pay and Benefits sections. Pay: salary range details. Benefits: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. We must not include sections with filler like "commensurate with experience". Not present. Now produce HTML. Structure:

          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.

          About the role

          maybe? The posting has "The opportunity". Could use that as heading. But we already have intro paragraphs. Could make a section "About the role" with the opportunity paragraph. However instruction: Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings where applicable. So we need to map content to those headings. Thus: - About the role: use the "The opportunity" paragraph (maybe also include location? but location already separate). We'll put the opportunity paragraph under About the role. - Responsibilities: "Your Key Responsibilities" list. - Skills: "Skills And Attributes For Success" list. - Requirements: "To qualify for the role, you must have:" list. - Qualifications: maybe "Ideally, you’ll also have" list (preferred). Or we could combine into Requirements but we have Qualifications heading available. - Benefits: medical/dental, pension/401k, PTO. - Pay: salary range details. We also have "What We Look For" and "What We Offer You". Those could be merged into existing sections? "What We Look For" could be part of Skills or Requirements? But we already have Skills and Requirements. Could treat "What We Look For" as a separate section maybe "About the team"? Not in list. But we could incorporate into Skills or Requirements. However instruction: Prefer few substantive sections over many thin ones. We already have many sections: About the role, Responsibilities, Skills, Requirements, Qualifications, Benefits, Pay. That's 7 sections. Adding What We Look For would be 8. Could we merge What We Look For into Skills or Requirements? It's about looking for collaborative, curious, accountable professionals, passionate about zero trust, etc. That's more like desired attributes, could go under Skills or Qualifications. Since we already have Skills and Qualifications, we could add those points to Skills section as extra bullets. But we must preserve all substantive information