Data Product and Integration Analyst

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro about Genworth (company description). Could be "About the role"? Actually "About the role" maybe includes description of role and company? The posting includes "At Genworth, we empower families..." That's company overview. Could be placed under "About the role" or maybe separate "About Genworth". But only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put company overview under About the role. - Position location and schedule: "POSITION LOCATION Richmond, VA This position is available to Virginia residents as Richmond, Virginia in-office applicants A Hybrid schedule of both Remote and In-Office days is required. In office days are Tuesday, Wednesday and Thursday with working hours targeting our core business hours of 9am-5pm EST." This gives schedule info. So we can have a Schedule section. - Pay: "National Range: $84,400 - $127,000 Disclaimer: This role is aligned to a national market-based pay range. Actual compensation will vary based on geographic location, experience, skills, and other job-related factors. In addition to base salary, this role is eligible to participate in a bonus incentive plan. Incentive compensation is based on individual and company performance and is not guaranteed." That's pay info. - Benefits: "Employee Benefits & Well-Being ..." list many benefits. So Benefits section. - Responsibilities: The sections "YOUR ROLE", "What You Will Be Doing" with subcategories: Data Integration & Management, Data Governance & Stewardship, Business Translation & Requirements Management, Analytics & Continuous Improvement, Collaboration & Leadership. Those are responsibilities. - Requirements/Qualifications/Skills: The posting has "What You Bring" with many bullet-like statements: Bachelor's degree..., Minimum of 5 years’ experience..., etc. Also "Nice to Have". Those could be split into Requirements (mandatory) and Qualifications (maybe education) and Skills (technical). But we need to decide which headings to use. We have three possible headings: Requirements, Qualifications, Skills. We need to include only those with real specific content. We can allocate: - Qualifications: Education (Bachelor's degree ... or equivalent work experience). Could also include Master's degree nice to have but that's optional. - Requirements: Minimum years experience (5 years data analysis etc). Also maybe "Minimum of 5 years’ experience with SQL", etc. Those are experience requirements. - Skills: Specific technical skills: Power BI, Python/R, Azure, Git, Excel VBA, Agile, etc. Also "Critical Thinking", "Results Orientation", etc (soft skills). Could be under Skills. We must not create sections with filler like "commensurate with experience". We have actual specifics. We must not repeat job title as heading. So no

Data Product and Integration Analyst

. We must not include Job ID/requisition numbers. We must not include application instructions, cookie/navigation/legal/EEO etc. The posting includes "Additional At this time, Genworth will not sponsor a new applicant for employment authorization for this position." That's maybe a legal note about sponsorship; could be considered boilerplate? It's about work authorization. Might be considered EEO/legal. Probably should remove as it's not substantive about role. Also "Disclaimer: This role is aligned to a national market-based pay range." That's part of Pay section, we can keep as part of Pay description. We need to preserve all substantive information. So we need to include the company overview, role description, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We must use

