Associate, Data Transformation & Governance
for each section heading. Use - for lists. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate. Keep all substantive info.
We need to parse the job description.
Sections:
- About the role / Position Summary: The paragraph after "Associate, Data Transformation & Governance - Position Summary:" up to before "Essential Duties & Responsibilities:" includes description of vision, function, scope, role responsibilities overview. We'll put that in About the role.
- Responsibilities: Essential Duties & Responsibilities list (many bullet-like sentences). We'll turn each sentence into
- .
- Requirements: Qualifications & Requirements section (including bullet list of qualifications). We'll separate maybe into Requirements (including Qualifications & Requirements). Could also separate "Preferred Experience" as part of Requirements? Probably combine.
- Pay: base salary range.
- Possibly "Success Measures" could be a section? Not in allowed headings list; we have only those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Qualifications is similar to Requirements; we can use either. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have content for About the role, Responsibilities, Requirements/Qualifications, Pay. We'll include About the role, Responsibilities, Requirements (or Qualifications), Pay.
We should not create sections with filler. So include only those.
Now format.
We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points from Essential Duties & Responsibilities and Qualifications & Requirements etc.
We must not include boilerplate like "Other duties as assigned." That's substantive? It's a line but maybe considered boilerplate? It's part of duties; we could keep it but it's generic. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other duties as assigned." is not boilerplate but it's a generic phrase; maybe keep? It's not specifically prohibited. I'd keep it as part of responsibilities.
Similarly "Preferred Experience" is part of qualifications.
We need to capture all details.
Let's extract the About the role paragraph:
"Grant Thornton GTech’s vision is centered around enabling scalable, secure, and repeatable data transformation capabilities that support enterprise transformation, mergers and acquisitions, and modern analytics. The Data Transformation & Governance function is responsible for embedding governance, quality, stewardship, compliance, and data standards into transformation initiatives so that data from acquired companies is accurate, secure, compliant, and ready for analytics and business decision-making. Scope extends well beyond structured data. Every acquisition arrives with records held in mailboxes, personal and shared file storage, collaboration sites, chat history, service management platforms, and line-of-business applications, alongside the structured data in HR, finance, and client systems. Much of the firm’s retention and legal exposure sits in that unstructured content rather than in the database tables. This function is expected to see the whole estate, catalog it, determine how each category should be handled, and advise the integration teams accordingly. The Associate, Data Transformation & Governance will help execute governance activities for acquired-company data integration by supporting inventory and classification work, documentation, data quality tracking, stewardship coordination, compliance evidence, and transformation readiness activities. The role works across both structured systems and unstructured content, and partners with data governance leads, data stewards, Data & Analytics, application teams, security and privacy stakeholders, and implementation partners to help ensure data migration, integration, archival, and analytics enablement work is organized, traceable, and aligned with enterprise governance expectations."
We'll put that in
.
Now Responsibilities: list each bullet after "Essential Duties & Responsibilities:" until before "Qualifications & Requirements". Let's copy them:
- 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.
Now Qualifications & Requirements: we need to capture all bullet points.
Let's extract:
- 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.
- Exposure to merger, acquisition, divestiture, or acquired-company technology and data integration initiatives preferred.
- 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.
- 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; relevant data governance, privacy, records management, project management, or data certifications preferred.
Then "Preferred Experience" bullet list:
- 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.
Then "Success Measures" list (maybe could be considered as part of Requirements? But not in allowed headings; we could omit or incorporate into Responsibilities? It's more about performance metrics. Since we have no heading for Success Measures, we could either omit or include as part of Responsibilities? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We don't have a heading for Success Measures in allowed list, so we should not create a heading for it. We could embed those bullet points under Responsibilities or Requirements? They are measures of success, not duties. Might be okay to omit? But we must preserve ALL substantive information. If we omit, we lose info. We could incorporate them under a generic section like "Requirements" but that might be misrepresenting. However the instruction says we can only use those headings; we could put them under "Requirements" as part of qualifications? Not ideal but maybe acceptable. Better to create a section "Requirements" and include both qualifications and success measures? But success measures are not requirements. Could we create a section "Qualifications" and include both qualifications and success measures? The allowed headings include Qualifications. So we could have Qualifications section containing both the qualifications and success measures. That would preserve all info. Let's do that: Use
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. Keep all substantive info. We need to parse the job description. Sections: - About the role / Position Summary: The paragraph after "Associate, Data Transformation & Governance - Position Summary:" up to before "Essential Duties & Responsibilities:" includes description of vision, function, scope, role responsibilities overview. We'll put that in About the role. - Responsibilities: Essential Duties & Responsibilities list (many bullet-like sentences). We'll turn each sentence into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have content for About the role, Responsibilities, Requirements/Qualifications, Pay. We'll include About the role, Responsibilities, Requirements (or Qualifications), Pay. We should not create sections with filler. So include only those. Now format. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points from Essential Duties & Responsibilities and Qualifications & Requirements etc. We must not include boilerplate like "Other duties as assigned." That's substantive? It's a line but maybe considered boilerplate? It's part of duties; we could keep it but it's generic. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other duties as assigned." is not boilerplate but it's a generic phrase; maybe keep? It's not specifically prohibited. I'd keep it as part of responsibilities. Similarly "Preferred Experience" is part of qualifications. We need to capture all details. Let's extract the About the role paragraph: "Grant Thornton GTech’s vision is centered around enabling scalable, secure, and repeatable data transformation capabilities that support enterprise transformation, mergers and acquisitions, and modern analytics. The Data Transformation & Governance function is responsible for embedding governance, quality, stewardship, compliance, and data standards into transformation initiatives so that data from acquired companies is accurate, secure, compliant, and ready for analytics and business decision-making. Scope extends well beyond structured data. Every acquisition arrives with records held in mailboxes, personal and shared file storage, collaboration sites, chat history, service management platforms, and line-of-business applications, alongside the structured data in HR, finance, and client systems. Much of the firm’s retention and legal exposure sits in that unstructured content rather than in the database tables. This function is expected to see the whole estate, catalog it, determine how each category should be handled, and advise the integration teams accordingly. The Associate, Data Transformation & Governance will help execute governance activities for acquired-company data integration by supporting inventory and classification work, documentation, data quality tracking, stewardship coordination, compliance evidence, and transformation readiness activities. The role works across both structured systems and unstructured content, and partners with data governance leads, data stewards, Data & Analytics, application teams, security and privacy stakeholders, and implementation partners to help ensure data migration, integration, archival, and analytics enablement work is organized, traceable, and aligned with enterprise governance expectations." We'll put that in
.
Now Responsibilities: list each bullet after "Essential Duties & Responsibilities:" until before "Qualifications & Requirements". Let's copy them:
- 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.
Now Qualifications & Requirements: we need to capture all bullet points.
Let's extract:
- 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.
- Exposure to merger, acquisition, divestiture, or acquired-company technology and data integration initiatives preferred.
- 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.
- 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; relevant data governance, privacy, records management, project management, or data certifications preferred.
Then "Preferred Experience" bullet list:
- 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.
Then "Success Measures" list (maybe could be considered as part of Requirements? But not in allowed headings; we could omit or incorporate into Responsibilities? It's more about performance metrics. Since we have no heading for Success Measures, we could either omit or include as part of Responsibilities? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We don't have a heading for Success Measures in allowed list, so we should not create a heading for it. We could embed those bullet points under Responsibilities or Requirements? They are measures of success, not duties. Might be okay to omit? But we must preserve ALL substantive information. If we omit, we lose info. We could incorporate them under a generic section like "Requirements" but that might be misrepresenting. However the instruction says we can only use those headings; we could put them under "Requirements" as part of qualifications? Not ideal but maybe acceptable. Better to create a section "Requirements" and include both qualifications and success measures? But success measures are not requirements. Could we create a section "Qualifications" and include both qualifications and success measures? The allowed headings include Qualifications. So we could have Qualifications section containing both the qualifications and success measures. That would preserve all info. Let's do that: Use