Collibra Data Quality SME *6472760

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. Also remove "Accenture Flex offers a market competitive suite of benefits..."? That is benefits info, so keep Benefits section. Also "Compensation at Accenture varies depending on a wide array of factors..." is pay info, but it's vague: "Compensation at Accenture varies depending on a wide array of factors...". The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The compensation statement is vague: "Compensation at Accenture varies depending on a wide array of factors...". That's not a specific range. However later they list a table of hourly salary ranges for many locations: "$44.00 to $54.00". That is specific. So we can include Pay section with that info. Also schedule: "This role requires being onsite 3+ days per week with the client in one of the following locations: Pennington, NJ, or Charlotte NC. Additionally, 5 days of Time Away are mandated per calendar quarter." That's schedule info. So include Schedule section. Now we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe list of preferred qualifications?), Benefits (Accenture Flex benefits), Pay (hourly salary range table), Schedule (onsite 3+ days, 5 days Time Away per quarter). We must not repeat job title as heading. Also we must not include Job ID/requisition numbers. We need to preserve all substantive information. Let's extract content. Original text: "As an SME you will be responsible for acting as a software detective providing a dynamic service by identifying and solving issues within multiple components of critical business systems. You are expected to collaborate and manage the team to perform effectively. You will take responsibility for team decisions, engage with multiple teams and contribute to key decisions. You will provide solutions to problems for your immediate team and across multiple teams is a vital part of this role. Develop a deep understanding of system components to quickly diagnose and resolve complex issues. Support and guide team members by sharing expertise and best practices to enhance overall team performance. Collaborate with cross functional teams to ensure seamless integration and operation of business critical systems. Contribute to continuous improvement initiatives by identifying process enhancements and automation opportunities. Analyze recurring problems and develop proactive strategies to prevent future incidents. This role requires being onsite 3+ days per week with the client in one of the following locations: Pennington, NJ, or Charlotte NC. Additionally, 5 days of Time Away are mandated per calendar quarter." Then "Basic Qualifications Minimum 5 years of experience with Collibra Data Governance Associates Degree or greater" "Preferred Qualifications Advanced proficiency in the following: Microsoft Power Business Intelligence (BI) PostgreSQL Administration Business Operation Management Application Production Support Modern Platform Engineering Op Models Data Quality Python REST API Testing" Then "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. We anticipate this job posting will be posted until 10/18/2026. Accenture Flex offers a market competitive suite of benefits including medical, dental, vision, and long-term disability coverage, a 401(k) plan, and paid time off. See more information on our benefits here: Accenture Flex Jobs Role Location Hourly Salary Range California $44.00 to $54.00 Cleveland $44.00 to $54.00 Colorado $44.00 to $54.00 Columbus $44.00 to $54.00 Connecticut $44.00 to $54.00 District of Columbia $44.00 to $54.00 Illinois $44.00 to $54.00 Maine $44.00 to $54.00 Maryland $44.00 to $54.00 Massachusetts $44.00 to $54.00 Minnesota $44.00 to $54.00 New York $44.00 to $54.00 New Jersey $44.00 to $54.00 Virginia $44.00 to $54.00 Washington $44.00 to $54.00" Then accommodation etc which we drop. We need to preserve all substantive info: The posting until date maybe not needed? It's not a section heading; could be part of About the role? Probably not needed. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting date maybe not essential but it's substantive? It's not a boilerplate; it's info about posting duration. Could be included in About the role as a note? But we have no specific section for posting date. Could include as a paragraph under About the role? Might be okay. However we should not invent sections. We can include a

about the role that includes the description and maybe the posting end date. But we must not add filler. We need to decide sections: - About the role: paragraph summarizing the role (the first paragraph). Could also include the posting end date? Might be considered meta. Safer to include only the role description. - Responsibilities: list of duties from the description: acting as software detective, collaborate and manage team, take responsibility for team decisions, engage with multiple teams, contribute to key decisions, provide solutions to problems for immediate team and across multiple teams, develop deep understanding of system components to quickly diagnose and resolve complex issues, support and guide team members by sharing expertise and best practices, collaborate with cross functional teams to ensure seamless integration and operation of business critical systems, contribute to continuous improvement initiatives by identifying process enhancements and automation opportunities, analyze recurring problems and develop proactive strategies to prevent future incidents. We can put each as