• for any list of duties/requirements/benefits. So for each bullet list we need to wrap in
  • . For prose we use

    . We must not add extra sections like "About the company". Only allowed headings. Thus we need to decide which content goes under which heading. Let's outline:

    About the role

    At Genworth, we empower families to navigate the aging journey with confidence. We are compassionate, experienced allies for those navigating care with guidance, products, and services that meet families where they are. Further, we are the spouses, children, siblings, friends, and neighbors of those that need care—and we bring those experiences with us to work in serving our millions of policyholders each day. We apply that same compassion and empathy as we work with each other and our local communities. Genworth values all perspectives, characteristics, and experiences so that employees can bring their full, authentic selves to work to help each other and our company succeed. We celebrate our diversity and understand that being intentional about inclusion is the only way to create a sense of belonging for all associates. We also invest in the vitality of our local communities through grants from the Genworth Foundation, event sponsorships, and employee volunteerism. Our four values guide our strategy, our decisions, and our interactions: Make it human. We care about the people that make up our customers, colleagues, and communities. Make it about others. We do what's best for our customers and collaborate to drive progress. Make it happen. We work with intention toward a common purpose and forge ways forward together. Make it better. We create fulfilling purpose-driven careers by learning from the world and each other.

    That seems appropriate.

    Responsibilities

    We need to list duties. The "YOUR ROLE" paragraph plus the "What You Will Be Doing" sections with subheadings. We can combine into a list. We could produce
    • items for each major duty. Let's extract: - Serve as a key connector between business stakeholders, analytics teams, data engineering, and technology partners to strengthen how enterprise data is defined, integrated, governed, and used. - Help create trusted, curated data assets that support customer segmentation, business reporting, analytics, and informed decision-making across critical policy, customer, and risk-related domains. - Translate business needs into clear data requirements, validate data mappings and business rules, document definitions and lineage, and support data quality controls that improve consistency, usability, and trust. - Contribute to continuous improvement by identifying opportunities to enhance data accessibility, streamline data processes, strengthen governance practices, and enable scalable data products for reporting and strategic analytics. Then under Data Integration & Management: - Design and maintain curated datasets that integrate data across multiple systems and domains supporting customer segmentation, and critical business reporting needs. - Partner with data engineering teams to identify, source, and transform data from multiple systems into trusted enterprise data assets. - Validate data mappings, lineage, and business rules to ensure accuracy, consistency, and traceability across data domains. - Support the development and maintenance of data products that enable reporting, analytics, and informed business decision-making. Data Governance & Stewardship: - Apply enterprise data governance principles to strengthen data quality, integrity, consistency, and usability. - Develop and maintain business metadata, data dictionaries, business glossaries, and lineage documentation. - Define and monitor data quality controls, identify issues, and coordinate remediation activities with appropriate stakeholders. - Partner with business and technology stakeholders to establish common definitions and governance standards across data domains. Business Translation & Requirements Management: - Act as a liaison between business stakeholders and technical teams, translating business needs into clear, actionable data requirements. - Analyze business processes to understand how data is generated, consumed, and used across the organization. - Facilitate discussions to align stakeholders on data definitions, requirements, priorities, and expected outcomes. - Partner with reporting and analytics teams to ensure data solutions support business objectives and decision-making needs. Analytics & Continuous Improvement: - Identify opportunities to improve data accessibility, data quality, process efficiency, and governance practices. - Perform exploratory analysis to validate business assumptions and support strategic initiatives. - Recommend enhancements to data models, data flows, and governance processes. - Support enterprise initiatives involving customer segmentation, risk analytics, and operational reporting. Collaboration & Leadership: - Serve as a subject matter resource for data assets within assigned business domains. - Provide guidance to team members and stakeholders on data governance standards and best practices. - Lead small projects or workstreams involving data integration, governance, or process improvement. - Build strong relationships across business, analytics, data engineering, and technology teams. We can combine all these into a single
      with many
      • . That's fine.

        Requirements

        We need to list mandatory requirements: Minimum of 5 years’ experience in data analysis, business analysis, data governance, data stewardship, data modeling, or data engineering in a dynamic environment. Minimum of 5 years’ experience with SQL, including authoring highly complex queries to extract, transform, and analyze large data sets. Minimum of 3 years’ experience using Power BI, with proficiency in semantic models, dataflows, gateways, and publishing to Power BI Server. Minimum of 3 years’ experience with scripting languages, such as Python or R. Minimum of 3 years’ experience supporting data governance, metadata management, or data quality initiatives. Minimum of 3 years’ experience working within Azure or other cloud environments and related data services, including familiarity with data warehouse, data lake, and modern data architecture concepts. Strong understanding of data governance, data quality, metadata management, and data lineage concepts, including familiarity with enterprise data catalog and governance platforms. Experience with Git-based source code management tools and practices. Advanced Microsoft Excel skills, including developing pivot tables, connecting to external data sources, and automating tasks with VBA. Experience with Agile delivery methodologies. Critical Thinking: Strong analytical and problem-solving skills, including the ability to apply quantitative and qualitative insights to support business strategy and effective execution. Results Orientation: Strong sense of urgency and accountability, with a consistent focus on delivering high-quality work within deadlines. Self-Motivation: Ability to manage multiple and changing priorities independently while maintaining a drive for results in a fast-paced environment. Communication: Deliver clear and effective verbal and written communications to both technical and non-technical audiences. Understand, analyze, and document complex business processes. Translate business requirements into practical technical data solutions. Teamwork & Collaboration: Build relationships and collaborate effectively with cross-functional teams, influencing outcomes and contributing as a strong team player. Demonstrate excellent stakeholder management and cross-functional collaboration skills. We could split some into Skills but we have separate Skills heading. However the instructions say we can use Skills heading for list of skills. We could put technical skills under Skills, and soft skills under Requirements? But we need to follow the allowed headings; we can decide. Better: Requirements: mandatory experience and education (maybe). Qualifications: education (Bachelor's degree). Skills: technical and soft skills. But we have a lot of overlapping. Let's think: The posting lumps "What You Bring" includes education, experience, technical skills, soft skills. We could make: - Qualifications: Bachelor's degree in Information Systems, Data Analytics, Computer Science, Business, Statistics, or a related field, or equivalent work experience. (Also maybe Nice to Have Master's degree - but that's optional, we could include under Qualifications as nice to have? But we should not create filler; we can include Nice to Have as part of Qualifications but note it's nice to have. However we should not invent placeholder. It's real content: "Nice to Have Master’s degree in Data Analytics or a related discipline." That's specific, we can include. - Requirements: Minimum of 5 years’ experience in data analysis, business analysis, data governance, data stewardship, data modeling, or data engineering in a dynamic environment. Minimum of 5 years’ experience with SQL, including authoring highly complex queries to extract, transform, and analyze large data sets. Minimum of 3 years’ experience using Power BI, with proficiency in semantic models, dataflows, gateways, and publishing to Power BI Server. Minimum of 3 years’ experience with scripting languages, such as Python or R. Minimum of 3 years’ experience supporting data governance