Sr. Product Analyst – Privacy Operations

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. We 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. Job Title: Sr. Product Analyst Privacy Operations Number of Openings: 1 Preferred Time zone if Remote: EST. hybrid(3 days in office, 2 remote) Willing to consider 100% remote for the right candidate Target Start Date: ASAP Interview Process: Virtual. 2 rounds Shift / Schedule: Standard 9-5 Then sections: PERFORMANCE DETAILS (objectives) etc. We need to extract: - About the role: description of role, objectives, what they will work on. Could be from "What are the major objective(s) of the role? Specifically, what does this person need to do to be considered a success? What will they be working on?" Then the paragraph about Privacy Operations team, partnership with Enterprise Technology Services, implementing OneTrust, supporting product owners, etc. - Responsibilities: list from "Key Responsibilities:" bullet list. - Requirements: maybe "MUST HAVE technologies" and "MUST HAVE Critical Skills". Could be combined into Requirements or Qualifications. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically Requirements = must-have technologies/skills; Qualifications = relevant experience; Skills = maybe nice-to-have? But we need to follow instruction: include a section only when posting has real specific content for it. We can allocate: - About the role: from performance details. - Responsibilities: from Key Responsibilities. - Requirements: from MUST HAVE technologies and MUST HAVE Critical Skills (maybe combine). - Qualifications: from Relevant Experience (required and preferred). - Skills: maybe from Nice to have technologies/skills? Or we could treat Skills as nice-to-have. But we need to ensure we don't create empty sections. - Benefits: from PRO038 Nesco Resource offers a comprehensive benefits package... includes MEC plan etc. - Pay: not mentioned; we should not create Pay section. - Schedule: from Shift / Schedule: Standard 9-5. Also hybrid info. So we can include Schedule section with that info. We must not include boilerplate like EEO etc. Remove that. We must not duplicate lines. We need to preserve all substantive info. Let's extract content. About the role: "The Privacy Operations team works to enhance the enterprise privacy program supporting both Client and Orange & Rockland in response to growing customer expectations, risk management imperatives, and current/evolving legal obligations around the collection, storage, processing, and sharing of personal data. In partnership with Enterprise Technology Services, the team is responsible for implementing and managing the technology using the OneTrust platform and the supporting business processes to create a privacy by design culture that embeds privacy protection and controls throughout the lifecycle of the data. The Senior Product Analyst will be responsible for supporting the Product Owners in product and feature development, testing, and documentation for data privacy governance with a specific focus on a new third-party data sharing governance platform." Also maybe include objectives: "What are the major objective(s) of the role? Specifically, what does this person need to do to be considered a success? What will they be working on?" But we already captured. We could also include "Target Start Date: ASAP" maybe in About the role? But schedule section covers shift. Target start date maybe not needed; but could be included in About the role as extra detail. However we should not invent sections; we can include it in About the role as a sentence. But we need to preserve all substantive info. So include Target Start Date: ASAP somewhere. Could be in About the role. Also Preferred Time zone if Remote: EST. hybrid(3 days in office, 2 remote) Willing to consider 100% remote for the right candidate. That's schedule/location info. Could go in Schedule section. Interview Process: Virtual. 2 rounds - maybe not needed; but it's substantive. Could be included in About the role or maybe a separate section? Not among headings. Could be omitted? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Could add a note in About the role or maybe a separate "Process" but not allowed headings. Could incorporate into About the role as a sentence: "The interview process is virtual with two rounds." Number of Openings: 1 - also substantive. Could be included in About the role. We must not repeat job title as heading. Now Requirements: Must have technologies: "Familiarity with One Trust familiarity with privacy, data governance, and risk management technologies Proficiency in Microsoft Office and related tools (Word, Excel, PowerPoint, Teams, SharePoint, Azure DevOps)". Note there is duplicate "Familiarity with One Trust". We'll combine. Must have Critical Skills: "Privacy & Data Governance Background Software implementation project experience business analysis and process documentation skills UAT/Testing and stakeholder management experience." We'll list as bullet list under Requirements. Qualifications: Relevant Experience: "Experience as an analyst or part of a product team on technology implementation projects, required. Ability to work independently and collaboratively with teammates and stakeholders to drive results and build consensus, required. Capable of managing multiple priorities and deadlines with attention to detail, required. Experience developing and delivering presentations and creating clear documentation for diverse audiences, required. Proficiency in Microsoft Office and related tools (Word, Excel, PowerPoint, Teams, SharePoint, Azure DevOps), required. Experience in a privacy or data governance-related role in operations, risk management and/or compliance, designing and/or implementing privacy program elements. Experience in a regulated environment (e.g., utility industry) preferred. Experience using or familiarity with privacy, data governance, and risk management technologies, especially OneTrust." We'll list bullet list. Skills: Nice to have: "Utility or regulated industry experience Cybersecurity knowledge- Understanding of privacy controls, data protection practices, and information security concepts." We'll list bullet list. Benefits: "Nesco Resource offers a comprehensive benefits package for our associates, which includes a MEC (Minimum Essential Coverage) plan that encompasses Medical, Vision, Dental, 401K, and EAP (Employee Assistance Program) services." Schedule: "Shift / Schedule: Standard 9-5" plus hybrid info: "Preferred Time zone if Remote: EST. hybrid(3 days in office, 2 remote) Willing to consider 100% remote for the right candidate." We'll combine. We should also include Target Start Date: ASAP maybe in About the role. Interview Process: Virtual. 2 rounds maybe also in About the role. Number of Openings: 1 maybe in About the role. Let's craft About the role paragraph(s) that include all those details. We'll produce HTML:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

