Cyber - Data Protection Microsoft 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", "To qualify for the role", "Ideally, you’ll also have...", "What We Look For", "What We Offer You". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Apply today", "To make the most of your application experience..." etc. Also remove EEO statement at end. Also remove "EY | Building a better working world" etc. We need to preserve all substantive information. So we need to keep location line? It says "Location: Anywhere in Country". That's minor metadata; we can fold into a short

or drop it. Probably include as a short paragraph. We need sections: About the role (intro), Responsibilities (Your Key Responsibilities), Requirements/Qualifications (To qualify for the role + Skills And Attributes For Success maybe combine?), Skills (maybe separate), Benefits (What We Offer You includes salary range and total rewards), Pay (salary range), Schedule? Not present, so omit. We should not create sections with filler like "commensurate with experience". We have salary ranges specific, so we can include Pay section. We need Benefits section: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. We need to avoid duplicating content. Let's extract substantive paragraphs. 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." "The Opportunity In a rapidly changing technology, data, privacy, and cybersecurity landscape, clients across industries look to us for trusted guidance on protecting information, enabling responsible data use, and managing risk. As a Senior within the Data Protection and Privacy team, you will serve as a junior Microsoft architect with primary expertise in Microsoft Purview and broader working knowledge across the Microsoft Security stack. You will help clients translate business, legal, privacy, regulatory, and security requirements into practical architecture, governance, and implementation approaches. This role is designed for a senior-level consulting professional who can lead defined workstreams, facilitate client discussions, produce high-quality solution designs, and guide implementation teams while continuing to develop toward a lead architect role. You will work across data protection, privacy, security, identity, endpoint, cloud, analytics, and AI governance stakeholders in complex enterprise environments." That's about the role. Then "Your Key Responsibilities As a Senior on the Data Protection and Privacy team, your key responsibilities would include:" followed by a long list of responsibilities separated by periods. We need to turn into

