Senior 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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive information. We need to parse the description. Key parts: - Description paragraph: At Liberty Mutual, technology isn't just a part of our business — it's what drives us forward... U.S. based role only We cannot consider candidates that require visa sponsorship or candidates that currently are on an F1 or OPT visa. This is a hybrid role requiring two days a week in the office (Tech hub office locations are located in Boston, Portsmouth, Indianapolis, Columbus, and Plano.) We are seeking a Senior Data Engineer with strong analytical skills to join our growing Data and Analytics Engineering team in the PL Product/Finance and Vendor Extract space. This is an exciting opportunity for an engineer who brings a blend of technical data engineering expertise and business analyst instincts — someone who not only builds data solutions but deeply understands the data they work with and the business problems they solve. Operating as an agile team within a Fortune 100 company, you will be on the front edge of an IT transformation, working collaboratively with business stakeholders, data scientists, and engineering peers to design and deliver high-quality data solutions. That's about the role. Then "Key Responsibilities" list bullet points. Then "Qualifications" list bullet points. Then "Preferred" bullet points. Then "About Us" paragraph about Pay Philosophy etc. Also "We value your hard work... benefits..." etc. We need sections: About the role (maybe from description), Responsibilities, Requirements (maybe combine Qualifications and Preferred?), Skills (maybe from qualifications?), Benefits, Pay, Schedule. We need to decide what content goes where. We have explicit "Key Responsibilities" list. We have "Qualifications" list (required). Also "Preferred" list. We have "About Us" includes Pay Philosophy and benefits description. We have schedule info: hybrid role requiring two days a week in the office (Tech hub office locations are located in Boston, Portsmouth, Indianapolis, Columbus, and Plano.) We have location info: U.S. based role only, cannot consider visa sponsorship etc. That could be part of Requirements? Might be part of About the role? It's a constraint. We need to avoid filler sections like "Pay" unless actual salary range given. There's a Pay Philosophy paragraph but no specific numbers. It says "The typical starting salary range for this role is determined by a number of factors...". That's vague but still mentions salary range. However instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The Pay Philosophy paragraph does state that there is a typical starting salary range determined by factors, and full salary range reflects competitive labor market value. It's not a specific number but it's stating that there is a salary range. Is that considered filler? It's not a specific number but it's still stating that there is a range. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "typical starting salary range ... determined by a number of factors" is somewhat vague but not exactly those filler phrases. It does say "full salary range for this role reflects the competitive labor market value". It's still vague but maybe acceptable to include Pay section with that paragraph. However we might consider it too vague; but the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay philosophy, so we can include Pay section with that content. Benefits: The posting mentions benefits: "We value your hard work, integrity and commitment to make things better, and we put people first by offering you benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://LMI.co/Benefits". That's a statement about benefits, albeit generic. It does mention benefits exist and a link. That's substantive enough? It's not a list but it's a statement. The instruction says avoid filler like "commensurate with experience". This is not that. So we can include Benefits section with that sentence. Schedule: hybrid role requiring two days a week in the office (Tech hub office locations are located in Boston, Portsmouth, Indianapolis, Columbus, and Plano.) That's specific schedule info. So we can include Schedule section. Now we need to decide sections: - About the role: combine the introductory paragraph(s) before Key Responsibilities. That includes description of company, role, hybrid, location constraints, etc. - Responsibilities: list from Key Responsibilities. - Requirements: maybe combine Qualifications (required) and maybe also include location/visa constraints? But those could be in About the role. We'll put Requirements as the Qualifications list (required). Could also include "Preferred" as separate Skills? Or we could have Skills section for preferred qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (covering both required and preferred), Benefits, Pay, Schedule. Or we could split Requirements and Skills. But we need to avoid many thin sections. Let's decide: About the role, Responsibilities, Requirements (including required qualifications), Benefits, Pay, Schedule. Preferred qualifications could be included under Requirements as "Preferred" bullet points, but we could also add a Skills section. However we have to avoid thin sections; adding Skills might be okay if we have content. Let's see: Preferred bullet points: Understanding of Cloud/Hybrid data architecture concepts, Exposure to data governance, data quality frameworks, or master data management concepts, Experience in the insurance or financial services industry is a plus. That's three bullets. Could be included under Requirements as "Preferred Qualifications". Might be okay to keep Requirements section with both required and preferred, labeling maybe not needed. But we can just list them as bullet points under Requirements. Thus we will have:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

(including required and preferred)

Benefits

...

Pay

...

Schedule

...