...

Schedule

...

We must not include Pay section. Now ensure we don't repeat content. Let's extract each piece. About the role content: - Job Title: Sr. Product Analyst Privacy Operations (but we shouldn't repeat as heading; we can mention in paragraph maybe not needed but it's substantive? The instruction says do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid mentioning it in paragraph. Could include but maybe redundant. Safer to not include it; but we need to preserve all substantive info. The job title is already shown elsewhere; we can omit repeating it. However the number of openings, target start date, interview process, preferred time zone/hybrid, etc are substantive and not elsewhere. Let's compose: "The Sr. Product Analyst Privacy Operations role supports the Privacy Operations team in enhancing the enterprise privacy program for Client and Orange & Rockland, responding to customer expectations, risk management, and legal obligations around personal data. In partnership with Enterprise Technology Services, the team implements and manages the OneTrust platform to embed privacy‑by‑design controls throughout the data lifecycle. The analyst will support Product Owners in product and feature development, testing, and documentation for data privacy governance, focusing on a new third‑party data sharing governance platform. The position is targeted to start ASAP, with a virtual interview process consisting of two rounds. The role is hybrid (3 days in office, 2 days remote) in the EST time zone, with willingness to consider 100% remote for the right candidate. There is 1 opening." That covers number of openings, target start date, interview process, schedule/hybrid, time zone, remote willingness. Now Responsibilities: list from Key Responsibilities. Let's copy each bullet: - Coordinate with the project team and stakeholders in performing discovery and documentation of current state to design new processes and identify tooling. - Support the automation of privacy processes by documenting workflows and developing proof-of-concepts. - Contribute to the creation of strategic artifacts, such as wireframes and process flows, and produce formal documentation and presentations for internal and external audiences. - Collaborate with technical teams to support the integration of the privacy platform with other enterprise systems, such as ServiceNow. - Assist in the maintenance and enhancement of tools built on the OneTrust platform by supporting template updates, data migration, and troubleshooting technical issues with vendors. - Coordinate User Acceptance Tests (UAT) and serve as a tester, executing tasks based on Functional and UAT test scripts. - Participate in cross-functional efforts to identify capabilities, gaps, and opportunities in developing a data privacy governance framework within the overarching enterprise data governance framework and strategy. - Support a customer-centric and service-oriented culture, taking special interest in meeting the needs of our customers, employees, and other stakeholders. Now Requirements: Must have technologies and critical skills. We can combine into one list: - Familiarity with OneTrust - Familiarity with privacy, data governance, and risk management technologies - Proficiency in Microsoft Office and related tools (Word, Excel, PowerPoint, Teams, SharePoint, Azure DevOps) - Privacy & Data Governance background - Software implementation project experience - Business analysis and process documentation skills - UAT/Testing and stakeholder management experience Note: "Familiarity with One Trust" appears twice; we list once. Now Qualifications: from Relevant Experience. List: - Experience as an analyst or part of a product team on technology implementation projects (required) - Ability to work independently and collaboratively with teammates and stakeholders to drive results and build consensus (required) - Capable of managing multiple priorities and deadlines with attention to detail (required) - Experience developing and delivering presentations and creating clear documentation for diverse audiences (required) - Proficiency in Microsoft Office and related tools (Word, Excel, PowerPoint, Teams, SharePoint, Azure DevOps) (required) - Experience in a privacy or data governance-related role in operations, risk management and/or compliance, designing and/or implementing privacy program elements - Experience in a regulated environment (e.g., utility industry) (preferred) - Experience using or familiarity with privacy, data governance, and risk management technologies, especially OneTrust Note: Proficiency in Microsoft Office appears also in Requirements; but it's okay to repeat as it's substantive in both sections. However we might avoid duplication but instruction says preserve ALL substantive information; duplication is okay if it's in original. But we could keep it in both sections as it's present in both. However to reduce redundancy we could keep only in Qualifications (since it's required) and maybe not repeat in Requirements? But Requirements also includes proficiency in Microsoft Office as must-have technology. It