Sr. Data Engineer

We need to output HTML fragment with sections: About the role (maybe from intro), Responsibilities, Requirements (Minimum Education and/or Experience Required + Preferred Experience + Systems & Technology Requirements?), maybe Skills? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need to decide which sections to include. We have content: Intro paragraph describing role, could be "About the role". Then "Responsibilities Include" list. Then "Minimum Education and/or Experience Required" (qualifications). Then "Preferred Experience:" list. Then "Systems & Technology Requirements" list. Then "Travel" (no overnight travel). Then "Compensation" with salary range. Then "Sponsorship" (visa). Then benefits link. Then EEO boilerplate (remove). Also "This is a full-time remote position, in a positive and flexible environment. Residency within 100 miles of the Kansas City, Missouri office is required." That could be part of About the role or maybe a separate "Schedule"? Not schedule. Could be part of About the role. We should not include sections like Benefits unless actual benefits described; only mention "Visit our Benefits page for more information." That's not specific benefits, so we should not create Benefits section. Pay section: we have compensation range, so include Pay. Schedule: not mentioned besides full-time remote; but we could include Schedule? The posting says "This is a full-time remote position". That's schedule info (full-time). Could include Schedule section with that detail. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state full-time remote, so we can include Schedule. But we need to avoid filler like "not specified". We have specifics: full-time remote, residency within 100 miles of Kansas City. So we can include Schedule. We should not repeat job title as heading. No Job ID. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Interested in learning more about the amazing benefits the NAIC offers? Visit our Benefits page for more information." That's basically a benefits link but not specific benefits; we should not create Benefits section. So we can drop that sentence. Also remove "The NAIC is proud to be an Equal Opportunity Employer ..." entirely. Now structure:

About the role

... intro paragraph(s) ... maybe combine intro and remote/residency.

Responsibilities

• ... each responsibility line ...

Requirements

Maybe combine Minimum Education/Experience and Preferred Experience and Systems & Technology Requirements? Could split into Qualifications and Skills. But instruction: prefer few substantive sections over many thin ones. Could have Requirements covering education/experience, preferred experience, and tech requirements. Or we could have Qualifications and Skills separate. Let's see: We have Minimum Education and/or Experience Required (education + years). Preferred Experience (financial/insurance etc). Systems & Technology Requirements (list of tools). Could combine into Requirements section with sublists? But we need to use

