Data Engineering Intern

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key info: Compensation: $28 per hour Location: Omaha, NE The Job: description. What You Will Do: list of duties. Who You Are And What You Need: qualifications/requirements. We Are Giving You: benefits/perks. Who We Are: company description (maybe About the role? Actually "About the role" could be the description of the job: The Job paragraph. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content maps. - About the role: maybe the introductory paragraph: "As a Data Engineering Intern, you'll spend the summer building the datasets and pipelines..." That's about the role. - Responsibilities: the "What You Will Do" bullet list. - Requirements: maybe "Who You Are And What You Need" includes requirements like pursuing degree, availability, interest, etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. We can combine some. We need to include Pay: compensation $28 per hour. Schedule: maybe mention "No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m." Also "Available to work full-time onsite at the Buildertrend HQ in Omaha, NE, for the full summer." That's schedule. Benefits: "We Are Giving You" list: Office environment with perks, free daily lunches, summer housing, onsite fitness center, no weekend hours (but that's schedule), monthly events. We also have location: Omaha, NE. We need to include location maybe in About the role or a separate meta? Could be in About the role paragraph. We must not include boilerplate like EEO, legal, etc. Must remove those paragraphs. We must not include navigation, cookie, etc. We must not repeat job title. We must not include Job ID. We must not include application instructions. We must not include "Working At Buildertrend" etc? That is some culture description maybe could be part of About the role? But it's somewhat generic; we can include if substantive. It says: "At Buildertrend, we fully recognize that we all work so we can live better lives..." That's fluff but maybe considered boilerplate? It's not EEO but it's culture. Might be okay to include as part of About the role? But we need to avoid filler. It's somewhat generic but still substantive about company culture. Could include in About the role or maybe a separate "About the company" but not required heading. Since we have limited headings, we could incorporate into About the role. We must not create sections with placeholder text like "commensurate with experience". We have actual pay. We must not create Benefits section unless posting actually states them. It does: free daily lunches, summer housing, onsite fitness center, monthly events. So we can create Benefits. Schedule: we have "No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m." Also "Available to work full-time onsite ... for the full summer." That's schedule. Pay: $28 per hour. Now we need to output HTML fragment only. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Maybe we split Requirements and Qualifications and Skills but we can combine into Requirements (including qualifications and skills). However the instruction says use those headings only if there is real specific content. We could create Requirements for degree, availability, interest; Qualifications for SQL, programming language; Skills for AI tools, problem-solving, communication, teamwork. But that may create many thin sections. Better to have fewer substantive sections. Could do: About the role, Responsibilities, Qualifications (covering degree, skills, etc.), Benefits, Pay, Schedule. That's 6 sections. But we need to follow the list of allowed headings; we can omit others. Thus: About the role: includes The Job paragraph + company description maybe. Responsibilities: What You Will Do list. Qualifications: Who You Are And What You Need list (including degree, availability, interest, SQL, programming language, curiosity about Databricks/dbt, AI tools experience, problem-solving, communication, independent/team work, eager to learn). Could also include location? Already in About. Benefits: We Are Giving You list. Pay: Compensation. Schedule: No weekend hours, Monday-Friday 8-5, full-time summer. We must ensure we don't repeat info. Let's extract exact sentences. About the role: "The Job As a Data Engineering Intern, you'll spend the summer building the datasets and pipelines that teams across Buildertrend rely on to make decisions. You'll work alongside experienced data engineers, get hands-on with a modern data stack, and learn how raw data from tools like Salesforce and SQL Server becomes curated, trustworthy datasets that power our BI, analytics and AI initiatives. We don't expect you to already know every framework we use. We're looking for curiosity, solid fundamentals and a real interest in the craft of data engineering. By the end of the internship, you'll have sharpened your technical skills, gained real engineering experience and shipped work that helps the business run on numbers people can trust." Also maybe include "We Are Giving You" is benefits, not about role. Also "Who We Are" paragraph about Buildertrend: "Great builders don’t just manage projects – they run successful businesses. That’s where Buildertrend comes in. As the leading residential construction management platform, we give contractors the power to control their financials, schedules, team workflows and client relationships – all in one system. No more juggling disconnected tools or guessing on profitability. With nearly two decades of industry expertise, Buildertrend helps builders work smarter, scale faster and stay ahead of the competition. If you want to learn more about us, check out: https://buildertrend.com/about/" And "Working At Buildertrend" paragraph: "At Buildertrend, we fully recognize that we all work so we can live better lives—we appreciate and respect that this is a job and not your whole life. What makes Buildertrend so special is a commitment to ensuring you can have the best job, work with the best people, and live your best life outside of work. Our goal is to create a culture where everyone can make an impact on our customers, communities, and each other. In short: We want you to be who you are, love what you do, and build your best life." These are somewhat fluff but could be considered About the role/company. Might be okay to include. But we must avoid boilerplate; these are not legal EEO. They are descriptive. Could include. But we need to be careful not to include too much fluff; but it's still substantive about company. We'll include a concise version: maybe combine The Job and Who We Are and Working At Buildertrend into About the role. Now Responsibilities: list from "What You Will Do". Each sentence starts with a verb. List: - Help build and maintain ELT/ETL pipelines that bring data in from sources like SQL Server, Salesforce and other business tools, and turn it into clean, usable datasets. - Write SQL to transform, model and prepare data that supports BI, product analytics, and ML/AI use cases. - Partner with Data Engineers, Analysts and other stakeholders to understand what a dataset needs to do before you build it. - Learn our modern data stack, including Databricks, dbt and a medallion (bronze, silver, gold) approach to organizing data, with guidance and mentorship along the way. - Write and run data quality and freshness checks so the teams using your datasets can trust the numbers. - Document what you build, including table definitions, column notes and simple diagrams, clearly enough for both people and AI tools to use. - Use AI-assisted development tools, including Claude, to accelerate coding, debugging and problem-solving workflows while still being responsible and accountable for the quality and accuracy of your work. - Complete assigned tasks and projects within established sprint timelines. Now Qualifications: from "Who You Are And What You Need". List: - Currently pursuing a bachelor’s degree in computer science, data science, or a related field. - Available to work full-time onsite at the Buildertrend HQ in Omaha, NE, for the full summer. - Strong interest in data engineering, including building datasets, ETL/ELT, and getting data ready to support BI, analytics and ML/AI work. - Familiar with SQL and at least one programming language such as Python (through coursework or personal projects is perfectly fine). - Curiosity about data tools and frameworks like Databricks and dbt, and an eagerness to learn them on the job. - Experience using AI tools (such as Claude, GitHub Copilot or similar) in coursework or personal projects, or a strong interest in learning how to use them effectively. - Strong problem-solving and analytical skills, and comfort working with data. - Clear and effective written and verbal communication skills. - Comfortable working independently and as part of a team. - Eager to learn, ask questions and apply feedback constructively. We could also include location but we already have location in availability. Now Benefits: from "We Are Giving You". List: - Office environment with all the perks of a high-energy tech company. - Free daily lunches at the office. - Summer housing at a local university – you can skip the summer housing search and focus on the experience. - Onsite fitness center to keep you feeling your best. - No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m. (but that's schedule; maybe we move to Schedule) - Monthly events to connect other interns and Buildertrend employees. We need to avoid duplication; schedule part we will put in Schedule section. Thus Benefits: office environment, free daily lunches, summer housing, onsite fitness center, monthly events. Now Pay: "$28 per hour". Schedule: "No weekend hours – just work hard Monday-Friday between 8 a.m. and 5 p.m." Also "Available to work full-time onsite at the Buildertrend HQ in Omaha, NE, for the full summer." (but that's also in Qualifications; we might keep availability in Qualifications; schedule can just be the hours). We'll include schedule: Monday-Friday 8am-5pm, no weekend hours, full-time summer. Now we need to output HTML. We'll wrap each section in

and then

or

. For About the role: we can use

with multiple sentences. We must not include any extra text outside HTML. Let's craft. About the role paragraph: combine The Job, Who We Are, Working At Buildertrend maybe summarized. But we must preserve ALL substantive information; cannot invent or summarize away detail. Summarizing is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details; we must keep all details. Summarizing may be considered summarizing away detail? It says do NOT summarize away detail. So we should keep the details as they are, not condense them into a summary that loses specifics. However we can rephrase but must keep all info. Safer to keep the original sentences. Thus we could just include the original paragraphs as is, maybe split into multiple

tags. We can include the exact sentences from The Job, Who We Are, Working At Buildertrend as separate paragraphs under About the role. But we must avoid duplication; there is no duplication. Thus About the role will have multiple