Manager, Data Transformation & Governance

We need to output only HTML fragment with headings

for sections present. Need to extract sections: About the role (position summary), Responsibilities (Essential Duties & Responsibilities), Requirements (Qualifications & Requirements). Possibly also Skills? Not separate. Benefits, Pay, Schedule not present. So we include only those three sections. We must preserve all substantive info, not invent. Use

• for any list of duties/requirements/benefits. The responsibilities are a long paragraph with many sentences; we could break into list items per duty? The instruction: Use
  • for any list of duties/requirements/benefits. The responsibilities section is essentially a list of duties; we can convert each sentence starting with a verb into
  • . But we must preserve all info; we can keep as

    if not a list? The instruction says use

    • for any list of duties/requirements/benefits. So we should make a list. Similarly Qualifications & Requirements is a list; we can make list. We need to not repeat job title as heading. No Job ID. We must not include boilerplate. We'll produce:

      About the role

      ... position summary ...

      Responsibilities

      • Apply and extend enterprise data governance frameworks to acquired-company integration, covering standards, roles, ownership expectations, stewardship routines, escalation paths, and performance metrics, and adapt them to entity-specific circumstances without departing from firm requirements.
      • Embed governance requirements into data transformation initiatives, including data migration, integration, modernization, archival, reporting, and analytics enablement activities.
      ... etc for each duty. We need to ensure we capture all duties from the text. Let's extract them from the "Essential Duties & Responsibilities:" paragraph. It's a long sentence with many clauses separated by periods? Actually it's a paragraph with many sentences each starting with a verb. Let's split by periods that end a sentence. I'll copy the responsibilities text: "Apply and extend enterprise data governance frameworks to acquired-company integration, covering standards, roles, ownership expectations, stewardship routines, escalation paths, and performance metrics, and adapt them to entity-specific circumstances without departing from firm requirements.Embed governance requirements into data transformation initiatives, including data migration, integration, modernization, archival, reporting, and analytics enablement activities.Establish and maintain a view of the full data estate for each acquisition, spanning structured application data alongside mailboxes, file storage, collaboration sites, chat and meeting content, service management records, and line-of-business repositories.Catalog acquired-company content by category, sensitivity, ownership, business purpose, and disposition, and maintain that inventory as the authoritative reference for integration planning.Advise tenant consolidation, application, infrastructure, service management, and end user technology teams on how each category of content should be handled during migration, including what moves, what is archived, what is left behind, and what must be preserved in place pending further review.Assess unstructured and semi-structured content for regulated, privileged, personal, and client-confidential material, and define handling, access, and protection requirements before that content is moved or made broadly accessible.Drive identification and assignment of accountable data owners for acquired-company data domains before that data is ingested, transformed, or made available for new use, and escalate where ownership cannot be established.Obtain and document owner approval for new or materially changed use of data, and maintain traceable evidence of those approvals.Manage the review and approval path for external sharing and third-party access, including implementation partners and offshore delivery teams, and confirm approvals are in place before access is granted.Identify data entering the environment without established ownership, registration, or approval, including externally sourced datasets and content held outside sanctioned systems, and drive it through review and registration or removal.Classify acquired-company data and content against enterprise retention requirements and category definitions, distinguishing records that must be retained for a defined period from working copies, duplicates, and transient content.Establish retention periods, retention triggers, and disposal timing for acquired-company data and archived datasets, working with accountable owners where no external requirement dictates the period.Coordinate defensible disposal of content that has reached the end of its retention period, including scheduling, approval, evidence capture, and confirmation of confirmation.Confirm legal hold and business hold status before any disposal, decommissioning, or archival action, and suspend routine disposal where a hold is in effect.Coordinate with legal, risk, and service line stakeholders to identify holds applicable to acquired-entity data, communicate those requirements to stewards and delivery teams, and track them through to release.Identify circumstances that extend retention beyond standard periods, including inherited contractual commitments, audit and investigation activity, and content with long-term business or historical value, and manage the documented exception or extension path where requirements cannot be met.Coordinate with service line quality and risk stakeholders to determine which acquired-entity records must be retained to satisfy professional standards for audit, tax, and advisory work, and reflect those determinations in migration and archival plans.Account for jurisdictional differences across the acquisition portfolio, including local privacy, data residency, and statutory retention requirements, and reconcile them against enterprise requirements where they conflict.Drive data quality and standardization by defining data quality rules, profiling approaches, root-cause analysis routines, remediation plans, reconciliation expectations, and quality gates across integration workstreams.Standardize data definitions, formats, critical data elements, metadata, lineage, and ownership expectations across acquired-company sources and enterprise target-state platforms.Maintain catalog and business glossary content for acquired-company data domains so that consumers can determine meaning, context, provenance, and appropriate use without relying on informal knowledge.Support data consumers across the firm by confirming that integrated and archived data meets agreed quality thresholds, and by routing new use cases to the accountable owner for approval.Manage stewardship activities by defining steward responsibilities within integration scope, tracking stewardship actions, supporting training and engagement, and promoting accountability for data assets.Support adoption and effective use of governance technologies such as data catalog, metadata management, lineage, data quality, master data management, and data issue management tools.Work with IT, data platform teams, and vendors to define governance technology requirements, support pilots, contribute to rollout planning, and ensure tools are aligned to data transformation needs.Collaborate with Legal, Privacy, Risk, Compliance, and Security teams to operationalize data protection controls, classification, access controls, masking, retention, and disposal requirements.Monitor and report on governance performance, including data quality scores, policy adherence, stewardship engagement, remediation progress, issue aging, readiness gates, and transformation governance maturity.Produce executive-ready dashboards, status updates, and governance reporting to communicate risks, readiness, compliance, decisions needed, and business value from governance activities.Facilitate cross-functional working sessions to align transformation goals with governance requirements and ensure data decisions are made with clear ownership, traceability, and business accountability.Support source-to-target mapping, lineage, reconciliation, data issue resolution, and integration readiness activities during acquired-company data transformation efforts.Promote a data-driven culture by communicating governance expectations, reinforcing consistent practices, and helping teams understand the value of trusted, compliant, and reusable data.Identify opportunities to improve governance processes, data quality controls, stewardship routines, metadata practices, automation, reporting, and transformation delivery repeatability.Other duties as assigned." We need to split into list items. Each sentence ends with a period. Some sentences have no space after period before next sentence (e.g., "...requirements.Embed"). We'll need to add space. We'll just treat each sentence as separate item. Let's manually split: 1. Apply and extend enterprise data governance frameworks to acquired-company integration, covering standards, roles, ownership expectations, stewardship routines, escalation paths, and performance metrics, and adapt them to entity-specific circumstances without departing from firm requirements. 2. Embed governance requirements into data transformation initiatives, including data migration, integration, modernization, archival, reporting, and analytics enablement activities. 3. Establish and maintain a view of the full data estate for each acquisition, spanning structured application data alongside mailboxes, file storage, collaboration sites, chat and meeting content, service management records, and line-of-business repositories. 4. Catalog acquired-company content by category, sensitivity, ownership, business purpose, and disposition, and maintain that inventory as the authoritative reference for integration planning. 5. Advise tenant consolidation, application, infrastructure, service management, and end user technology teams on how each category of content should be handled during migration, including what moves, what is archived, what is left behind, and what must be preserved in place pending further review. 6. Assess unstructured and semi-structured content for regulated, privileged, personal, and client-confidential material, and define handling, access, and protection requirements before that content is moved or made broadly accessible. 7. Drive identification and assignment of accountable data owners for acquired-company data domains before that data is ingested, transformed, or made available for new use, and escalate where ownership cannot be established. 8. Obtain and document owner approval for new or materially changed use of data, and maintain traceable evidence of those approvals. 9. Manage the review and approval path for external sharing and third-party access, including implementation partners and offshore delivery teams, and confirm approvals are in place before access is granted. 10. Identify data entering the environment without established ownership, registration, or approval, including externally sourced datasets and content held outside sanctioned systems, and drive it through review and registration or removal. 11. Classify acquired-company data and content against enterprise retention requirements and category definitions, distinguishing records that must be retained for a defined period from working copies, duplicates, and transient content. 12. Establish retention periods, retention triggers, and disposal timing for acquired-company data and archived datasets, working with accountable owners where no external requirement dictates the period. 13. Coordinate defensible disposal of content that has reached the end of its retention period, including scheduling, approval, evidence capture, and confirmation of completion. 14. Confirm legal hold and business hold status before any disposal, decommissioning, or archival action, and suspend routine disposal where a hold is in effect. 15. Coordinate with legal, risk, and service line stakeholders to identify holds applicable to acquired-entity data, communicate those requirements to stewards and delivery teams, and track them through to release. 16. Identify circumstances that extend retention beyond standard periods, including inherited contractual commitments, audit and investigation activity, and content with long-term business or historical value, and manage the documented exception or extension path where requirements cannot be met. 17. Coordinate with service line quality and risk stakeholders to determine which acquired-entity records must be retained to satisfy professional standards for audit, tax, and advisory work, and reflect those determinations in migration and archival plans. 18. Account for jurisdictional differences across the acquisition portfolio, including local privacy, data residency, and statutory retention requirements, and reconcile them against enterprise requirements where they conflict. 19. Drive data quality and standardization by defining data quality rules, profiling approaches, root-cause analysis routines, remediation plans, reconciliation expectations, and quality gates across integration workstreams. 20. Standardize data definitions, formats, critical data elements, metadata, lineage, and ownership expectations across acquired-company sources and enterprise target-state platforms. 21. Maintain catalog and business glossary content for acquired-company data domains so that consumers can determine meaning, context, provenance, and appropriate use without relying on informal knowledge. 22. Support data consumers across the firm by confirming that integrated and archived data meets agreed quality thresholds, and by routing new use cases to the accountable owner for approval. 23. Manage stewardship activities by defining steward responsibilities within integration scope, tracking stewardship actions, supporting training and engagement, and promoting accountability for data assets. 24. Support adoption and effective use of governance technologies such as data catalog, metadata management, lineage, data quality, master data management, and data issue management tools. 25. Work with IT, data platform teams, and vendors to define governance technology requirements, support pilots, contribute to rollout planning, and ensure tools are aligned to data transformation needs. 26. Collaborate with Legal, Privacy, Risk, Compliance, and Security teams to operationalize data protection controls, classification, access controls, masking,