We must not include any boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting includes "Liberty Mutual is an equal opportunity employer..." and Fair Chance Notices etc. Remove those. Also remove "About Us Pay Philosophy:" heading? We'll incorporate into Pay section. Now we need to preserve all substantive information. Let's extract. About the role paragraph: "At Liberty Mutual, technology isn't just a part of our business — it's what drives us forward. We deliver our customers peace of mind every day by helping them protect what they value most. Our passion for placing the customer at the center of everything we do is driving a transformational shift at Liberty Mutual. U.S. based role only We cannot consider candidates that require visa sponsorship or candidates that currently are on an F1 or OPT visa. This is a hybrid role requiring two days a week in the office (Tech hub office locations are located in Boston, Portsmouth, Indianapolis, Columbus, and Plano.) We are seeking a Senior Data Engineer with strong analytical skills to join our growing Data and Analytics Engineering team in the PL Product/Finance and Vendor Extract space. This is an exciting opportunity for an engineer who brings a blend of technical data engineering expertise and business analyst instincts — someone who not only builds data solutions but deeply understands the data they work with and the business problems they solve. Operating as an agile team within a Fortune 100 company, you will be on the front edge of an IT transformation, working collaboratively with business stakeholders, data scientists, and engineering peers to design and deliver high-quality data solutions." We need to ensure we keep all that. Note there is a missing space after "U.S. based role only". We'll keep as is. Now Responsibilities list (from "Key Responsibilities"): - Design, develop, and maintain scalable data pipelines, data models, and integration processes using modern cloud-based technologies (AWS, Snowflake, etc.) - Analyze complex data sets and technical problems to design effective, flexible, and innovative solutions that meet business needs - Collaborate closely with Product Owners, business stakeholders, and cross-functional teams to translate business requirements into technical data solutions - Build and support ETL/ELT pipelines for structured and unstructured data from internal and external sources, including APIs, flat files, and enterprise applications - Implement data quality checks, validation rules, reconciliations, exception handling, and monitoring to ensure data integrity - Develop automated tests across multiple scopes (Unit, System, Integration, Regression) to ensure reliability and accuracy of data solutions - Perform data profiling, root cause analysis, and troubleshooting of data issues across production and non-production environments - Document data flows, data dictionaries, and technical specifications to support data governance and knowledge sharing - Identify and recommend continuous improvement opportunities across data engineering processes and tooling - Collaborate with engineers and architects, and actively contribute to code reviews and engineering best practices - Leverage AI-assisted development tools like GitHub Copilot - Actively uses AI tools to improve the speed, quality, and scale of work; can point to concrete workflows where AI adds value; critically evaluates and validates AI-generated output; and applies AI responsibly, protecting confidential and customer data. Note the last bullet is a bit long; we keep as is. Now Qualifications (required): - Bachelor’s degree in computer science, Engineering, Information Systems, or a related technical or business discipline (or equivalent experience) - 5-6 years of experience in data engineering, data analytics, or a related technical role - Strong proficiency in SQL, including writing complex queries, data modeling, and working with relational and analytical databases - Familiarity with cloud-based data platforms and tools such as Snowflake, AWS or similar technologies - Curious and open to exploring some mainframe technologies - Strong analytical and problem-solving skills with the ability to interpret and communicate data-driven insights - Demonstrated ability to work in an agile, squad-based environment with cross-functional teams - Proactive, self-motivated, and a logical thinker with strong attention to detail - Excellent written and verbal communication skills, with the ability to clearly convey technical concepts to non-technical stakeholders - Experience with data integration and ETL/ELT tools such as IDMC - Familiarity with CI/CD pipelines, version control (Git), and software development best practices Now Preferred: - Understanding of Cloud / Hybrid data architecture concepts - Exposure to data governance, data quality frameworks, or master data management concepts - Experience in the insurance or financial services industry is a plus We'll combine these under Requirements. Now Benefits section: from "We value your hard work, integrity and commitment to make things better, and we put people first by offering you benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://LMI.co/Benefits". Also earlier "About Us" includes: "At Liberty Mutual, our goal is to create a workplace where everyone feels valued, supported, and can thrive. We build an environment that welcomes a wide range of perspectives and experiences, with inclusion embedded in every aspect of our culture and reflected in everyday interactions. This comes to life through comprehensive benefits, workplace flexibility, professional development opportunities, and a host of opportunities provided through our Employee Resource Groups. Each employee plays a role in creating our inclusive culture, which supports every individual to do their best work. Together, we cultivate a community where everyone can make a meaningful impact for our business, our customers, and the communities we serve." That's also substantive about benefits and culture. We should include that as part of Benefits section