Data Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "Skanska is searching for a dynamic Data Engineer. This is a great opportunity to start a career with a company that builds things that matter and values its team. We are proud to share our culture of diversity and inclusion. Our work makes a clear contribution to society and the environment around us. We build in many different verticals. Whether we are building schools to provide inspiring spaces for learning, roads to connect communities, or hospitals to care for patients, it all contributes to our purpose – we build for a better society. Skanska's values —Be Better Together, Act Ethically and Transparently, Commit to Customer, and Care for Life—are deeply engrained in how we work, which is why our values support and drive our D&I efforts. We are seeking a talented Data Engineer to design, develop, modernize, and support enterprise data integration, analytics, and reporting solutions across legacy, on-premises, and cloud-based platforms. The ideal candidate will have experience with Microsoft data technologies such as SQL Server, SSIS, and SSRS, together with hands-on exposure to Microsoft Fabric, Azure Data Factory (ADF), Azure Synapse Analytics, Databricks, Spark, Delta Lake, and Lakehouse architectures. This role will partner closely with business stakeholders, analysts, architects, and engineering teams to build scalable data pipelines and trusted data products using ETL/ELT and Medallion Architecture principles. The successful candidate will possess strong SQL and data engineering skills, an understanding of data governance, security, quality, lineage, and observability, and experience working within Agile, Scrum, or Kanban delivery environments. Fabric Data Engineer Associate (DP-700) certification is preferred. The ideal candidate will have a passion for new technologies and a proven track record of contributing to the technical and architectural vision within an enterprise setting." Then "Data Engineer Required Qualifications:" then list bullet points: - 3+ years of experience developing SQL-based data integration, transformation, and reporting solutions. - 3+ years of experience designing, developing, and supporting ETL/ELT pipelines using technologies such as SQL Server Integration Services (SSIS), Azure Data Factory, Azure Functions, Logic Apps, Azure Synapse Analytics, or similar data integration platforms. - 3+ years of experience with data warehouse design, dimensional modeling, or modern analytical data platforms. - 1+ year of experience with Microsoft Fabric or Databricks, including exposure to Lakehouse concepts, Apache Spark, Delta tables, data pipelines, and orchestration. - 1+ year of experience using GitHub, Azure DevOps, or other source control systems. - 6+ months of experience working within Agile, Scrum, or Kanban delivery frameworks. - Bachelor's degree in Computer Science, Data Engineering, Information Systems, or a related field; or equivalent professional experience. - Currently, the company is not considering applicants for this position who now or in the future require employment sponsorship by the company. Then "Our Investment in you: We believe that Benefits should connect you to the support you need when it matters most, and should help you care for those who matter most. That’s why we provide an array of options (including medical, dental, and vision insurance plans), expert guidance, and always-on tools, that are personalized to meet the needs of your reality – to help support you physically, financially, and emotionally through the big milestones and in your everyday life. Please visit the compensation and Benefits summary on our careers site for more details." Then later: "Compensation and financial well-being – Competitive base salary, excellent bonus program, 401k, & Employee ownership program." Also: "Come work with us and join a winning team! Background Check Required" Then EEO etc. We need sections: About the role (intro description), Responsibilities (maybe from description of tasks), Requirements (maybe required qualifications), Qualifications (maybe education/experience?), Skills (maybe technologies), Benefits (benefits description), Pay (compensation), Schedule (maybe not present). We must only include sections if there is real specific content. There's no explicit schedule info, so omit Schedule. We need to avoid repeating job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from posting, but we can organize into sections. We must not include boilerplate like EEO, privacy policy, search firm disclaimer, etc. Also remove duplicated lines. We need to decide what goes where. Let's extract substantive content: About the role: The introductory paragraph describing company, mission, values, and role purpose. Could be: "Skanska is searching for a dynamic Data Engineer... We are seeking a talented Data Engineer to design, develop, modernize, and support enterprise data integration, analytics, and reporting solutions across legacy, on-premises, and cloud-based platforms. The ideal candidate will have experience with Microsoft data technologies such as SQL Server, SSIS, and SSRS, together with hands-on exposure to Microsoft Fabric, Azure Data Factory (ADF), Azure Synapse Analytics, Databricks, Spark, Delta Lake, and Lakehouse architectures. This role will partner closely with business stakeholders, analysts, architects, and engineering teams to build scalable data pipelines and trusted data products using ETL/ELT and Medallion Architecture principles. The successful candidate will possess strong SQL and data engineering skills, an understanding of data governance, security, quality, lineage, and observability, and experience working within Agile, Scrum, or Kanban delivery environments. Fabric Data Engineer Associate (DP-700) certification is preferred. The ideal candidate will have a passion for new technologies and a proven track record of contributing to the technical and architectural vision within an enterprise setting." That seems like responsibilities and qualifications mixed. But we can separate. Responsibilities: design, develop, modernize, support enterprise data integration, analytics, reporting solutions; partner with stakeholders; build scalable data pipelines and trusted data products using ETL/ELT and Medallion Architecture; work with business stakeholders, analysts, architects, engineering teams. Requirements: maybe the list of required qualifications (the bullet list). Qualifications: maybe education and experience? But we can combine. Skills: technologies: SQL Server, SSIS, SSRS, Microsoft Fabric, Azure Data Factory, Azure Synapse Analytics, Databricks, Spark, Delta Lake, Lakehouse, ETL/ELT, Medallion Architecture, data governance, security, quality, lineage, observability, Agile/Scrum/Kanban, GitHub, Azure DevOps, source control. Benefits: medical, dental, vision insurance plans; expert guidance; always-on tools; support physically, financially, emotionally; compensation and benefits summary link; competitive base salary, excellent bonus program, 401k, Employee ownership program. Pay: competitive base salary, excellent bonus program, 401k, Employee ownership program (maybe also mention bonus). Could be separate. But we must not create Pay section unless posting actually states them. It does: "Compensation and financial well-being – Competitive base salary, excellent bonus program, 401k, & Employee ownership program." So we can include Pay. Benefits: medical, dental, vision insurance plans; expert guidance; always-on tools; support physically, financially, emotionally. We need to avoid duplication: The compensation line appears also in Benefits? We'll separate. We must not include "Background Check Required" maybe as a note but it's substantive; could be placed in a short p under maybe Requirements? But it's not a heading; we can include as a paragraph under maybe Requirements or a separate note. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Background Check Required is minor metadata; we can fold into a short p. We must remove EEO etc. Now produce HTML. Structure:

  About the role

  ... (intro paragraph)

  Responsibilities

  • Design, develop, modernize, and support enterprise data integration, analytics, and reporting solutions across legacy, on-premises, and cloud‑based platforms.
  • Partner closely with business stakeholders, analysts, architects, and engineering teams to build scalable data pipelines and trusted data products using ETL/ELT and Medallion Architecture principles.

  Requirements

  • 3+ years of experience developing SQL‑based data integration, transformation, and reporting solutions.
  • 3+ years of experience designing, developing, and supporting ETL/ELT pipelines using technologies such as SQL Server Integration Services (SSIS), Azure Data Factory, Azure Functions, Logic Apps, Azure Synapse Analytics, or similar data integration platforms.
  • 3+ years of experience with data warehouse design, dimensional modeling, or modern analytical data platforms.
  • 1+ year of experience with Microsoft Fabric or Databricks, including exposure to Lakehouse concepts, Apache Spark, Delta tables, data pipelines, and orchestration.
  • 1+ year of experience using GitHub, Azure DevOps, or other source control systems.
  • 6+ months of experience working within Agile, Scrum, or Kanban delivery frameworks.
  • Bachelor's degree in Computer Science, Data Engineering, Information Systems, or a related field; or equivalent professional experience.
  • Currently, the company is not considering applicants for this position who now or in the future require employment sponsorship by the company.

  Skills

  • SQL Server, SSIS, SSRS
  • Microsoft Fabric, Azure Data Factory (ADF), Azure Synapse Analytics, Databricks, Spark, Delta Lake, Lakehouse architectures
  • ETL/ELT and Medallion Architecture principles
  • Data governance, security, quality, lineage, observability
  • Agile, Scrum, Kanban delivery environments
  • GitHub, Azure DevOps, source control
  • Fabric Data Engineer Associate (DP‑700) certification (preferred)

  Benefits

  • Medical, dental, and vision insurance plans
  • Expert guidance and always‑on tools personalized to support physical, financial, and emotional well‑being
  • Access to compensation and benefits summary on the careers site for more details

  Pay

  Competitive base salary, excellent bonus program, 401(k), and employee ownership program.

  Optionally add a short p for Background Check Required: maybe under Requirements or separate note. Could add a

  Background check required.

  after Pay or within Requirements as a minor metadata. The instruction says fold minor metadata into a short

  or drop it. So we can add a

  Background check required.

  after Pay. We must not include any other boilerplate. Now output only HTML fragment. Check that we didn't repeat job title. Good. Check that we didn't include any heading with empty content. All sections have content. Check that we didn't include Pay/Schedule/Benefits unless stated. Benefits and Pay are stated. Schedule not present, omitted. Check that we preserved all substantive info: Did we miss any? Let's review original text for any other substantive details not captured: - "We are proud to share our culture of diversity and inclusion." Included in About the role? We didn't explicitly mention diversity and inclusion. We could add a sentence in About the role: "We are proud to share our culture of diversity and