Data Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Skills, Benefits, Pay, Schedule. But we must only include sections that have real specific content. The posting includes About the Role, Key Responsibilities, Required Qualifications, Preferred Qualifications, Skills & Competencies, Education & Experience, Work Arrangement & Schedule, Compensation & Benefits, Compliance / Additional Information (which we must remove as boilerplate). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. - About the role: we have content. Include

About the role

with paragraph(s). - Responsibilities: we have Key Responsibilities list. Include

Responsibilities

with

• items. - Requirements: we have Required Qualifications. Could also include Preferred Qualifications under Qualifications? The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (maybe required) and Qualifications (maybe preferred). Or combine required and preferred under Qualifications? But we have both Required Qualifications and Preferred Qualifications. We could put Required Qualifications under Requirements heading, and Preferred Qualifications under Qualifications heading. That seems appropriate. - Skills: we have Skills & Competencies list. Include

  Skills

  with list. - Benefits: The posting says "Compensation and specific employee benefits are not provided in the original job description." Then they list some highlights (growth-focused culture, etc.) but those are not benefits per se. The instruction: never create Benefits section unless posting actually states them. It does not give specific benefits like health insurance, etc. It mentions "Delta Defense highlights: * A growth-focused company culture.* Opportunities to contribute to meaningful business and organizational initiatives.* A company recognized on the Inc. 5000 list for 15 consecutive years.* A mission-focused work environment.* Professional growth and development opportunities." Those are more like company highlights, not explicit benefits. The instruction says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The benefits section would be not specified; we should not include Benefits section. - Pay: Not specified; do not include Pay. - Schedule: Work Arrangement & Schedule includes location, hybrid flexibility, goal to work onsite. That is specific content. So we can include Schedule section with that info. The heading Schedule is allowed. We'll include location and work arrangement details. We must not repeat job title as heading. Not include Job ID/requisition numbers. Remove boilerplate like EEO, compliance, etc. We need to preserve all substantive information. So we need to include all details from About the Role, Responsibilities, Required Qualifications, Preferred Qualifications, Skills & Competencies, Education & Experience (maybe we can fold into Requirements/Qualifications?), Work Arrangement & Schedule. Education & Experience section duplicates some of Required/Preferred qualifications; we should not duplicate content. We need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit Education & Experience we might lose some info like "High school diploma or equivalent is required." That's already in Required Qualifications. Also "Associate or Bachelor's degree ... is preferred." That's in Preferred Qualifications. "Equivalent relevant experience may be considered." That's also in Required Qualifications? Not exactly; but we can incorporate that into Required Qualifications maybe. However we have Required Qualifications already includes high school diploma, 2-5 years experience, 3-5 years SQL, 1 year Agile, ETL/ELT, analytical modeling, risk policies, core values, no sponsorship. It does not mention "Associate or Bachelor's degree ... preferred" nor "equivalent relevant experience may be considered." Those are in Preferred Qualifications and Education & Experience. So we need to keep those. Thus we need to include Education & Experience content somewhere. Could we put it under Qualifications? Possibly combine Education & Experience into Qualifications section (both required and preferred). But we already have Requirements (required) and Qualifications (preferred). We could move the education details into those sections. Let's extract: Required Qualifications bullet list: - High school diploma or equivalent. - 2–5 years of experience in data engineering or business intelligence roles. - 3–5 years of SQL experience. - At least 1 year of experience with Agile Software Development Life Cycle (SDLC). - Solid understanding of ETL/ELT methodologies. - Solid understanding of industry-standard analytical modeling techniques. - Ability to work in accordance with organizational risk policies and data-related standards. - Demonstrated alignment with the Core Values of Delta Defense, LLC. - Must be able to work without current or future employer sponsorship, as Delta Defense does not provide sponsorship for this role. Preferred Qualifications: - Associate or Bachelor's degree in Computer Science, Information Management, Data Science/Analytics, Statistics, or equivalent relevant experience. - Experience working with AWS cloud technologies, including S3 and EMR. - 1+ year of dbt experience. - Proficiency with Python and scripting languages. Education & Experience: Education: * High school diploma or equivalent is required. * Associate or Bachelor's degree in Computer Science, Information Management, Data Science/Analytics, Statistics, or a related field is preferred. * Equivalent relevant experience may be considered. Experience: * 2–5 years of experience in data engineering or business intelligence. * 3–5 years of SQL experience. * 1+ year of Agile SDLC experience. * 1+ year of dbt experience is preferred. Thus Education & Experience repeats some of the required/preferred. To avoid duplication, we could keep Requirements and Qualifications as given, and not include Education & Experience separately (since its content is covered). However we must preserve ALL substantive information; if we omit Education & Experience heading but its content is already present elsewhere, we are not losing info. That's acceptable because we are not summarizing away detail; we are just not duplicating. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we keep the info elsewhere, it's preserved. So we can omit Education & Experience section. Now Skills & Competencies list: many items, some overlap with Required/Preferred but we should keep as Skills section. Now Work Arrangement & Schedule: includes Job Location, Work Arrangement, Employment Type (Not specified), Schedule (Not specified), Sponsorship (already covered). We need to keep location and work arrangement details. Employment Type and Schedule are not specified; we should not include them as they are filler/placeholder? The instruction: never emit a heading followed by filler/placeholder text. If we include Schedule heading but content is "Not specified", that's filler. So we should not include Schedule section if the only content is not specified. However we have location and work arrangement specifics. We could make a section called "Schedule" but include location and work arrangement? That seems mismatched. Better to create a section maybe "Work Arrangement" but allowed headings are limited. We could put location and work arrangement under Schedule heading? Not ideal. Perhaps we can include a paragraph under Schedule heading with location and work arrangement details, and omit the unspecified parts. The heading Schedule is allowed; we can put location and work arrangement there. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Schedule is a permissible heading. We can put location and work arrangement details there. We must not include filler like "Employment Type: Not specified" or "Schedule: Not specified". So we will omit those lines. Thus Schedule section will contain: - Job Location: Delta Defense headquarters, West Bend, Wisconsin. - Work Arrangement: Hybrid flexibility is available; however, the goal is for this person to work onsite. - Sponsorship: Delta Defense does not currently or in the future provide sponsorship for this role. (But sponsorship is already mentioned in Required Qualifications; we could keep it there; but we could also mention here. To avoid duplication, maybe we keep sponsorship only in Required Qualifications. However we already have that bullet. We'll keep it there and not repeat. Thus Schedule section will have location and work arrangement. Now Benefits: we determined not to include. Pay: not include. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  Delta Defense is seeking a Data Engineer to help transform complex data into reliable, actionable insights that support business decisions. This hands-on role focuses on building clean, tested, and reusable datasets, supporting the Enterprise Data Warehouse, and improving access to KPIs, metrics, and reporting across the organization. The Data Engineer will work with data infrastructure, transformation standards, data quality, cloud technologies, and data modeling while partnering with the Data Architecture team. The role is based at the Delta Defense headquarters in West Bend, Wisconsin, with some hybrid flexibility, although the goal is for the position to be primarily onsite.

  Responsibilities

  • Work within systems and infrastructure that collect and process data to create clean, tested, and reusable datasets for analysis.
  • Contribute to established data transformation standards and ensure compliance with data format and attribute requirements.
  • Support data quality standards by maintaining and enhancing data profiling methodologies.
  • Apply engineering best practices for CI/CD, unit testing, performance testing, and optimization.
  • Partner with the Data Architecture team to maintain data model quality and consistency.
  • Leverage existing data infrastructure to fulfill data-related requests.
  • Perform data housekeeping, cleansing, normalization, hashing, and required data model changes.
  • Analyze data to identify anomalies, trends, and correlations across similar datasets.
  • Troubleshoot data and engineering problems, identify potential solutions, and resolve issues.
  • Maintain awareness of best practices related to Personally Identifiable Information (PII).
  • Follow organizational risk policies and standards related to data management.
  • Perform other duties as assigned.

  Requirements

  • High school diploma or equivalent.
  • 2–5 years of experience in data engineering or business intelligence roles.
  • 3–5 years of SQL experience.
  • At least 1 year of experience with Agile Software Development Life Cycle (SDLC).
  • Solid understanding of ETL/ELT methodologies.
  • Solid understanding of industry-standard analytical modeling techniques.
  • Ability to work in accordance with organizational risk policies and data-related standards.
  • Demonstrated alignment with the Core Values of Delta Defense, LLC.
  • Must be able to work without current or future employer sponsorship, as Delta Defense does not provide sponsorship for this role.

  Qualifications

  • Associate or Bachelor's degree in Computer Science, Information Management, Data Science/Analytics, Statistics, or equivalent relevant experience.
  • Experience working with AWS cloud technologies, including S3 and EMR.
  • 1+ year of dbt experience.
  • Proficiency with Python and scripting languages.

  Skills

  • Data engineering
  • Business intelligence
  • SQL
  • ETL/ELT
  • Data transformation
  • Data cleansing and normalization
  • Data profiling and data quality
  • Data modeling
  • Analytical modeling
  • Python and scripting
  • AWS cloud technologies
  • Amazon S3
  • Amazon EMR
  • db