Data Engineering Manager

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Remove boilerplate etc. We need to parse the posting. Sections: - About the role: The initial paragraph describing the role: "Lead the engineering, integration, and architecture behind our enterprise data ecosystem. Hastings Insurance is seeking a Data Engineering Manager to join our Information Technology team. In this leadership role, you will lead the team responsible for the engineering and operation of the data platforms, pipelines, integrations, and architecture that form the foundation of Hastings' enterprise data environment. You will oversee the movement, transformation, integration, storage, and availability of data across the organization, ensuring that enterprise data is reliable, scalable, secure, and accessible to the systems and teams that depend on it. This includes responsibility for data engineering, data warehousing, enterprise integration, data modeling, and the continued modernization of our data environment. This is an IT-focused data engineering leadership role rather than a business intelligence or analytics position. You'll partner closely with our Business Intelligence team and other technology and business stakeholders, while your team's primary focus remains the engineering, infrastructure, integration, and operational foundation that enables reporting, analytics, and business use of enterprise data." We can put that as

About the role

then

...

. - Responsibilities: The "What You'll Do" bullet list. The posting includes a list of responsibilities after "What You'll Do". It's a series of sentences separated by periods, but we can treat as list items. Should we use

• . Yes. List items: - Lead, coach, and develop a team responsible for enterprise data engineering, data warehousing, integration, and platform operations. - Provide technical leadership and direction for the design, development, deployment, and support of enterprise data pipelines and data platforms. - Guide the architecture and continued modernization of Hastings' enterprise data environment, balancing current operational needs with long-term scalability and maintainability. - Ensure reliable ingestion, movement, transformation, integration, and delivery of data across enterprise systems and downstream data consumers. - Establish and promote engineering practices that improve data quality, consistency, lineage, governance, security, and reliability. - Guide data modeling, warehousing, integration, and architectural practices that support scalable and reusable enterprise data solutions. - Partner closely with Business Intelligence, IT engineering and architecture teams, product owners, and other stakeholders to translate data needs into sustainable technical solutions. - Oversee production support and operational health of enterprise data solutions, including performance, reliability, troubleshooting, root cause analysis, and continuous improvement. - Evaluate emerging technologies and recommend solutions that improve scalability, automation, performance, reliability, and cost effectiveness. - Develop and manage maintenance schedules for enterprise data platforms and related systems. - Support vendor evaluations, contract discussions, and third-party data service relationships. - Stay informed on emerging data engineering practices and technology trends, including developments within the Property & Casualty insurance industry. Also "Additional Role Highlights" maybe part of responsibilities? Could be separate but we can include as responsibilities as well. The "Additional Role Highlights" includes bullet-like sentences: - Lead the team responsible for the technical foundation of Hastings' enterprise data ecosystem. - Help shape the modernization and future direction of enterprise data engineering and architecture at Hastings. - Work across both established and evolving technologies as Hastings continues to modernize its data environment. - Partner closely with IT engineering, architecture, Business Intelligence, and organizational leadership. - Balance people leadership, technical direction, platform strategy, and operational responsibility. - Influence how enterprise data is engineered, integrated, governed, and made available throughout the organization. We could merge them into responsibilities list. - Requirements: The "What You'll Bring" bullet list. Items: - Bachelor's degree in Information Technology, Computer Science, Engineering, Business, or a related field, or equivalent professional experience. - 10+ years of progressive experience in data engineering, enterprise data platforms, data warehousing, systems integration, or related disciplines. - Experience leading, mentoring, or providing technical direction to data engineering or other technical professionals. - Strong experience designing, developing, and supporting enterprise ETL/ELT pipelines and data integration solutions. - Strong understanding of data warehousing, data modeling, enterprise integration, and data architecture principles. - Experience with the following: - Working with relational databases and large-scale enterprise data environments. - Supporting production data platforms, including troubleshooting, performance optimization, reliability, and continuous improvement. - Working across legacy and modern data environments and contributing to modernization or migration initiatives. - Understanding of data governance, data quality, lineage, security, and related enterprise data management practices. - Strong communication and collaboration skills with the ability to work effectively across technical and nontechnical teams. - Ability to provide technical direction while balancing business priorities, operational needs, and long-term architectural considerations. We need to format as list items; sublist maybe but we can flatten. - Preferred Qualifications: The "Preferred Qualifications" bullet list: - Experience with(in) the following: - Property & Casualty insurance industry or another complex, data-intensive industry. - Modern cloud data platforms and cloud-based data engineering architectures. - SQL Server and modern ETL/ELT, orchestration, data modeling, or enterprise integration technologies. - Automation, CI/CD, or DevOps practices supporting data engineering environments. - Supporting enterprise data warehouses and downstream business intelligence environments. We can treat as list items. - Benefits: The posting mentions benefits in "About Hastings Insurance" paragraph: "We offer competitive pay and benefits, including a 401(k) with company matching contributions, generous paid time off, tuition and professional development assistance, and company performance-based incentive compensation opportunities." Also earlier: "Our Organizational Commitment" etc. So we have benefits: 401(k) with company matching, generous paid time off, tuition and professional development assistance, company performance-based incentive compensation opportunities. Also maybe "competitive pay". But we should not create Pay section unless posting actually states them. Pay: Not explicitly stated; only "competitive pay". That is vague; we should not create Pay section because it's not specific. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (specific items). So we can include Benefits section with those specifics. - Schedule: The posting includes "Location & Schedule: This full-time, salaried position will generally work Monday through Friday, 8:00 a.m. to 4:30 p.m. Eastern Time. The role may be performed on-site at our Hastings, Michigan headquarters, in a hybrid arrangement, or remotely. Remote candidates must reside in Illinois, Indiana, Michigan, Ohio, or Wisconsin. All new employees attend in-person orientation at our Hastings headquarters, and remote employees should expect regular travel to Hastings for training, meetings, or company events." Thus schedule details: full-time, salaried, Monday-Friday 8am-4:30pm ET. Also location details. We can include schedule section with that info. The rule: include schedule only if posting actually states them. Yes. We should not include location as separate heading; but schedule section can contain location info as part of schedule? Probably okay. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "About Hastings Insurance" descriptive paragraph? That is about company; maybe we can keep as part of Benefits? Actually "About Hastings Insurance" is company overview; not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Hastings Insurance" is not boilerplate; it's company description. Might be considered part of the posting but not required sections. However we could include it as part of "About the role"? Might be redundant. Better to keep only relevant sections: About the role, Responsibilities, Requirements (What You'll Bring), Preferred Qualifications, Benefits, Schedule. Possibly also Skills? The posting does not have a separate Skills section; skills are embedded in requirements. So we skip Skills. We must not create sections with filler like "commensurate with experience". Not present. Now produce HTML fragment:

  About the role

  Lead the engineering, integration, and architecture behind our enterprise data ecosystem. Hastings Insurance is seeking a Data Engineering Manager to join our Information Technology team. In this leadership role, you will lead the team responsible for the engineering and operation of the data platforms, pipelines, integrations, and architecture that form the foundation of Hastings' enterprise data environment. You will oversee the movement, transformation, integration, storage, and availability of data across the organization, ensuring that enterprise data is reliable, scalable, secure, and accessible to the systems and teams that depend on it. This includes responsibility for data engineering, data warehousing, enterprise integration, data modeling, and the continued modernization of our data environment. This is an IT-focused data engineering leadership role rather than a business intelligence or analytics position. You'll partner closely with our Business Intelligence team and other technology and business stakeholders, while your team's primary focus remains the engineering, infrastructure, integration, and operational foundation that enables reporting, analytics, and business use of enterprise data.

  Responsibilities

  • Lead, coach, and develop a team responsible for enterprise data engineering, data warehousing, integration, and platform operations.
  • Provide technical leadership and direction for the design, development, deployment, and support of enterprise data pipelines and data platforms.
  • Guide the architecture and continued modernization of Hastings' enterprise data environment, balancing current operational needs with long-term scalability and maintainability.
  • Ensure reliable ingestion, movement, transformation, integration, and delivery of data across enterprise systems and downstream data consumers.
  • Establish and promote engineering practices that improve data quality, consistency, lineage, governance, security, and reliability.
  • Guide data modeling, warehousing, integration, and architectural practices that support scalable and reusable enterprise data solutions.
  • Partner closely with Business Intelligence, IT engineering and architecture teams, product owners, and other stakeholders to translate data needs into sustainable technical solutions.
  • Oversee production support and operational health of enterprise data solutions, including performance, reliability, troubleshooting, root cause analysis, and continuous improvement.
  • Evaluate emerging technologies and recommend solutions that improve scalability, automation, performance, reliability, and cost effectiveness.
  • Develop and manage maintenance schedules for enterprise data platforms and related systems.
  • Support vendor evaluations, contract discussions, and third-party data service relationships.
  • Stay informed on emerging data engineering practices and technology trends, including developments within the Property & Casualty insurance industry.
  • Lead the team responsible for the technical foundation of Hastings' enterprise data ecosystem.
  • Help shape the modernization and future direction of enterprise data engineering and architecture at Hastings.
  • Work across both established and evolving technologies as Hastings continues to modernize its data environment.
  • Partner closely with IT engineering, architecture, Business Intelligence, and organizational leadership.
  • Balance people leadership, technical direction, platform strategy, and operational responsibility.
  • Influence how enterprise data is engineered, integrated, governed, and made available throughout the organization.

  Requirements

  • Bachelor's degree in Information Technology, Computer Science, Engineering, Business, or a related field, or equivalent professional experience.
  • 10+ years of progressive experience in data engineering, enterprise data platforms, data warehousing, systems integration, or related disciplines.
  • Experience leading, mentoring, or providing technical direction to data engineering or other technical professionals.
  • Strong experience designing, developing, and supporting enterprise ETL/ELT pipelines and data integration solutions.
  • Strong understanding of data warehousing, data modeling, enterprise integration, and data architecture principles.
  • Experience working with relational databases and large-scale enterprise data environments.