Cyber Data Privacy Specialist - Senior Consultant

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract content: First paragraph: "As a Senior Consultant in Deloitte's Digital Trust & Privacy practice, you will support the design and implementation of privacy technology solutions that help organizations address regulatory requirements, strengthen data governance, and enable trusted business outcomes. You will contribute across configuration, integration, testing, and deployment activities while working with client, vendor, and cross-functional teams. This role offers the opportunity to take on increased ownership in privacy-by-design initiatives, Consent & Preference Management, and AI governance efforts, and large-scale technology implementations. Recruiting for this role ends on 12/31/2026." We can treat this as About the role (or maybe "About the role" heading). Should we include recruiting end date? It's metadata; we can fold into short p. Next: "Work you'll do" then bullet list? Actually it's sentences: "Strategize with clients to identify privacy technology gaps that can be addressed with technology to enable future state privacy goals and navigate complex IT architectures to incorporate privacy technology solutions. Lead working sessions with client stakeholders to gather technical, functional, and business requirements and establish use cases to inform future state architecture. General awareness of global and domestic privacy regulations and concepts, and how they relate to the deployment of technology in line with applicable laws and regulations, and general knowledge of integrating technologies with third-party tools and APIs. Configure, integrate, test, and deploy privacy tools and technologies to help clients automate their privacy capabilities and enhance customer experiences. Coordinate with client stakeholders and technology vendor representatives to clarify queries, troubleshoot implementation issues, and test end-to-end deployment and system integrations, and manage and execute project activities across the IT Software Development Life Cycle (SDLC) including leading regular check-ins with team members and vendors Develop and maintain technical configuration documentation, and manage and provide technical oversight to solution deployment and rollout." These are responsibilities. So we can put under Responsibilities heading with