. - Requirements: Basic Qualifications: Minimum 5 years of experience with Collibra Data Governance, Associates Degree or greater. - Qualifications: Preferred Qualifications: list of advanced proficiencies. - Skills: maybe we could combine Preferred Qualifications as Skills? But we already have Qualifications section for Preferred Qualifications. The instruction says use headings for Skills as well. Could we put the list of preferred qualifications under Skills? But we already have Qualifications for Preferred Qualifications. Might be redundant. Better to follow the headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have Basic Qualifications (requirements) and Preferred Qualifications (maybe qualifications). Skills could be the specific technical skills: Microsoft Power BI, PostgreSQL Administration, Business Operation Management, Application Production Support, Modern Platform Engineering Op Models, Data Quality, Python, REST API Testing. Those are skills. So we can put those under Skills. Thus: - About the role: paragraph describing role (first paragraph). - Responsibilities: list of duties (the bullet points derived from the description). - Requirements: Basic Qualifications: Minimum 5 years experience with Collibra Data Governance, Associates Degree or greater. - Qualifications: maybe we could put "Preferred Qualifications" as a heading? But we already have Qualifications heading. Could put the list of preferred qualifications under Qualifications. However we also have Skills heading for the specific technical skills. To avoid duplication, we could put the list of preferred qualifications under Qualifications (as a paragraph) and then under Skills list the specific technical skills. But the preferred qualifications list includes those technical skills; they'd be duplicated. Better to treat Qualifications as the preferred qualifications (the bullet list) and Skills maybe not needed. But we need to follow instruction: use headings for Skills if we have content. If we don't have distinct skills beyond qualifications, we could omit Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section called Qualifications (or Skills). But we need to decide. Given we have both Basic Qualifications and Preferred Qualifications, we could have: - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications (list of advanced proficiencies). - Skills: maybe we could list the same items but that would be thin. Better to omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for Benefits: yes. Pay: we have hourly salary range table. Schedule: onsite 3+ days, 5 days Time Away per quarter. Now we need to format. We must not repeat job title as heading. No Job ID. We must not include boilerplate like "Accenture Flex offers a market competitive suite of benefits including medical, dental, vision, and long-term disability coverage, a 401(k) plan, and paid time off. See more information on our benefits here: Accenture Flex Jobs". That's benefits info; we keep it. We should not include the line "We anticipate this job posting will be posted until 10/18/2026." That's not under any section; maybe we could put it in About the role as a note? But it's not about the role; it's about posting duration. Could be considered meta. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not boilerplate but it's about posting duration. Might be considered not essential to the role. Safer to omit. Now we need to output HTML fragment. Structure:

About the role

As an SME you will be responsible for acting as a software detective providing a dynamic service by identifying and solving issues within multiple components of critical business systems. You are expected to collaborate and manage the team to perform effectively. You will take responsibility for team decisions, engage with multiple teams and contribute to key decisions. You will provide solutions to problems for your immediate team and across multiple teams is a vital part of this role. Develop a deep understanding of system components to quickly diagnose and resolve complex issues. Support and guide team members by sharing expertise and best practices to enhance overall team performance. Collaborate with cross functional teams to ensure seamless integration and operation of business critical systems. Contribute to continuous improvement initiatives by identifying process enhancements and automation opportunities. Analyze recurring problems and develop proactive strategies to prevent future incidents.

Responsibilities

• Act as a software detective to identify and solve issues within multiple components of critical business systems.
• Collaborate and manage the team to perform effectively.
• Take responsibility for team decisions and engage with multiple teams to contribute to key decisions.
• Provide solutions to problems for your immediate team and across multiple teams.
• Develop a deep understanding of system components to quickly diagnose and resolve complex issues.
• Support and guide team members by sharing expertise and best practices to enhance overall team performance.
• Collaborate with cross‑functional teams to ensure seamless integration and operation of business critical systems.
• Contribute to continuous improvement initiatives by identifying process enhancements and automation opportunities.
• Analyze recurring problems and develop proactive strategies to prevent future incidents.

Requirements