Data Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. The posting includes: - THE POSITION: description about role, responsibilities, etc. Could be "About the role" or "Responsibilities". We need to decide. - THE GAME PLAN: bullet points under Build & Maintain Data Pipelines, Collaborate Across Teams, Data Quality & Operations. Those are responsibilities. - THE STATS: "What we're looking for in our next teammate": includes required qualifications (3+ years experience, SQL, etc.) and Preferred Qualifications. - About Fanduel: company description. - Player Benefits: benefits details. - Salary range: $116,000 - $145,000 USD. - Also mention other benefits: medical, vision, dental, life, disability, 401k matching, short/long term incentive, paid personal time off, 14 paid company holidays, paid sick time. - Also mention schedule? Not explicit. Thus sections we can include: - About the role (maybe from THE POSITION paragraph). Could be a short prose. - Responsibilities (from THE GAME PLAN bullet points). We'll need to convert bullet points into

• . - Requirements (the required qualifications from THE STATS: 3+ years experience, strong SQL, familiarity with programming language, hands-on experience with tools, understanding of data modeling, experience with cloud platforms). We'll list as
  . - Qualifications (maybe Preferred Qualifications). Could be separate section "Preferred Qualifications" but we only have headings list: Qualifications, Skills. Could combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications for required, and Skills for preferred? Or we could put required under Requirements, preferred under Qualifications, and maybe Skills separate if we have skill list. But we have skills mentioned: SQL, Python, etc. Could be under Skills. However we already have Requirements covering technical qualifications. Might be okay to have Requirements and Qualifications both. But we must not create sections with filler text. Must have real content. We have Benefits: from Player Benefits and also later list. Pay: salary range. Schedule: not present, so we should NOT include Schedule section. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie/legal. The posting includes a lot of EEO statement at end; we must remove that. Also remove duplicated lines. We need to preserve all substantive information. Let's extract substantive content: **About the role** (from THE POSITION): "The roster has an opening with your name on it We are looking for a Data Engineer to join our growing data engineering team and help build the pipelines and infrastructure that power analytics, machine learning, and business decision-making across the company. In this role, you’ll own the design, development, and maintenance of reliable data systems while collaborating with stakeholders to support high-impact data use cases. The ideal candidate is a strong technical contributor who enjoys working with data at scale, solving practical problems, independently executing on projects, and continuously learning in a fast-paced environment. If you’re excited by this challenge and want to work within a dynamic company, then we’d love to hear from you." Also there is a line: "In addition to the specific responsibilities outlined above, employees may be required to perform other such duties as assigned by the Company. This ensures operational flexibility and allows the Company to meet evolving business needs." This is generic but still substantive? It's a standard line; might be considered boilerplate? It's not EEO but it's a generic statement. Might be okay to keep? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is not exactly those, but it's a generic "other duties as assigned". Might be considered boilerplate but not explicitly listed. Safer to keep? It's not adding much value; but we can keep as part of About the role. **Responsibilities** (from THE GAME PLAN): We have three sub-sections: - Build & Maintain Data Pipelines: * Design, build, and maintain scalable batch and streaming data pipelines to support analytics and business operations. * Write clean, efficient, and well-documented code using tools like Python, SQL, and Spark. * Ensure data is reliable, accurate, and delivered in a timely manner. * Lead projects to build or improve well-scoped data products. - Collaborate Across Teams: * Work with data analysts, data scientists, and product managers to understand and clarify ambiguous requirements to deliver actionable data solutions. * Translate business questions into engineering tasks and contribute to technical planning. * Participate in code reviews, sprint planning, and retrospectives as part of an agile team. * Contribute to team wide best practices. - Data Quality & Operations: * Monitor data pipelines and troubleshoot issues in a timely, systematic manner. * Driving reliability and continuous improvement of data platforms and pipelines. * Implement data quality checks and contribute to observability and testing practices. * Document data sources, transformations, and architecture decisions to support long-term maintainability. We need to output as
  • items. Could combine all into one list or separate lists under subheadings? The instruction only says use
    • for any list of duties/requirements/benefits. It doesn't forbid subheadings inside. But we only have allowed headings list; we could add extra headings like

      but not in list. Safer to just make one flat list of all responsibilities. **Requirements** (from THE STATS required qualifications): - 3+ years of experience in data engineering, analytics engineering, or software engineering with a focus on data. - Strong SQL skills and familiarity with at least one programming language (e.g., Python, Java, or Scala). - Hands-on experience with modern data tools such as Databricks, Airflow, dbt, Spark, or Kafka. - Understanding of data modeling concepts, data warehousing, and ETL/ELT best practices. - Experience working with cloud-based data platforms (AWS, GCP, or Azure). **Qualifications** (Preferred Qualifications): - Experience supporting BI, analytics, or data science teams. - Familiarity with version control, CI/CD, and collaborative development workflows. - Exposure to data governance, privacy, or compliance practices. - Eagerness to learn new technologies and contribute to the growth of the team. **Skills** maybe we could list specific technical skills: Python, SQL, Spark, etc. But we already covered in Requirements. Could create Skills section summarizing tools: Python, SQL, Spark, Databricks, Airflow, dbt, Kafka, AWS/GCP/Azure. However that might be redundant. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section? But we have headings list includes both Requirements and Qualifications. Could we put required under Requirements and preferred under Qualifications? That seems appropriate. **Benefits** (from Player Benefits and later): - Health plans (some as low as $0 per paycheck) including programs for fertility and family planning, mental health support, and fitness benefits. - Generous paid time off (PTO & sick leave). - Annual bonus and long-term incentive opportunities (based on performance). - 401k with up to a 5% match. - Commuter benefits. - Pet insurance. - More benefits (see FanDuel Total Rewards). - Medical, vision, and dental insurance. - Life insurance. - Disability insurance. - 401(k) matching program. - Short-term or long-term incentive compensation (cash bonuses and stock program participation). - Paid personal time off and 14 paid company holidays. - Paid sick time in accordance with applicable state and federal laws. We need to avoid duplication. Combine similar items. **Pay** (salary range): $116,000 - $145,000 USD, dependent on experience, location, business needs, market demand. **Schedule**: not present, so omit. Also we have company description "About Fanduel". Could be a section "About the company" but not in allowed headings. Could we put under "About the role"? Probably not. The allowed headings list does not include "About the company". However we could include it as a paragraph under About the role? Might be okay to include as a separate section with heading "About the company" but not allowed. The instruction: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings like About Fanduel. We could incorporate that info into About the role or maybe omit? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description somewhere. If we cannot add a heading not in list, we could put it as a

      under About the role section (since it's still about the role/company). That would preserve info without extra heading. Thus About the role section will contain both the role description and company overview. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce something like:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      ...

      Qualifications

      ...

      Benefits

      ...

      Pay

      $116,000 - $145,000 USD, dependent on relevant experience, location, business needs and market demand.

      We must ensure we don't include filler like "commensurate with experience". Not present. Check for any duplicated lines: we need to avoid repeating same benefit twice. Let's craft the About the role paragraph: Combine: "The roster has an opening with your name on it. We are looking for a Data Engineer to join our growing data engineering team and help build the pipelines and infrastructure that power analytics, machine learning, and business decision-making across the company. In this role, you’ll own the design, development, and maintenance of reliable data systems while collaborating with stakeholders to support high-impact data use cases. The ideal candidate is a strong technical contributor who enjoys working with data at scale, solving practical problems, independently executing on projects, and continuously learning in a fast-paced environment. If you’re excited by this challenge and want to work within a dynamic company, then we’d love to hear from you. In addition to the specific responsibilities outlined above, employees may be required to perform other such duties as assigned by the Company. This ensures operational flexibility and allows the Company to meet evolving business needs. FanDuel Group is the premier mobile gaming company in the United States and Canada. FanDuel Group consists of a portfolio of leading brands across mobile wagering including: America’s #1 Sportsbook, FanDuel Sportsbook; its leading iGaming platform, FanDuel Casino; the industry’s unquestioned leader in horse racing and advance-deposit wagering, FanDuel Racing; and its daily fantasy sports product. In addition, FanDuel Group operates FanDuel TV, its broadly distributed linear cable television network and FanDuel TV+, its leading direct-to-consumer OTT platform. Fan