• . Next: "Required Qualifications:" then list: - Bachelor's degree in Computer Science, Computer Engineering, Information Technology, or similar Engineering disciplines - 4+ years of experience in software design, architecture development, and technology implementation - 2+ years of experience with OneTrust and other technologies - 1+ years of implementation experience with OneTrust, Ketch, Transcend, Cassie, or Securiti's Consent & Preference Management solution - Ability to travel 25-75%, on average, based on the work you do and the clients and industries/sectors you serve These are required qualifications. Then "Preferred Qualifications:" then a long list broken into categories: Technical Skills, Communication Skills, Project Management Experience, Teamwork and Collaboration, Change Management, Master's degree..., Certifications..., Experience with application development..., Understanding of Ad-Tech / Mar-Tech..., Limited sponsorship may be available. We need to decide sections: Could have Requirements (maybe required qualifications) and Qualifications (preferred). Or we could combine required and preferred under Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for required qualifications, Qualifications for preferred qualifications, Skills for technical skills etc. But we also have a separate Skills heading maybe for technical skills list. However the preferred qualifications includes many categories: Technical Skills, Communication Skills, Project Management Experience, Teamwork and Collaboration, Change Management, etc. Could split them into Skills (technical) and maybe other sections? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put technical skills under Skills. Communication, Project Management, Teamwork, Change Management could go under Qualifications? Or we could incorporate them into Qualifications as bullet points. We need to preserve all substantive info. So we need to include all preferred qualifications details. We can structure:

  About the role

  ... (including recruiting end date maybe)

  Responsibilities

  • ... each responsibility

  Requirements

  • ... required qualifications

  Qualifications

  • ... preferred qualifications (maybe grouped)

  Skills

  • ... technical skills from preferred qualifications
  But that would duplicate some content (technical skills appear both in Qualifications and Skills). Better to split: Qualifications heading for education/experience preferences (Master's degree, certifications, etc.) and Skills heading for technical skills list. Communication, Project Management, Teamwork, Change Management could be placed under Qualifications as well (they are more like competencies). Or we could put them under Skills as well (they are skills). But we have only one Skills heading; we could include all skill-related items there: technical skills, communication skills, project management, teamwork, change management. That seems appropriate. Thus: - About the role: paragraph summarizing role and recruiting end date. - Responsibilities: list of work you'll do. - Requirements: required qualifications (bullet list). - Skills: all preferred qualifications items (technical skills, communication skills, project management experience, teamwork and collaboration, change management, plus maybe Master's degree, certifications, experience with application development, understanding of Ad-Tech/Mar-Tech, limited sponsorship). However some of those are not strictly skills but qualifications (education, certifications). But we can still include them under Skills heading as they are preferences. The instruction says prefer a few substantive sections over many thin ones. So we could combine all preferred qualifications into one section called Qualifications (or Skills). But we already have Requirements for required. Then we could have Qualifications for preferred (including education, certifications, technical skills, etc.). That would be one section. Then we might not need Skills separate. However we have to use headings from list; we can omit Skills if not needed. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can decide to have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That seems fine. We'll not create Skills, Benefits, Pay, Schedule unless present. Benefits not mentioned. Pay is mentioned: wage range $105,400 - $207,800 and discretionary annual incentive program. That is pay info. So we should include Pay section. Schedule: travel ability 25-75% mentioned under required qualifications (Ability to travel 25-75%). That's schedule? It's travel percentage. Could be considered Schedule. But we already have travel under Requirements. However we could also create a Schedule section for travel expectation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated, so include Pay. Schedule: travel percentage is stated, but is that schedule? It's about travel requirement, not work schedule. Might be considered Schedule? The heading list includes Schedule as possible. The posting mentions ability to travel 25-75% based on work. That's more about travel expectation, not schedule like full-time/part-time. Might be okay to put under Requirements. But we could also create a Schedule section with that detail. However we already have travel in Required Qualifications; moving it to Schedule would duplicate or remove from Requirements. We should preserve all info; we can keep it in Requirements and also maybe not create Schedule section to avoid thin section. Since we already have travel info, we can keep it there. The instruction: prefer a few substantive sections over many thin ones. So we likely won't add Schedule unless we have other schedule info (like remote/hybrid). Not present. So we omit Schedule. Benefits: not mentioned besides discretionary annual incentive program (which is part of compensation). Could be considered Benefits but it's incentive. Not explicit benefits like health, retirement. So we omit Benefits. Pay: we have wage range and discretionary annual incentive program. So we create Pay section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Now we need to extract content precisely. About the role paragraph: combine first paragraph plus maybe the recruiting end date. Original: "As a Senior Consultant in Deloitte's Digital Trust & Privacy practice, you will support the design and implementation of privacy technology solutions that help organizations address regulatory requirements, strengthen data governance, and enable trusted business outcomes. You will contribute across configuration, integration, testing, and deployment activities while working with client, vendor, and cross-functional teams. This role offers the opportunity to take on increased ownership in privacy-by-design initiatives, Consent & Preference Management, and AI governance efforts, and large-scale technology implementations. Recruiting for this role ends on 12/31/2026." We'll put that in

  . Responsibilities: list each bullet. Let's list them: - Strategize with clients to identify privacy technology gaps that can be addressed with technology to enable future state privacy goals and navigate complex IT architectures to incorporate privacy technology solutions. - Lead working sessions with client stakeholders to gather technical, functional, and business requirements and establish use cases to inform future state architecture. - General awareness of global and domestic privacy regulations and concepts, and how they relate to the deployment of technology in line with applicable laws and regulations, and general knowledge of integrating technologies with third-party tools and APIs. - Configure, integrate, test, and deploy privacy tools and technologies to help clients automate their privacy capabilities and enhance customer experiences. - Coordinate with client stakeholders and technology vendor representatives to clarify queries, troubleshoot implementation issues, and test end-to-end deployment and system integrations, and manage and execute project activities across the IT Software Development Life Cycle (SDLC) including leading regular check-ins with team members and vendors - Develop and maintain technical configuration documentation, and manage and provide technical oversight to solution deployment and rollout. Make each

• . Requirements: required qualifications list: - Bachelor's degree in Computer Science, Computer Engineering, Information Technology, or similar Engineering disciplines - 4+ years of experience in software design, architecture development, and technology implementation - 2+ years of experience with OneTrust and other technologies - 1+ years of implementation experience with OneTrust, Ketch, Transcend, Cassie, or Securiti's Consent & Preference Management solution - Ability to travel 25-75%, on average, based on the work you do and the clients and industries/sectors you serve Qualifications: preferred qualifications list (all items under Preferred Qualifications). We need to capture them exactly as listed, preserving details. Preferred Qualifications block: "Technical Skills Understand marketing technologies, including customer data platforms, consent, cookies, tag management solutionsAbility to understand, develop and enhance existing client architectures and solution designs to meet data privacy requirementsPrior experience in performing SaaS implementations for complex organizations and IT ecosystems.Ability to comprehend and execute basic technology concepts such as Application Programming Interfaces (API's), system requests methods (GET/POST), etc.Demonstrated experience in performing integrations with Marketing Platforms (e.g., Sales Force Marketing Cloud), Master Data Management (e.g., Informatica MDM) and middleware (MuleSoft, Kafka)Familiarity with privacy tools such as OneTrust, BigID, Securiti.ai, etc.Hands-on experience and knowledge of software engineering concepts/technologies, such as:JavaScript, RESTful APIs, HTTP Requests, JDBC, HTML CSSSQL, NoSQL, database management conceptsAPI management tools such as Apigee, PostmanAgile/Scrum methodology to build and rollout complex software solutionsUnderstanding of privacy program requirements and capabilities such as data inventory, data subject rights, consent and preference management, privacy by design, privacy impact assessments, incident response, third-party risk, etc.Knowledge of Data Privacy Laws and Regulations: Familiarity with data privacy legislation such as GDPR,