AWS Data Governance Engineer

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

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a paragraph about NTT DATA strives to hire... but that's generic. The role description: "We are currently seeking a AWS Data Governance Engineer...". Could treat as About the role. Responsibilities: there is a "Key Responsibilities" section with sub-bullets. Requirements: there is "Required Skills & Experience". Qualifications: there is "Preferred Qualifications". Skills: maybe combine with Required? But we can have Skills section separate if content. Benefits: there is mention of company benefits. Pay: there is hourly range. Schedule: not mentioned (remote role but no schedule). So we should not include Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, accessibility, etc. Also remove application instructions. Also remove duplicated lines. We need to preserve all substantive information. So we need to include details: location Nashville, Tennessee (US-TN), United States (US). Role: AWS Data Governance Engineer. Description: partner with stakeholders etc. Responsibilities list: we need to capture bullet points. The responsibilities are described in paragraphs with headings: AWS Data Governance & Metadata Management, AWS Platform & Governance Support, Data Catalog & Governance Enablement, Stakeholder Collaboration, Platform Integration & Support. We need to turn those into

• items. Probably each bullet is a sentence. We'll extract each distinct duty. Let's parse responsibilities: Under "AWS Data Governance & Metadata Management": - Support enterprise metadata management, cataloging, lineage, classification, and stewardship initiatives across AWS-based data platforms. - Enable metadata capture, tagging, catalog publication, and governance workflows that improve discoverability, trust, and compliance of enterprise data assets. - Assist with data subject area mapping, metadata enrichment, data classification, and governance enablement activities. - Support business glossary, stewardship, certification, and governance processes. - Partner with governance stakeholders to identify opportunities to improve metadata quality, lineage visibility, and governance adoption. Under "AWS Platform & Governance Support": - Support data governance capabilities across AWS cloud environments. - Partner with cloud engineering teams to integrate governance controls, metadata management, cataloging, and lineage capabilities into AWS-based solutions. - Support AWS security requirements related to data governance, metadata management, and compliance initiatives. - Assist with governance standards, access management, classification controls, and cloud governance best practices. Under "Data Catalog & Governance Enablement": - Support enterprise data catalog capabilities including asset onboarding, classification, lineage, certification, and discoverability. - Assist with governance workflow implementation and operationalization. - Guide users on how to Client, understand, and trust enterprise data assets. (Probably a typo: "Guide users on how to Client, understand, and trust enterprise data assets." We'll keep as is.) - Develop and expand expertise supporting Collibra capabilities and governance platform adoption. - Partner with governance teams to mature enterprise data management and governance capabilities. Under "Stakeholder Collaboration": - Work closely with governance leads, data stewards, business stakeholders, architects, and engineering teams to gather governance requirements and enable governance solutions. - Translate business requirements into metadata, cataloging, lineage, classification, and governance capabilities. - Communicate governance concepts effectively to both technical and non-technical audiences. - Facilitate discussions and drive governance-related decisions across multiple stakeholder groups. Under "Platform Integration & Support": - Support integration of governance capabilities with AWS services, cloud data platforms, metadata repositories, APIs, and reporting solutions. - Assist with operational support, platform enhancements, governance automation, and continuous improvement initiatives. - Partner with architecture and platform teams to improve metadata management and governance effectiveness. - Support onboarding and adoption of governance capabilities across the enterprise. Now Required Skills & Experience: list items: - Experience: 7+ years of experience in data governance, metadata management, cloud platforms, data engineering, or related disciplines. - 3+ years of hands-on experience working within AWS environments. - 3+ years of experience supporting enterprise data governance, metadata management, data cataloging, or governance enablement initiatives. - AWS & Cloud Platforms: Strong experience working with AWS cloud services and cloud-based data platforms. - Understanding of AWS security concepts, governance controls, and access management. - Experience supporting cloud-based data assets and cloud database platforms. - Experience implementing or supporting governance capabilities within cloud environments. - Data Governance & Metadata Management: Experience with: - Metadata capture and tagging - Data catalog publication and search - Data lineage management - Data classification and governance - Data stewardship concepts - Business glossary management - Data subject area mapping - Metadata enrichment and governance processes - Data Platform & Engineering Concepts: - Understanding of cloud data platforms and enterprise data pipelines. - Experience supporting metadata integration across multiple systems and platforms. - Working knowledge of data management concepts and governance best practices. - Familiarity with SQL and data-related technologies. - Professional Skills: - Strong communication, presentation, and stakeholder management skills. - Ability to explain technical concepts to non-technical audiences. - Ability to operate independently and drive outcomes with limited supervision. - Comfortable working in ambiguous and evolving environments. - Strong organizational, analytical, and problem-solving abilities. - Demonstrated adaptability and willingness to learn new technologies and platforms. Preferred Qualifications: - Experience with Collibra administration, implementation, configuration, or support. - Experience with Alation or similar data catalog and governance platforms. - Experience supporting metadata management, governance workflows, lineage, and governance automation initiatives. - Experience with Python for automation, scripting, or metadata-related solutions. - Experience with SQL and cloud-based data platforms. - Experience working with container technologies such as Docker or Kubernetes. - Experience supporting financial services, risk, compliance, HR, procurement, legal, or enterprise business domains. Pay: Starting hourly range ($70.00-$75.55/hour). Also mention incentive compensation, benefits. Benefits: Company benefits may include medical, dental, and vision insurance, flexible spending or health savings account, life, and AD&D insurance, short-and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally required benefits. Also mention AWS certifications highly desirable (maybe under Preferred? but we can add a note under Skills or Preferred). We'll include as a bullet under Preferred Qualifications or maybe under Skills. Since it's not in Required or Preferred, but mentioned after benefits. We'll add a separate bullet under Preferred Qualifications? Actually it's after benefits: "AWS certifications are highly desirable." We'll include as a bullet under Preferred Qualifications. Also location: Nashville, Tennessee (US-TN), United States (US). We'll include in About the role paragraph. Now we need to output HTML fragment with sections:

  About the role

  ...

  etc. We must not include empty sections. We'll include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Skills with Requirements? But we have separate sections for Required Skills & Experience (Requirements) and Preferred Qualifications (Qualifications). Skills could be under Requirements? But we have a Skills section; we could put professional skills there. However the instruction: Prefer a few substantive sections over many thin ones. We could merge Skills into Requirements or Qualifications. But we have distinct content: Required Skills & Experience includes both experience and skills. Professional Skills is a subsection. Qualifications is Preferred Qualifications. To avoid many thin sections, we could have: About the role, Responsibilities, Requirements (includes required experience and skills), Qualifications (preferred), Benefits, Pay. That's 5 sections. That seems good. Thus we will not have a separate Skills section; we will incorporate professional skills into Requirements. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. We'll need to escape any HTML special characters? Not needed. Let's craft. About the role paragraph: Include NTT DATA strives to hire..., we are seeking AWS Data Governance Engineer in Nashville, Tennessee (US-TN), United States (US). Also mention the role description: partner with governance stakeholders etc. Could summarize but must preserve all substantive information; we can't summarize away detail. However we can keep the description as is but we need to avoid duplication with responsibilities. The About the role can be a short paragraph summarizing the role but not repeating responsibilities details. However we must preserve ALL substantive information; we cannot omit details. If we summarize, we might lose detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all details, not summarize. That means we need to include the full description from the posting, not just a summary. However we can break it into sections: About the role could include the introductory sentences about NTT DATA and the role location and maybe the first sentence about seeking AWS Data Governance Engineer. Then responsibilities section will contain the detailed responsibilities. That way we keep all info: the introductory sentences are preserved in About the role; responsibilities are preserved in Responsibilities section; required experience in Requirements; preferred qualifications in Qualifications; benefits and pay in their sections. Thus we need to extract the introductory sentences before "Key Responsibilities". Let's locate: "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a AWS Data Governance Engineer to join our team in Nashville, Tennessee (US-TN), United States (US). NTT DATA is seeking an AWS-focused Data Governance Engineer to support enterprise data governance initiatives within a large-scale cloud environment. This role will partner with governance stakeholders, cloud engineering teams, data stewards, architects, and platform teams to operationalize metadata management, data cataloging, lineage, classification, stewardship, and governance processes across AWS-based data platforms. The ideal candidate brings strong AWS and cloud platform experience, understands enterprise data governance concepts, and has the ability to develop expertise in Collibra and related governance tools over time." That's the introductory paragraph before Key Responsibilities. We'll put that in About the role. Now Responsibilities: we will list all bullet points from the Key Responsibilities subsections as
  • . We'll need to ensure we don't lose any. We'll combine all bullet points into a single list? Could be multiple
    under same heading but it's okay. We'll just output one
    with all items. Now Requirements: we need to include Required Skills & Experience content. We'll break into
    with items. Might be long but okay. We need to capture each bullet point as separate
    • . For sub-bullets (like under AWS & Cloud Platforms), we can still make each as separate
    • . We'll flatten. Similarly for Qualifications: Preferred Qualifications list. Benefits: we need to include the benefits description. It's a sentence: "Company benefits may include medical, dental, and vision insurance, flexible spending or health savings account, life, and AD&D insurance, short-and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally required benefits". Also mention that position may be eligible for incentive compensation based on individual and/or company performance. Also mention that this position is eligible for company benefits that will depend on the nature of the role offered. We'll include all. Pay: Starting hourly range ($70.00-$75.55/hour). Also mention that this range reflects min and max target compensation across US locations. Actual compensation depends on factors. Also mention incentive compensation eligibility. We'll include. Now ensure we don't include boilerplate: EEO, legal, accessibility, etc. Also remove duplicated lines. Now produce HTML. Let's craft. We'll need to ensure proper nesting:

      About the role