Data Strategy & Governance Consultant
Accenture · Albany, New York Metropolitan Area · 1 mo ago
Business Development$70k–$206k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description about Accenture, AI and Data practice, etc. We need to reformat into semantic HTML using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse the posting.
First paragraph: "We Are Accenture is a leading global professional services company..." This is company overview. Could be part of "About the role"? Usually "About the role" includes description of role and team. But we have description of Accenture and AI and Data practice. Could treat as "About the role" or maybe "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Intro about Accenture and AI and Data practice: could be "About the role" (context). Might also be "About the team". We'll put under
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse the posting.
First paragraph: "We Are Accenture is a leading global professional services company..." This is company overview. Could be part of "About the role"? Usually "About the role" includes description of role and team. But we have description of Accenture and AI and Data practice. Could treat as "About the role" or maybe "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Intro about Accenture and AI and Data practice: could be "About the role" (context). Might also be "About the team". We'll put under About the role
with paragraphs.
- Then "You Are You are a Data Strategy & Governance Consultant who executes the design and operationalization of enterprise data governance frameworks..." This is role description. Could also be part of About the role or Responsibilities. Probably "About the role" includes role summary. We'll include that.
- Then "The Work" bullet list: Execute data governance design..., Operationalize governance models..., Support governance structures..., Configure governance tooling..., Support compliance alignment..., Travel may be required... This is responsibilities. So we will put under Responsibilities
with - items.
- Then "Here’s What You Need" list of minimum experience etc. That's requirements/qualifications. We need to decide split between Requirements and Qualifications and Skills. The instruction: Use headings for Requirements, Qualifications, Skills. We need to allocate content.
We have:
Minimum of 3 years of experience in a data management, data governance, or a data strategy role (in a AWS, Microsoft, Google, etc. environment)
Minimum of 2 years of hands-on experience operationalizing data governance frameworks (stewardship, ownership, data quality, metadata management)
Minimum of 2 years of hands-on experience with data cataloging or lineage tooling (e.g., Databricks, Snowflake, Collibra, Alation, Microsoft Purview)
Minimum of 2 years of experience working within or supporting regulatory and privacy compliance requirements
Bachelor's degree or equivalent (minimum 12 years' work experience). If Associate’s Degree, must have equivalent minimum 6-year work experience
These are requirements/qualifications. Could treat as Requirements.
Then "Bonus Points If You" list: utilities experience, semantic layers, Master's degree, exposure to MDM and stakeholder management, relevant certifications. These could be Skills or Qualifications (preferred). We'll put under
Skills
maybe.
But we also have "Compensation at Accenture varies..." and then benefits and salary ranges per location. That's Pay and Benefits sections.
We have "Benefits Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". So we need Benefits section.
Pay: we have compensation varies and then salary ranges per location. That is specific pay info. So we should include Pay section with the salary ranges.
Schedule: we have "Travel may be required for this role, varying from 0 to 80% depending on business need and client requirements." That's about travel, not schedule. No explicit schedule (full-time, part-time). So we should not create Schedule section because no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. So we include Pay and Benefits, but not Schedule.
Now we need to ensure we don't include boilerplate like EEO, accommodation request, etc. Remove those sections.
Also remove duplicated lines, navigation, cookie, legal, etc. The posting includes many accommodation, EEO statements, etc. We must drop them.
Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", "Other Employment Statements", etc.
Also remove "Visit us at accenture.com." maybe keep as part of About the role? It's not essential but could be considered boilerplate? It's a link to company site. Might be considered navigation? Probably safe to keep as part of company overview but it's not substantive about role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link to accenture.com is not substantive about role; it's just a generic link. Could be considered boilerplate. Safer to remove.
Also remove "We anticipate this job posting will be posted until 08/25/2026." That's metadata; maybe drop as not substantive? It's about posting duration. Could be considered not essential. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. This is minor metadata; we could drop it or put in a short p. Probably drop.
Now compile HTML.
Structure:
About the role
... (company overview and role summary)
Responsibilities
- Execute data governance design — support the design and operationalization of governance frameworks covering data ownership, stewardship, data quality standards, metadata management, and policy enforcement.
- Operationalize governance models — work with business and technology stakeholders to turn data strategy into actionable governance operating models that enable trusted data for analytics and AI.
- Support governance structures — help establish governance councils, define data classification and access policies, and document standards and processes.
- Configure governance tooling — implement and drive adoption of cataloging, lineage, and data quality tooling (e.g., Databricks, Snowflake, Collibra, Alation, Microsoft Purview).
- Support compliance alignment — ensure governance work aligns with regulatory and privacy requirements and contributes to master data management efforts.
- Travel may be required for this role, varying from 0 to 80% depending on business need and client requirements.
Requirements
- Minimum of 3 years of experience in a data management, data governance, or a data strategy role (in a AWS, Microsoft, Google, etc. environment)
- Minimum of 2 years of hands-on experience operationalizing data governance frameworks (stewardship, ownership, data quality, metadata management)
- Minimum of 2 years of hands-on experience with data cataloging or lineage tooling (e.g., Databricks, Snowflake, Collibra, Alation, Microsoft Purview)
- Minimum of 2 years of experience working within or supporting regulatory and privacy compliance requirements
- Bachelor's degree or equivalent (minimum 12 years' work experience). If Associate’s Degree, must have equivalent minimum 6-year work experience
Skills
- Minimum of 1 year of experience serving utilities clients (electric, gas, or water) or in a utilities finance, controllership, or regulatory function (bonus)
- Experience with building semantic layers (bonus)
- Master’s degree in a relevant field (bonus)
- Exposure to master data management and stakeholder management (bonus)
- Relevant data governance or data platform certifications (bonus)
But we need to indicate these are bonus points; we could keep as is.
Now Pay section:
Pay
Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below.
- California: $70,350 to $205,800
- Cleveland: $59,100 to $164,600
- Colorado: $63,800 to $177,800
- District of Columbia: $68,000 to $189,300
- Illinois: $59,100 to $177,800
- Maine: $54,400 to $151,400
- Maryland: $63,800 to $177,800
- Massachusetts: $63,800 to $189,300
- Minnesota: $63,800 to $177,800
- New York: $66,300 to $205,800
- New Jersey: $68,000 to $205,800
- Virginia: $59,100 to $189,300
- Washington: $80,200 to $189,300
We could also list other cities but they are duplicates of states? The list includes many cities after the salary ranges. Actually after the salary ranges list, there is a long list of cities: Philadelphia, PA Albany, NY Arlington, VA Atlanta, GA Austin, TX Beaverton, OR Bentonville, AR Boston, MA Carmel, IN Charlotte, NC Chicago, IL Cincinnati, OH Cleveland, OH Columbus, OH Culver City, CA Denver, CO Detroit, MI Hartford, CT Houston, TX Irving, TX Kirkland, WA Miami, FL Milwaukee, WI Minneapolis, MN Morristown, NJ Mountain View, CA Nashville, TN New York City, NY Oklahoma City, OK Overland Park, KS Pittsburgh, PA Raleigh, NC Sacramento, CA San Diego, CA San Francisco, CA Scottsdale, AZ Seattle, WA St. Louis, MO St. Petersburg, FL Walnut Creek, CA
These appear to be locations where the role may be hired, but no salary ranges given for each city; they are just locations. The instruction: include Pay section only when posting actually states them. It does state salary ranges for certain states, and also lists many cities. Should we include the city list? It's location info, not pay. Could be part of About the role or maybe a separate "Location" section but we only have allowed headings. Could fold into About the role as a short paragraph: "Role may be located in various cities including ..." but we must not invent headings. We could add a under About the role mentioning locations. However the instruction: Prefer a few substantive sections over many thin ones. So we could add location info to About the role.
Thus About the role paragraph will include company overview, role description, and note that the role may be located in many cities (list). But we must preserve all substantive information; we shouldn't drop the city list. So we include them.
Now Benefits section:
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more
Skills
maybe. But we also have "Compensation at Accenture varies..." and then benefits and salary ranges per location. That's Pay and Benefits sections. We have "Benefits Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". So we need Benefits section. Pay: we have compensation varies and then salary ranges per location. That is specific pay info. So we should include Pay section with the salary ranges. Schedule: we have "Travel may be required for this role, varying from 0 to 80% depending on business need and client requirements." That's about travel, not schedule. No explicit schedule (full-time, part-time). So we should not create Schedule section because no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. So we include Pay and Benefits, but not Schedule. Now we need to ensure we don't include boilerplate like EEO, accommodation request, etc. Remove those sections. Also remove duplicated lines, navigation, cookie, legal, etc. The posting includes many accommodation, EEO statements, etc. We must drop them. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", "Other Employment Statements", etc. Also remove "Visit us at accenture.com." maybe keep as part of About the role? It's not essential but could be considered boilerplate? It's a link to company site. Might be considered navigation? Probably safe to keep as part of company overview but it's not substantive about role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link to accenture.com is not substantive about role; it's just a generic link. Could be considered boilerplate. Safer to remove. Also remove "We anticipate this job posting will be posted until 08/25/2026." That's metadata; maybe drop as not substantive? It's about posting duration. Could be considered not essential. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. This is minor metadata; we could drop it or put in a short p. Probably drop. Now compile HTML. Structure:
About the role
... (company overview and role summary)
Responsibilities
- Execute data governance design — support the design and operationalization of governance frameworks covering data ownership, stewardship, data quality standards, metadata management, and policy enforcement.
- Operationalize governance models — work with business and technology stakeholders to turn data strategy into actionable governance operating models that enable trusted data for analytics and AI.
- Support governance structures — help establish governance councils, define data classification and access policies, and document standards and processes.
- Configure governance tooling — implement and drive adoption of cataloging, lineage, and data quality tooling (e.g., Databricks, Snowflake, Collibra, Alation, Microsoft Purview).
- Support compliance alignment — ensure governance work aligns with regulatory and privacy requirements and contributes to master data management efforts.
- Travel may be required for this role, varying from 0 to 80% depending on business need and client requirements.
Requirements
- Minimum of 3 years of experience in a data management, data governance, or a data strategy role (in a AWS, Microsoft, Google, etc. environment)
- Minimum of 2 years of hands-on experience operationalizing data governance frameworks (stewardship, ownership, data quality, metadata management)
- Minimum of 2 years of hands-on experience with data cataloging or lineage tooling (e.g., Databricks, Snowflake, Collibra, Alation, Microsoft Purview)
- Minimum of 2 years of experience working within or supporting regulatory and privacy compliance requirements
- Bachelor's degree or equivalent (minimum 12 years' work experience). If Associate’s Degree, must have equivalent minimum 6-year work experience
Skills
- Minimum of 1 year of experience serving utilities clients (electric, gas, or water) or in a utilities finance, controllership, or regulatory function (bonus)
- Experience with building semantic layers (bonus)
- Master’s degree in a relevant field (bonus)
- Exposure to master data management and stakeholder management (bonus)
- Relevant data governance or data platform certifications (bonus)
Pay
Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below.
- California: $70,350 to $205,800
- Cleveland: $59,100 to $164,600
- Colorado: $63,800 to $177,800
- District of Columbia: $68,000 to $189,300
- Illinois: $59,100 to $177,800
- Maine: $54,400 to $151,400
- Maryland: $63,800 to $177,800
- Massachusetts: $63,800 to $189,300
- Minnesota: $63,800 to $177,800
- New York: $66,300 to $205,800
- New Jersey: $68,000 to $205,800
- Virginia: $59,100 to $189,300
- Washington: $80,200 to $189,300
under About the role mentioning locations. However the instruction: Prefer a few substantive sections over many thin ones. So we could add location info to About the role. Thus About the role paragraph will include company overview, role description, and note that the role may be located in many cities (list). But we must preserve all substantive information; we shouldn't drop the city list. So we include them. Now Benefits section:
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more