• items. Probably each sentence is a responsibility. We'll split by periods. List items: - Lead defined Microsoft Purview workstreams, including discovery, requirements gathering, design, configuration guidance, testing, deployment planning, and operational transition. - Design and support Microsoft Purview capabilities such as Information Protection, sensitivity labeling, Data Loss Prevention, Data Lifecycle Management, Records Management, Insider Risk Management, Communication Compliance, eDiscovery, Audit, Data Map, Data Catalog, and Data Security Posture Management. - Develop data classification, information protection, retention, DLP, insider risk, and data governance strategies that align to business objectives and legal, privacy, regulatory, and security requirements. - Support security and privacy assessments, architecture reviews, maturity assessments, control gap analyses, roadmaps, operating models, and governance frameworks. - Facilitate client workshops and stakeholder interviews across security, privacy, legal, compliance, records, data governance, technology, and business teams. - Translate business and control requirements into solution architectures, design decisions, implementation backlogs, user stories, test scenarios, and measurable outcomes. - Create clear architecture diagrams, reference patterns, configuration standards, decision papers, executive presentations, and technical implementation guidance. - Support integration of Microsoft Purview with Microsoft Defender, Intune, Sentinel, Entra, Azure, Fabric, Microsoft 365, and related data and security services. - Contribute to data security and AI governance initiatives, including protection of sensitive data used by Microsoft 365 Copilot, generative AI solutions, analytics platforms, and enterprise applications. - Provide technical direction to implementation resources, review deliverables for quality, identify risks and dependencies, and escalate design decisions when appropriate. - Mentor junior team members, contribute reusable assets and delivery methods, and support proposal development and solution shaping for Data Protection and Privacy opportunities. - Maintain awareness of Microsoft product developments, industry standards, privacy requirements, and emerging data security and AI risks. Now "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 list of skills. We can treat as Skills section. List items (split by periods after each ability): - Strong knowledge of data protection, information governance, privacy, compliance, and security concepts. - Practical experience designing or implementing Microsoft Purview capabilities in an enterprise environment. - Ability to connect technical platform features to business, legal, privacy, regulatory, 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, architecture diagrams, 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 team 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. Now "To qualify for the role, you must have:" then list of qualifications. We can treat as Requirements/Qualifications section. List items: - A bachelor’s degree in Computer Science, Computer Engineering, Cybersecurity, Information Systems, Data Science, Privacy, or a related field, or equivalent relevant experience. - Approximately 3-6 years of relevant experience in cybersecurity, data protection, privacy, compliance, cloud security, information governance, or related technology consulting. - Hands-on experience with Microsoft Purview, with depth in two or more areas such as Information Protection, Data Loss Prevention, Data Lifecycle Management, Records Management, Insider Risk Management, eDiscovery, Audit, Data Map, Data Catalog, or Data Security Posture Management. - Experience gathering requirements and translating them into architecture, solution design, configuration, testing, deployment, and operating model considerations. - Working knowledge of at least two additional Microsoft technologies, such as Microsoft Defender, Intune, Sentinel, Entra, Azure security services, Fabric, or Microsoft 365. - Ability to communicate effectively through client conversations, workshops, interviews, written deliverables, presentations, and technical documentation. - Experience supporting projects in large or complex enterprise environments with multiple business, legal, privacy, security, data, and technology stakeholders. - Understanding of security and privacy frameworks or 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 Microsoft certifications such as SC-400, SC-401, SC-100, SC-200, AZ-500, MS-102, or a demonstrated plan to obtain relevant certifications." plus many more ideal qualifications. We could include as part of Qualifications or Skills? Probably as additional qualifications (preferred). We'll include as part of Qualifications section maybe as a separate bullet list under "Preferred Qualifications". But we only have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat "Requirements" as mandatory, "Qualifications" as preferred. Or combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. Thus: - Requirements: mandatory qualifications. - Qualifications: preferred/certifications etc. Let's extract preferred qualifications: "Ideally, you’ll also have Microsoft certifications such as SC-400, SC-401, SC-100, SC-200, AZ-500, MS-102, or a demonstrated plan to obtain relevant certifications. Experience with Microsoft Defender for Cloud Apps, Defender for Endpoint, Defender XDR, Intune, Sentinel, Entra ID, Azure Policy, Azure security services, or Microsoft Fabric. Experience with data discovery, classification, catalog, privacy management, DLP, DSPM, cloud security, SIEM, identity, or endpoint security technologies outside the Microsoft ecosystem. Experience developing data protection, privacy, AI governance, Zero Trust, cloud security, or enterprise security architecture deliverables. Experience integrating Microsoft technologies with ticketing, data governance, analytics, cloud, or third-party security platforms. Ability to develop PowerPoint presentations and Visio or equivalent architecture diagrams that communicate complex topics 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 and coordinating work across technical and functional teams." We'll put these as
  • under Qualifications. Now "What We Look For" section: maybe we can treat as Skills or maybe as a separate section but not in list. Could incorporate into Skills or maybe as a short paragraph under About the role? But we have Skills section already. The "What We Look For" is a paragraph describing desired traits. Could be part of Skills or maybe a separate section like "About the role". But we already have About the role. We could add a short paragraph after About the role describing what we look for. However instruction: include a section ONLY when posting has real, specific content for it. We have content for "What We Look For". Could make a section named "What We Look For" but not in allowed headings list. The allowed headings are examples; we can use those headings but not required to stick exactly? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; but we could also use other headings? It says e.g., meaning examples. Probably we should stick to those headings. So we need to map content to those headings. "What We Look For" could be part of Skills or About the role. I'd incorporate into Skills section as a paragraph before list? But Skills already has list. Could add a paragraph describing desired traits then list. That's fine. Now "What We Offer You" includes salary range and total rewards. We need Pay section for salary range, Benefits section for medical/dental etc. Thus: - About the role: includes location line and intro paragraphs (The Opportunity etc.) - Responsibilities: list from Your Key Responsibilities. - Requirements: mandatory qualifications (the "To qualify for the role, you must have:" list) - Qualifications: preferred qualifications (Ideally, you’ll also have... list) - Skills: Skills And Attributes For Success list plus maybe What We Look For paragraph. - Pay: salary range details. - Benefits: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. We should not include Schedule. Now we need to ensure we don't include boilerplate like "Learn more at ey.com/us/careers." That's part of What We