Data Scientist

We need to output HTML fragment with headings

for sections that have real content. Sections: About the role, Key Responsibilities, Required Qualifications, Preferred Qualifications, Skills & Competencies, Education & Experience, Work Arrangement & Schedule, Compensation & Benefits, Compliance / Additional Information? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use headings matching content. Should not repeat job title as heading. Should not put Job ID etc. Should include a section only when posting has real specific content. We need to preserve all substantive info, no invented or summarized away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's none. Also remove duplicated lines and application instructions. There's no explicit application instructions. The "Work Arrangement & Schedule" includes remote, full-time, mid-senior level, job function, and note that source does not specify weekly hours etc. We should include that info but not include placeholder like "not specified". The note says "The source job description does not specify weekly hours, working days, or required schedule flexibility." That's basically saying schedule not specified; we should not create a Schedule section if no specifics. However we have Work Arrangement & Schedule section with some content: Work Arrangement: Remote, Employment Type: Full-time, Seniority Level: Mid-Senior level, Job Function: Information Technology. That's substantive. So we can keep a section maybe called "Work Arrangement". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt. Probably better to follow the given examples but we can also use similar headings: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Skills & Competencies, Education & Experience, Work Arrangement, Compensation & Benefits, Additional Information. Use

for each. We need

• for any list of duties/requirements/benefits. So for Responsibilities, Required Qualifications, Preferred Qualifications, Skills & Competencies, Education & Experience (maybe list), Benefits (maybe list), etc. We need

  for prose. We must not repeat job title as heading. So no

  Sports Data Scientist

  . We must not include Pay/Schedule/Benefits sections unless posting actually states them. Pay: they gave Base Pay Range: $70,000–$80,000 per year. That's specific, so we should include a Pay section. Benefits: they gave employee testimonials about casual environment, work-life balance, culture. Those are not specified benefits but they are statements. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Base Pay Range, so Pay section is okay. For Benefits, they gave employee testimonials describing casual environment etc. Are those considered benefits? They are not explicit benefits like health insurance, but they are statements about culture. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot include a Benefits section if they mention benefits-like statements. However they said "These statements are presented as employee testimonials rather than specified benefits." So maybe we should not create a Benefits section because they are not specified benefits. Safer to omit Benefits section. Instead we could include them under Additional Information or maybe under Compliance/Additional Information. But we have a Compliance / Additional Information section that includes industries, business model description. That's substantive. We'll keep that. Pay section: include base pay range. Schedule: they said source does not specify weekly hours etc. So we should not create a Schedule section because no specifics. However we have Work Arrangement & Schedule section with remote, full-time etc. That's more about work arrangement. The instruction's example includes Schedule as a possible heading, but we should only include if posting states them. Since they didn't specify schedule, we omit Schedule heading. But we still have Work Arrangement info; we could put that under a heading like "Work Arrangement". That's allowed. Now we need to ensure we preserve all substantive information. Let's extract: About the Role: paragraph. Key Responsibilities: list of bullet points (each starts with *). We'll convert to
  • . Required Qualifications: list. Preferred Qualifications: list (one item). Skills & Competencies: list (many items). Could be long; we keep as list. Education & Experience: includes Education bullet and Experience bullet list. Work Arrangement & Schedule: includes Work Arrangement: Remote, Employment Type: Full-time, Seniority Level: Mid-Senior level, Job Function: Information Technology. Also note that source does not specify weekly hours etc. We should not include that note as it's basically saying no schedule info. We could omit that sentence. But we need to preserve all substantive information; that sentence is substantive? It's saying they don't specify schedule. That's meta. Might be considered boilerplate? It's not boilerplate but it's a statement about missing info. The instruction says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not include that sentence because it's essentially "not specified". So we omit that sentence. Compensation & Benefits: Base Pay Range: $70,000–$80,000 per year. Also note about final compensation based on skills and experience. Also employee testimonials about casual environment etc. Since we are not making Benefits section, we could include the testimonials under Additional Information or maybe under a "Company Culture" heading? But instruction says only include sections when posting has real specific content. The testimonials are specific content. Could we include them under a heading like "Company Culture"? Not in the examples but we can create a heading if we want. However they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not exclusive list. So we could add a heading like "Company Culture". But safer to put them under "Additional Information" or "Compliance / Additional Information". However that section already has industries and business model. We could add a paragraph there. Compliance / Additional Information: includes Industries: Business Consulting and Services; Sports Teams and Clubs. The company operates in sports data science and analytics space and works with NCAA programs... Its stated business model includes providing financial support and career resources to individuals early in their professional journey in exchange for a share of future earnings over a defined period. We'll keep that. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

    About the Role

    Our client is seeking a Sports Data Scientist to support NCAA collegiate programs with data-driven insights, particularly in the football, baseball, and basketball transfer portal. This role combines statistical data analysis, predictive modeling, data visualization, and deep sports knowledge to help clients evaluate transfer opportunities and make informed decisions. The ideal candidate has a strong foundation in data science and analytics, proficiency in Python and SQL, experience creating programmatic data visualizations, and the ability to communicate complex analytical concepts to nontechnical audiences. A strong interest in sports analytics and curiosity to challenge traditional assumptions about sports are important for success in this role.

    Responsibilities

    • Build predictive models using client data, analytical insights, and sports knowledge.
    • Conduct exploratory data analysis to identify data-driven insights related to the collegiate transfer portal.
    • Provide analytical support and actionable insights to collegiate programs.
    • Answer ad-hoc questions related to transfer targeting.
    • Analyze data to support decision-making across NCAA football, baseball, and basketball programs.
    • Ensure data integrity and accuracy across multiple data sources.
    • Prepare accurate and timely reports.
    • Communicate analytical findings and complex data concepts to nontechnical audiences.

    Required Qualifications

    • Bachelor’s degree in Statistics, Computer Science, Data Science, or a related field.
    • Programming experience.
    • Proficiency with Python, including pandas, Polars, and NumPy.
    • Proficiency with SQL.
    • Experience generating data visualizations programmatically.
    • Deep understanding of sports.
    • Strong communication skills with the ability to explain complex data concepts to nontechnical audiences.
    • Strong self-motivation and curiosity.
    • Attention to detail and commitment to accurate, timely reporting.

    Preferred Qualifications

    • Experience playing or working with college football, baseball, or basketball teams.

    Skills & Competencies

    • Sports analytics
    • Statistical data analysis
    • Predictive modeling
    • Exploratory data analysis
    • Data visualization
    • Python
    • pandas
    • Polars
    • NumPy
    • SQL
    • Data integrity and accuracy
    • Transfer portal analysis
    • Programming
    • Sports knowledge
    • Communication and data storytelling
    • Problem-solving
    • Self-motivation
    • Curiosity
    • Attention to detail
    • Ability to communicate with nontechnical audiences

    Education & Experience

    Education: Bachelor’s degree in Statistics, Computer Science, Data Science, or a related field.

    Experience:

    • Programming experience.
    • Experience with Python, including pandas, Polars, and NumPy.
    • Experience with SQL.
    • Experience generating data visualizations programmatically.
    • Experience in college football, baseball, or basketball is preferred but not required.

    Work Arrangement

    Work Arrangement: Remote

    Employment Type: Full-time

    Seniority Level: Mid-Senior level

    Job Function: Information Technology

    Pay

    Base Pay Range: $70,000–$80,000 per year. Final compensation will be based on skills and experience.

    Additional Information

    The company operates in the sports data science and analytics space and works with NCAA programs using data science and analytics to evaluate player value and fit within the evolving transfer portal. Its stated business model includes providing financial support and career resources to individuals early in their professional journey in exchange for a share of future earnings over a defined period.

    Industries: Business Consulting and Services; Sports Teams and Clubs.

    Employee feedback highlights a casual and collaborative environment, work-life balance, and a company culture focused on supporting employees.

    We need to ensure we didn't repeat job title as heading. We didn't. Check for any filler/placeholder text: we omitted the note about schedule not specified. Good. Check for duplication: we didn't duplicate. Check for any boilerplate: we removed compliance heading? We kept Additional Information but we could rename to Compliance / Additional Information. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if needed. It's okay. We need to ensure we used

    for section headings. Yes. We used