• for any list of duties/requirements/benefits. So we can have multiple
  inside the section. We could do:

  Requirements

  Minimum Education and/or Experience:

  ...

  Preferred Experience:

  ...

  Systems & Technology Requirements:

  ...
  That seems okay. Then

  Pay

  with salary range. Then

  Schedule

  with full-time remote and residency requirement. We should not include Benefits. Now ensure we preserve all substantive information. Let's extract details. Intro: "The Information Technology Group of the National Association of Insurance Commissioners (NAIC) has an exciting opportunity for a Senior Data Engineer. This position provides senior-level technical expertise across data architecture, data modeling, pipeline development, data integration, data quality, and platform optimization. Partners closely with data architects, data engineers, data stewards, business owners, project managers, and other stakeholders across the Enterprise Data Team, Information Technology Group (ITG), and business units to translate complex business and technical requirements into effective data solutions. The Senior Data Engineer is expected to lead complex data engineering efforts, establish and promote engineering standards, mentor other team members, and contribute to continuous improvement across the EDP. Through strong technical judgment and cross-functional collaboration, this role helps ensure enterprise data is accessible, trusted, secure, performant, and effectively leveraged to support NAIC's strategic objectives. This is a full-time remote position, in a positive and flexible environment. Residency within 100 miles of the Kansas City, Missouri office is required." We'll put that in About the role paragraph. Responsibilities list: each line after "Responsibilities Include". Let's capture: - Design, develop, and maintain scalable enterprise data solutions, including data architecture, models, pipelines, structures, and supporting processes within the Enterprise Data Platform (EDP). - Analyze complex data sources and business requirements in partnership with stakeholders to deliver secure, reliable, and efficient data solutions. - Develop, optimize, and support data pipelines that ingest, transform, integrate, and deliver trusted data aligned with business needs. - Implement data quality, governance, and operational processes to ensure enterprise data assets are accurate, consistent, secure, and well-managed. - Provide technical guidance, troubleshooting, and escalation support for teams using or impacting data within the EDP, including root cause analysis and sustainable issue resolution. - Review and modernize data models, pipelines, and legacy processes to improve scalability, reliability, automation, maintainability, and alignment with enterprise architecture standards. - Contribute to continuous improvement and platform strategy by evaluating emerging technologies, enhancing engineering practices, and identifying opportunities to expand enterprise data capabilities. Minimum Education and/or Experience Required: - Bachelor's degree in computer science, data analytics, data science, mathematics, statistics, information Systems, or another related analytical or technical field and 5 or more years of related data engineering experience; or an equivalent combination of education and work experience. - Experience designing, developing, and supporting enterprise data platforms, including data ingestion, transformation, modeling, integration, quality, and operational support. - Advanced experience with SQL, relational databases, ETL/ELT development, data modeling, and cloud-based data technologies. - Experience leading complex technical efforts, making data architecture or design recommendations, and mentoring other technical team members. - Experience with the software development life cycle, Agile delivery practices, and SAFe values and methods. Preferred Experience: - Experience with financial, insurance, regulatory, or market data. Systems & Technology Requirements: List each bullet: - Microsoft Office Suite/365 - Amazon Web Services (AWS) - Data pipeline orchestration and automation - Extract, Transform and Load (ETL/ELT) - CI/CD and DevOps practices - Git or source control platforms - Infrastructure as Code concepts, such as Terraform - RDBMS (Oracle, PostgreSQL) - NoSQL (MongoDB / DynamoDB) - Snowflake - Python - Structured Query Language (SQL) (duplicate of SQL? but keep) - MacOS - Data File Formats (JSON, Parquet, XML (likely XBRL in near future)) - Data modeling and dimensional modeling - Data warehouse and data Lakehouse concepts - Secrets management concepts, such as Vault or similar tools - Cloud security and IAM concepts - Data governance, lineage, metadata, and cataloging concepts - Performance tuning and query optimization - Data quality testing and data observability Travel: "This position does not require overnight business travel. Employees are responsible for their personal transportation to/from the home and office, including events, meetings, and training required by the NAIC." This could be part of Schedule or maybe a note. We'll include in Schedule maybe. Compensation: "$107,000 - $123,000, commensurate with education and experience." Sponsorship: "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is substantive; maybe include in a section like "Work Authorization" but not in given headings. Could fold into Requirements or a short p. Since we only have prescribed headings, we could put it in a

  under Requirements or maybe under About the role? Better to add a short paragraph after Requirements: maybe a

  about work authorization. But instruction: Use headings only for those sections; we can still have

  without heading. So we can add a

  after Requirements for sponsorship. We must not include EEO boilerplate. Now produce HTML fragment. Let's craft.

  About the role

  The Information Technology Group of the National Association of Insurance Commissioners (NAIC) has an exciting opportunity for a Senior Data Engineer. This position provides senior-level technical expertise across data architecture, data modeling, pipeline development, data integration, data quality, and platform optimization. Partners closely with data architects, data engineers, data stewards, business owners, project managers, and other stakeholders across the Enterprise Data Team, Information Technology Group (ITG), and business units to translate complex business and technical requirements into effective data solutions. The Senior Data Engineer is expected to lead complex data engineering efforts, establish and promote engineering standards, mentor other team members, and contribute to continuous improvement across the EDP. Through strong technical judgment and cross-functional collaboration, this role helps ensure enterprise data is accessible, trusted, secure, performant, and effectively leveraged to support NAIC's strategic objectives. This is a full-time remote position, in a positive and flexible environment. Residency within 100 miles of the Kansas City, Missouri office is required.

  Responsibilities

  • Design, develop, and maintain scalable enterprise data solutions, including data architecture, models, pipelines, structures, and supporting processes within the Enterprise Data Platform (EDP).
  • Analyze complex data sources and business requirements in partnership with stakeholders to deliver secure, reliable, and efficient data solutions.
  • Develop, optimize, and support data pipelines that ingest, transform, integrate, and deliver trusted data aligned with business needs.
  • Implement data quality, governance, and operational processes to ensure enterprise data assets are accurate, consistent, secure, and well-managed.
  • Provide technical guidance, troubleshooting, and escalation support for teams using or impacting data within the EDP, including root cause analysis and sustainable issue resolution.
  • Review and modernize data models, pipelines, and legacy processes to improve scalability, reliability, automation, maintainability, and alignment with enterprise architecture standards.
  • Contribute to continuous improvement and platform strategy by evaluating emerging technologies, enhancing engineering practices, and identifying opportunities to expand enterprise data capabilities.

  Requirements

  Minimum Education and/or Experience:

  • Bachelor's degree in computer science, data analytics, data science, mathematics, statistics, information Systems, or another related analytical or technical field and 5 or more years of related data engineering experience; or an equivalent combination of education and work experience.
  • Experience designing, developing, and supporting enterprise data platforms, including data ingestion, transformation, modeling, integration, quality, and operational support.
  • Advanced experience with SQL, relational databases, ETL/ELT development, data modeling, and cloud-based data technologies.
  • Experience leading complex technical efforts, making data architecture or design recommendations, and mentoring other technical team members.
  • Experience with the software development life cycle, Agile delivery practices, and SAFe values and methods.

  Preferred Experience:

  • Experience with financial, insurance, regulatory, or market data.