Governance Data Analyst (E6088)
IEEE · Piscataway, NJ · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections only if real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting:
Job Summary: we can treat as About the role? Probably "About the role" heading with summary paragraph.
Responsibilities: there is "Key Responsibilities" then bullet list items (though they are not bullet but lines). We need to extract responsibilities.
Requirements & Documentation etc. Actually there is a section "Key Responsibilities Requirements & Documentation:" then many bullet-like lines. We need to separate responsibilities and requirements.
We have "Education" line: Bachelor's degree or equivalent experience... Advanced degrees a plus. ReqMaster's or other advanced degree Pref
Work Experience lines: many "Req4-7 years ..." etc.
Skills And Requirements: list of functional abilities etc.
Other Requirements: includes IEEE policy note, immigration note, ADA reference, Category I, EEO statement (should be removed as boilerplate). Also disclaimer etc.
Travel Information: 5% Domestic
Schedule: Full-time
Job Type: Regular
Job Posting date etc.
We need to include Pay? Not present. Benefits? Not present. So we should not include Pay or Benefits sections.
Schedule: we have "Schedule Full-time". So we can include Schedule section with that.
We also have Travel Information maybe could be part of Schedule? But not required. Could include under Schedule? Probably better to include Travel under Schedule? But rule: include Schedule section only if posting actually states them. It does state Schedule Full-time. Travel Information maybe could be under Schedule? Not exactly. Could add a separate section? Not in allowed headings list. So we could incorporate travel info into Schedule section as a paragraph.
We must not include boilerplate like EEO, disclaimer, legal, etc. Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract:
About the role (Job Summary): The Data Governance Analyst plays a critical role in advancing enterprise data governance by partnering with business stakeholders, technology teams, and the data governance organization. This role requires exceptional communication and stakeholder-management skills, with the ability to translate complex data concepts into clear, actionable guidance. The analyst will work cross-functionally with IT Teams to guide governance best practices, define data quality and metadata requirements, and convert business needs into technical deliverables. In addition to driving functional requirements, this role is responsible for executing technical development work—building, configuring, and deploying data governance solutions across the data catalog, metadata, and other data quality platforms. The analyst will own the end-to-end delivery of governance capabilities, ensuring product integrity, enabling scalable processes, and championing data governance across diverse teams.
Responsibilities: list items from "Key Responsibilities Requirements & Documentation:" but we need to separate responsibilities vs requirements. The text after that heading seems to mix responsibilities and requirements. Let's parse:
"Key Responsibilities Requirements & Documentation: Collaborate with business stakeholders to gather, define, validate, and document data requirements and specifications.Strategy & Planning: Contribute to functional governance planning by aligning catalog structure, metadata standards, business glossaries, and quality rule frameworks to enterprise objectives.Product Quality Assurance: Maintain and govern metadata assets, business glossary content, and quality rules to ensure accuracy, consistency, compliance, and ongoing reliability.Product Quality Assurance: Conduct proactive monitoring and assurance of data integrity across the data catalog and quality rule configurations.Execution & Delivery: Implement and enforce data quality rules in Atlan, and use Soda to support continuous quality monitoring.Execution & Delivery: Support metadata integration and operational delivery in partnership with engineering, architecture, and data product functions.Stakeholder Engagement & Lead: Facilitate frequent cross-functional collaboration with Data Engineering, Data Architecture, and data product teams to promote governance alignment.Stakeholder Engagement & Lead: Actively promote data governance best practices, standards, and catalog adoption within business units and enterprise forums.Stakeholder Engagement & Lead: Serve as the designated Data Governance Subject Matter Expert (DG SME) in enterprise working sessions, representing business-unit needs and governance best practices.Consult and Lead: Provide consultative expertise and facilitation when guiding business stakeholders through data governance workflows and decisions.Leverage AI technology to evaluate and optimise governance processes."
These appear to be responsibilities (maybe also some requirements). We'll treat as responsibilities.
Requirements: Education, Work Experience, Skills And Requirements (functional abilities), Other Requirements (some like IEEE policy, immigration, ADA, Category I). But we need to filter out boilerplate: EEO statement, disclaimer, legal, immigration note? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The immigration note about not budgeted for employer-sponsored immigration support is likely legal/boilerplate? It's a specific requirement about immigration support; might be considered substantive? It's about visa sponsorship. Might be considered a requirement? The instruction says remove legal boilerplate. Immigration note could be considered legal. Safer to remove? But it's a specific condition: "PLEASE NOTE: This position is not budgeted for employer-sponsored immigration support, this includes all persons in F (both CPT and OPT), J, H, L, or O status." That's a condition; could be considered substantive. However it's legal/immigration. I'd lean to remove as boilerplate? The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal about immigration. So remove.
Other Requirements: "As defined in IEEE Policies, individuals currently serving on an IEEE board or committee are not eligible to apply." That's also a requirement/eligibility; could be considered substantive. Not exactly boilerplate. Keep? It's a policy restriction. Might be considered substantive. Keep.
"For information on work demands and conditions required for this position, please consult the reference document, ADA Requirements." That's a reference; could be considered boilerplate? It's pointing to ADA. Might be considered legal. Remove? It's a directive to consult doc; not substantive. Probably remove.
"This position is classified under Category I - Office Positions." That's substantive classification. Keep.
"All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or status as a protected veteran." That's EEO boilerplate; remove.
Disclaimer etc remove.
Travel Information: "5% Domestic". Keep.
Education: "Bachelor's degree or equivalent experience In Computer Science, Data Science, Informaton Technology, Business Management, or related technical field. Advanced degrees a plus. ReqMaster's or other advanced degree Pref". Need to clean typos: "Informaton". Keep as is? Probably preserve original text but we can fix obvious typo? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Fixing typo could be considered altering. Better to keep as is? It's a typo in source; we could keep exactly. But we could keep as is; it's still substantive. We'll keep as is.
Work Experience: many lines each prefixed with "Req4-7 years" etc. We need to extract the requirements.
Let's list them:
- Proven communicator with a strong ability to coordinate and drive follow-through across data governance teams and business stakeholders using multiple communication channels. (Req4-7 years)
- Demonstrated autonomy and self-motivation, with experience managing a largely independent workload and maintaining accountability without direct oversight. (Req4-7 years)
- Hands‑on experience using SQL, Python, or other programming languages for data analysis and validation. (Req)
- Analyst experience working daily with business stakeholders, leading requirements-driven working sessions, and translating business needs into structured technical specifications, user stories, and governance workflows within Jira. (Req4-7 years)
- Hands-on data governance experience supporting data cataloging, master data management (MDM), metadata governance, or data quality monitoring and remediation. (Req2-4 years)
- Practical understanding of data privacy, regulatory compliance, data policy frameworks, or industry data protection standards. (Pref2-4 years)
- Experience supporting the development, configuration, or management of data privacy policies, compliance requirements, or governance controls within data policy or catalog platforms. (Pref2-4 years)
- Prior experience contributing to data privacy tooling or policy governance in platforms such as Atlan. (Pref2-4 years)
Also there is "Req Master's or other advanced degree Pref" under Education.
Skills And Requirements: list of functional abilities etc. We'll capture as Skills section.
Let's extract Skills And Requirements bullet points (they are sentences separated by periods). The text:
"Functional AbilitiesStrong stakeholder management and interpersonal skills, with a talent for aligning diverse perspectives around a common vision.Ability to translate complex technical details into elegant, user‑centric solutions.Leverage AI technology to evaluate and optimise governance processes.Set accurate timelines for project work and communicate status updates, and risks.Strong documentation, writing, and presentation skills.Initiate and DeliverInfluential skills to educate the business on data governance efforts and requirements.Excellent teamwork and ability to guide the project team to a shared common goal and deliverables.Analytical SkillsStrong analytical aptitude and problem‑solving capabilities.Strong in user story definition, and dependencies for data-adjacent teams.Familiarity with highly technical data and analytics concepts including modern data architecture (cloud data warehouses, ETL/ELT, BI platforms, Machine-learning frameworks and workflows).Performs root cause analysis and understand the complex issue, then recommends a scalable solution.Decisions are grounded in Data Governance Best Practices, for scalability across the enterprise."
We need to split into list items. Could group by sentences. We'll create