Associate, Data Transformation & Governance

We need to output only HTML fragment, with headings

for 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 as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, legal, etc. Also remove application instructions. We need to parse the job description and extract sections. The posting includes: - Position Summary (maybe "About the role") - Essential Duties & Responsibilities (Responsibilities) - Qualifications & Requirements (Qualifications) - Preferred Experience (maybe Skills? Could be separate but we can include under Qualifications or Skills) - Success Measures (maybe not a standard heading; could be part of Responsibilities? Might be considered as performance metrics; but we have no heading for that; we could include under Responsibilities or maybe a separate section like "Success Measures" but not in allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have Pay: base salary range $76,000-$114,000. Benefits: Not explicitly listed; there is an "About Us" paragraph describing culture but not specific benefits. No explicit benefits like health insurance, 401k, etc. So we should not create Benefits section unless posting actually states them. It does not list benefits, so omit. Schedule: Not mentioned; omit. Skills: Could be derived from qualifications and preferred experience: e.g., ability to work with stakeholders, organizational, analytical, communication, documentation, follow-up skills; familiarity with tools; etc. We could create a Skills section with bullet points. Requirements: Might be same as Qualifications? The allowed headings include Requirements and Qualifications separately. We could put mandatory requirements under Requirements (e.g., 2+ years experience, bachelor's degree) and preferred qualifications under Qualifications or Skills. But we need to avoid duplication. Let's decide: - About the role: Position Summary paragraph(s). Could combine the initial paragraphs about vision, scope, role. - Responsibilities: Essential Duties & Responsibilities (the long list). We'll output as

• items. - Requirements: Mandatory qualifications: 2+ years experience in data governance etc; exposure to unstructured content; basic understanding of records retention; awareness of legal hold; exposure to M&A initiatives preferred? Actually "preferred" not mandatory. So mandatory: 2+ years experience in data governance, data management, data quality, data integration, records and information management, analytics, privacy and compliance, project coordination, or related enterprise technology roles. Experience supporting data governance, data quality, data documentation, data migration, integration, archival, analytics, or transformation activities. Exposure to unstructured content environments such as mail, file storage, or collaboration platforms, in addition to structured application data. Basic understanding of records retention concepts, including retention categories, retention periods, and disposal. Awareness of legal hold obligations and why routine disposal must be suspended when a hold is in effect. Exposure to merger, acquisition, divestiture, or acquired-company technology and data integration initiatives preferred (that's preferred, not mandatory). Basic understanding of data governance concepts... Experience maintaining data quality trackers... Familiarity with data catalogs... Basic understanding of privacy, data classification... Ability to work with business and technology stakeholders... Strong organizational, analytical, communication, documentation, and follow-up skills. Bachelor’s degree in Information Systems, Data Analytics, Business, Computer Science, Engineering, or related field required; relevant certifications preferred. We could split: Requirements = mandatory experience and education. Qualifications = preferred experience and certifications. Skills = specific skills (tools, stakeholder management, etc). But we need to avoid filler. Let's extract: Mandatory (Requirements): - 2+ years of experience in data governance, data management, data quality, data integration, records and information management, analytics, privacy and compliance, project coordination, or related enterprise technology roles. - Experience supporting data governance, data quality, data documentation, data migration, integration, archival, analytics, or transformation activities. - Exposure to unstructured content environments such as mail, file storage, or collaboration platforms, in addition to structured application data. - Basic understanding of records retention concepts, including retention categories, retention periods, and disposal. - Awareness of legal hold obligations and why routine disposal must be suspended when a hold is in effect. - Basic understanding of data governance concepts, including data ownership, data stewardship, critical data elements, metadata, data quality, lineage, catalog and glossary practice, retention, and governed data delivery. - Experience maintaining data quality trackers, remediation logs, reconciliation evidence, issue lists, meeting notes, documentation, or readiness materials. - Familiarity with data catalogs, metadata platforms, data quality tools, workflow tools, reporting tools, or data issue management capabilities preferred. (This says preferred, but we could still include under Requirements? Might be considered preferred; but we can put under Qualifications.) - Basic understanding of privacy, data classification, access management, masking, retention, and internal policy controls preferred. - Ability to work with business and technology stakeholders, follow structured processes, and maintain accurate governance documentation. - Strong organizational, analytical, communication, documentation, and follow-up skills. - Bachelor’s degree in Information Systems, Data Analytics, Business, Computer Science, Engineering, or related field required. Preferred (Qualifications): - Relevant data governance, privacy, records management, project management, or data certifications preferred. - Experience operating in a professional services, consulting, accounting, or complex enterprise environment. - Exposure to governance and data platform tools such as Microsoft Purview, Collibra, Informatica, Alation, Snowflake, Power BI, ServiceNow, or comparable technologies. - Exposure to retention, classification, or eDiscovery capabilities across mail, file storage, and collaboration platforms. - Experience supporting data archival, historical data retention, legacy system decommissioning, or compliance-driven data preservation activities. - Experience preparing governance templates, stewardship trackers, data readiness checklists, data quality scorecards, issue logs, or dashboard inputs. - Experience coordinating with implementation partners, systems integrators, vendors, or consulting teams. - Experience supporting cross-functional meetings with business, technology, risk, legal, privacy, security, and data stakeholders. Skills could be: Ability to work with stakeholders, strong organizational, analytical, communication, documentation, follow-up skills; familiarity with tools; etc. But we already have many skill-like items. Perhaps we can combine Qualifications and Skills: Qualifications for preferred experience, Skills for abilities/tools. But we must not create thin sections. Let's decide to have: - About the role (position summary) - Responsibilities (essential duties) - Requirements (mandatory experience/education) - Qualifications (preferred experience/certifications) - Skills (specific abilities: stakeholder collaboration, analytical, communication, documentation, organizational, follow-up; familiarity with data catalog/tools) - Pay (salary range) We'll omit Benefits and Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information. That means we must include all bullet points from responsibilities, all qualifications, etc. We must not omit any. We need to convert the long responsibilities list into
  • items. The list is long; we need to capture each bullet. The responsibilities are a paragraph with many sentences separated by periods. We need to split into logical items. The instruction: Use
    • for any list of duties/requirements/benefits. So we should treat each distinct duty as a list item. We'll need to parse the responsibilities section and break into items. Let's extract responsibilities sentences: "Help maintain data governance documentation that supports acquired-company integration, including standards, roles, ownership lists, stewardship trackers, escalation paths, and performance metric inputs." "Support governance activities for data transformation initiatives, including data migration, integration, modernization, archival, reporting, and analytics enablement workstreams." "Support build-out of the data estate inventory for assigned acquisitions, capturing structured application data alongside mailboxes, file storage, collaboration sites, chat and meeting content, service management records, and line-of-business repositories." "Record content attributes in the inventory, including category, sensitivity, ownership, business purpose, volume, and disposition, and keep entries current as discovery progresses." "Prepare summaries of content categories and handling direction for use by integration teams during migration planning." "Assist with review of unstructured and semi-structured content for regulated, privileged, personal, and client-confidential material, and document findings for follow-up." "Maintain ownership documentation for acquired-company data domains and track domains where an accountable owner has not yet been identified." "Maintain approval records for new or materially changed use of data, and for external sharing and third-party access, so the approval trail stays complete." "Flag data appearing in the environment without established ownership, registration, or approval, and route it for review." "Apply enterprise retention categories to acquired-company data and content under direction, and escalate items that do not classify cleanly." "Maintain records of retention periods, retention triggers, and disposal timing for acquired-company data and archived datasets, and track upcoming disposal eligibility." "Support disposal activities by preparing schedules, collecting approvals, and capturing evidence of completion." "Check and record legal hold and business hold status ahead of disposal, decommissioning, or archival activity, and maintain hold records through to release." "Document circumstances that extend retention beyond standard periods, including inherited contractual commitments, audit activity, and content with long-term business value, and help prepare exception or extension requests." "Capture record retention determinations made by service line quality and risk stakeholders for audit, tax, and advisory work, and reflect them in working documentation." "Record jurisdictional differences for assigned entities, including local privacy, data residency, and statutory retention requirements, and flag conflicts for review." "Support data quality and standardization activities by preparing profiling summaries, issue logs, remediation trackers, reconciliation evidence, and quality gate checklists." "Maintain data definitions, critical data element lists, metadata entries, lineage notes, and ownership documentation for assigned data domains or integration workstreams." "Maintain catalog and business glossary entries for assigned scope so consumers can determine meaning, context, and appropriate use." "Help coordinate data stewardship activities by tracking assigned actions, meeting notes, follow-ups, status updates, and open issues with data owners and stewards." "Assist with the use of governance technologies such as data catalog, metadata management, lineage, data quality, master data management, and data issue management tools." "Support IT, data platform teams, and vendors by documenting requirements, validating tool outputs, and preparing rollout or training materials for governance tools." "Assist Legal, Privacy, Risk, Compliance, and Security stakeholders with documenting data classification, access controls, masking requirements, retention expectations, and disposal evidence." "Prepare governance reports and status materials using inputs such as data quality scores, policy adherence, stewardship engagement, remediation progress, issue aging, and readiness status." "Maintain dashboards, trackers, meeting materials, and issue logs that communicate governance progress, risks, decisions needed, and assigned action items." "Participate in cross-functional working sessions and document decisions, actions, ownership, and follow-up items related to data governance and transformation readiness." "Support source-to-target mapping, lineage documentation, reconciliation tracking, data issue resolution, and integration readiness activities during acquired-company transformation efforts." "Promote consistent governance practices by maintaining accurate documentation, following enterprise standards, and helping teams understand governance requirements." "Identify opportunities to improve templates, trackers, documentation quality, reporting routines, and repeatable governance support processes." "Other duties as assigned." We'll keep all. Now Requirements: list each mandatory requirement as
    • . We'll need to decide which are mandatory vs preferred. The posting says "2+ years of experience in data governance, data management, data quality, data integration, records and information management, analytics, privacy and compliance, project coordination, or related enterprise technology roles." That's mandatory. "Experience supporting data governance, data quality, data documentation, data migration, integration, archival, analytics, or transformation activities." Mandatory. "Exposure to unstructured