Data Governance Specialist

We need to output HTML fragment with sections: About the role? The posting includes "Job Summary" and then duties, requirements, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes: Job Summary (could be About the role). Duties & Responsibilities (Responsibilities). Minimum Requirements & Qualifications (Requirements/Qualifications). Preferred Experience & Skills (Skills). Job Conditions (maybe not a standard heading; but we could treat as Requirements? It's more about eligibility; but we have no specific heading for Job Conditions; we could omit or incorporate into Requirements? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have: - About the role: could be the Job Summary paragraph(s). We'll put that under

About the role

with

. - Responsibilities: Duties & Responsibilities section. - Requirements: Minimum Requirements & Qualifications (maybe combine with Qualifications). Could split: Requirements (minimum) and Qualifications (preferred?). But we have both Minimum Requirements & Qualifications and Preferred Experience & Skills. We could treat Minimum Requirements & Qualifications as Requirements, and Preferred Experience & Skills as Skills. Or we could have Requirements and Qualifications both. The instruction says use those headings as examples; we can include both Requirements and Qualifications if we have distinct content. Let's do:

Requirements

for Minimum Requirements & Qualifications (the bullet list of education/experience). Use

• .

  Qualifications

  maybe for Preferred Experience & Skills? But Qualifications often similar to Requirements. However we have Preferred Experience & Skills separate; we could treat that as Skills. The instruction includes Skills heading. So we can do:

  Skills

  for Preferred Experience & Skills. We also have Job Conditions (eligibility, etc.) maybe not needed; but could be part of Requirements? Might be considered as Requirements but it's more about eligibility. Could we create a section like "Eligibility"? Not in list. Probably we should omit Job Conditions as it's boilerplate? It contains many eligibility statements; but they are substantive (age, commute, CORI, etc.). However they are somewhat generic but still specific to MBTA. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Job Conditions includes many eligibility requirements that are not exactly boilerplate but could be considered part of the job posting. However they are not in the list of headings we should use; we could incorporate them into Requirements or maybe a separate section like "Requirements" already includes education/experience; we could add another

  Requirements

  but we already used that for education/experience. Could we have two sections with same heading? Probably not ideal. Better to incorporate those eligibility points into Requirements as additional list items. Thus Requirements section will include both education/experience and eligibility conditions (age, commute, CORI, etc.). We'll list them as bullet points. We must not repeat job title as heading. No Pay/Benefits/Schedule sections because not provided. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reformat into HTML. We need to be careful not to include boilerplate like EEO, etc. The Job Conditions includes EEO etc. We should remove those lines. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO, anti-discrimination, etc. Also remove "Ability to uphold the rights and interests of the MBTA while building and maintaining effective relationships with employees and co-workers." That might be okay? It's not EEO but still generic. Might be considered boilerplate? Safer to remove generic statements that are not specific to the role. However we need to preserve substantive information; many of those are generic eligibility but still part of job conditions. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. It doesn't say remove all generic eligibility statements. But many lines like "Ability to effectively read, comprehend, communicate, and respond to instructions..." is generic but could be considered part of job conditions. Might keep. We'll need to parse the Job Conditions paragraph and keep relevant points, removing any that are clearly EEO or legal boilerplate. Let's extract Job Conditions text: "Ability to effectively read, comprehend, communicate, and respond to instructions, orders, signs, notices, inquiries, etc. in English. Be at least eighteen (18) years of age, except if participating in an approved high school internship / co-op program. Ability to commute to assigned work locations in the Boston, MA metro area, as required by the role. Ability to provide internal and external customers with courteous and professional experiences. Ability to work effectively, independently, and as part of a diverse workforce team (or supervise, if required). Ability to uphold the rights and interests of the MBTA while building and maintaining effective relationships with employees and co-workers. Ability to adhere to rules, regulations, collective bargaining agreements (if applicable), and policies of the MBTA, including the EEO, anti-discrimination, anti-harassment, and anti-retaliation policies. Have a satisfactory work record for the two (2) years immediately prior to the closing date of this posting (unless if current student or recent graduate), including overall employment, job performance, discipline, and safety records (infractions and/or offenses occurring after the closing of the posting and before the filling of a vacancy may preclude a candidate from consideration for selection). Ability to pass a Criminal Offender Record Information (CORI) check, comprehensive background screening, and / or medical Clinic screening, potentially including physical examination and drug and alcohol screenings. Ability to work all shifts and / or locations assigned, directed, or necessary for this position, including (for some transit / operations roles) up to twenty-four (24) hours per day, seven (7) days per week as necessary to accommodate severe weather conditions, emergencies, or any other circumstances that may potentially impact service or the safety of service. Intern / co-op staff must be enrolled full or part-time in an accredited educational program and maintain a cumulative GPA of at least 2.5 for the entire duration of the internship / co-op. Additionally, interns / co-ops must have valid work authorization and U.S. Social Security Number prior to starting pre-employment screenings / pre-boarding, working in their positions, and throughout the duration of their program." We need to remove EEO line: "Ability to adhere to rules, regulations, collective bargaining agreements (if applicable), and policies of the MBTA, including the EEO, anti-discrimination, anti-harassment, and anti-retaliation policies." That's EEO boilerplate; remove. Also maybe remove "Ability to uphold the rights and interests of the MBTA while building and maintaining effective relationships with employees and co-workers." Not EEO but could be considered generic; but it's not explicitly listed to remove. Keep? It's somewhat generic but still part of job conditions. I'd keep. Also remove any duplicated lines; none. Now we need to format all content. Let's extract sections: Job Summary (About the role): "The Data Governance Specialist supports the MBTA’s Data Resource Group by coordinating enterprise-wide data cataloging, master data management, data quality, and data governance initiatives. This role manages the contextual data infrastructure needed to deliver accurate, trusted, and accessible data, overseeing cataloged data assets and scalable processes that improve data ingestion and usability across the organization. Working within the Informatica Intelligent Data Management Cloud (IDMC), the Specialist helps design, implement, and maintain governance policies, standards, and frameworks that ensure data quality, integrity, and security. The position collaborates with data stewards, architects, and analytics teams to drive consistent data definitions, lineage, and catalog adoption, and monitors compliance, identifies improvement opportunities, and provides guidance on data-related issues to enable timely, data-driven decision-making across the MBTA." We'll put that in

  . Duties & Responsibilities: list items. We need to capture each bullet under Duties & Responsibilities. The text includes several headings within duties: "Data Catalog and Metadata Management:", "Data Governance and Stewardship Enablement:", "Data Quality Management:", "Master Data Management:", "Collaboration and Evangelism:" plus a final line "Perform all other duties and projects that may be assigned. Additional responsibilities may include focus on one or more departments or locations. See applicable addendum for department or location specific functions." We'll turn each bullet into

• . We'll need to preserve the content exactly as given, but we can break into separate
• for each major duty. The original uses colon headings and then sentences. We'll keep them as is inside
• . Let's list: - Configure and maintain the Data Catalog to automate metadata harvesting and data lineage tracking. - Increase adoption of governed and cataloged data assets by business users. - Collaborate with business units to define and manage metadata standards. - Ensure data assets are well-documented, searchable, and accessible for analytics and business users. - Support Cloud Data Governance and Catalog (CDGC) to operationalize governance frameworks. - Coordinate with data owners and stewards to ensure role clarity, stewardship workflows, and data certification processes. - Monitor governance KPIs and create dashboards/reports on governance adoption. - Develop measurable data quality metrics across key departments. - Define, customize and configure Informatica Data Quality rules and institute consistent monitoring processes. - Partner with business data owners and stewards to define data quality dimensions, thresholds, and remediation workflows. - Provide insights and alerts for inconsistent data, data anomalies and integrity issues. - Assist in configuring and maintaining Informatica MDM for key divisions and departments (Operations, Administration, Safety and Capital data assets). - Create a single, reliable "master" record for core business entities. - Reduce duplication and inconsistencies through effective MDM practices. - Ensure MDM integration with downstream operational systems, BI systems and analytics, - Act as the bridge between Technology, Analytics teams, and business data owners and stewards to promote trusted data usage. - Provide training and guidance to data owners, stewards, and analysts on leveraging Informatica tools. - Champion adoption of data governance, metadata, and quality practices across the MBTA. - Perform all other duties and projects that may be assigned. - Additional responsibilities may include focus on one or more departments or locations. - See applicable addendum for department or location specific functions. Note: The line "Ensure MDM integration with downstream operational systems, BI systems and analytics," ends with a comma; we keep as is. Now Requirements: Minimum Requirements & Qualifications text: "Bachelor's degree from an accredited institution in Computer Science, Information Management, Business Analytics, or related field. Two (2) years of experience with Informatica Data Catalog, Data Quality, Data Governance, Metadata Management, Master Data Management (MDM), and Data Marketplace. Two (2) years of experience in data governance, data management, or a related field. Strong understanding of metadata management, data quality, governance, and master data concepts. Experience working with data stewards, data owners, and cross-functional teams to operationalize governance frameworks. Familiarity with relational databases, cloud data platforms (AWS, Azure, or Snowflake), and API integration. Excellent communication and facilitation skills, with the ability to translate technical capabilities into business value. Analytical and problem-solving skills to identify and resolve data governance issues. Knowledge of data management technologies and tools. Substitutions A high school diploma or GED with an additional seven (7) years of directly related experience substitutes for the bachelor’s degree requirement. An associate’s degree from an accredited institution and an additional three (3) years of directly related experience substitutes for the bachelor’s degree requirement. A master’s degree in