Data Scientist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to extract content: Job Summary: description of role. Job Responsibilities: bullet list (multiple sentences). We'll need to format as

  • . Job Requirements: bullet list (multiple). Also includes "What CRH Offers You": includes benefits: Highly competitive base pay, Comprehensive medical, dental and disability benefits programs, Group retirement savings program, Health and wellness programs, An inclusive culture that values opportunity for growth, development, and internal promotion. Also "About CRH": description of company. We need to decide sections: maybe "About the role" (Job Summary), "Responsibilities", "Requirements", "Benefits". Possibly also "About the company". But we should avoid thin sections. The posting includes "About CRH" which is company overview; could be included as "About the company" or maybe not needed? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning we can use those headings if appropriate. We can also use other headings? Probably stick to those. We have content for About the role (Job Summary). Responsibilities. Requirements (Job Requirements). Benefits (What CRH Offers You). Pay: they mention "Highly competitive base pay" which is pay info, but we could include under Benefits or separate Pay section. Since they explicitly mention pay, we could create a Pay section with that line. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state pay: "Highly competitive base pay". So we can include Pay section. Benefits: they list medical, dental, disability, retirement, wellness, inclusive culture. So Benefits section. Schedule: not mentioned. So omit. Qualifications/Skills: Could be part of Requirements. We have Requirements list includes education, experience, skills. Could combine into Requirements. Or separate Qualifications and Skills. But we should prefer few substantive sections over many thin ones. So maybe combine into Requirements. Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Pay (h3), Benefits (h3). Possibly also About the company? Not in list but could be omitted. We need to preserve all substantive information. Let's extract details. Job Summary paragraph: "We are looking for a highly motivated individual to join our Oldcastle ABP Operational Performance Systems team. The individual is responsible for creating and managing enterprise level analytics and data science solutions that deliver actionable insights. This includes execution of the full development lifecycle and requires a strong background in data, statistics and machine learning, business analysis, and process improvement, along with excellent communication skills. The ideal candidate is an analytical problem solver with solid business acumen who can translate business needs into technical requirements and apply modern data science and AI tooling – including Snowflake Cortex and large language models (LLMs) – to real operational problems." That's the summary. Responsibilities: list of sentences separated by periods? Let's extract each bullet: - Development and support of operational systems, creating SOPs, providing training, and identifying key metrics that measure adoption and utilization. - Ability to work independently and with a team, to drive projects forward meeting timelines and objectives. - Craft and construct visually engaging, creative, and easy-to-use data delivery solutions including dashboards, scorecards, infographics, and reports that enable users to be more productive and better informed. - Partner with the business and IT to identify opportunities where additional insight/metrics could add value - Research and provide recommendations for ways to better utilize technology to improve our business operational processes and profitability. - Design, build, and deploy data science models – including forecasting, classification, anomaly detection, and optimization – that improve operational and commercial decision making. - Develop AI-enabled solutions using Snowflake Cortex and large language models (LLMs), including retrieval-augmented generation, document and text analysis, and natural language access to enterprise data. - Establish practices for model validation, monitoring, documentation, and responsible AI use so that solutions remain accurate, explainable, and supportable in production. We need to keep each as
  • . Job Requirements: list: - 2 + years of experience designing, building, and deploying BI/analytical solutions and reports - Bachelor’s degree or equivalent in computer science, data science, statistics, engineering, math, or another technical field - Advanced data visualization tool knowledge (Tableau) - Intermediate to advanced SQL skills, including hands-on work in a cloud data platform (Snowflake preferred) - Working proficiency in Python for data analysis and modeling (e.g., pandas, scikit-learn); R also considered - Hands-on experience applying data science and machine learning techniques such as regression, classification, clustering, and time series forecasting to business problems - Practical experience with LLMs and generative AI – prompt engineering, retrieval-augmented generation (RAG), or embedding-based search - Familiarity with Snowflake Cortex (Cortex Analyst, Cortex Search, Cortex AI functions) or comparable in-platform AI/ML services - Excellent written and verbal communication skills - Ability to travel domestically up to 25% We could also note "What CRH Offers You" as Benefits and Pay. Pay: "Highly competitive base pay" Benefits: list: - Comprehensive medical, dental and disability benefits programs - Group retirement savings program - Health and wellness programs - An inclusive culture that values opportunity for growth, development, and internal promotion We could also include "About CRH" description but maybe not needed as it's not a standard heading. However we might include as "About the company" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but better to stick to those. The "About CRH" is company overview; maybe we can incorporate into About the role? Not really. Could omit as it's not essential to the role? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "About the company" but not in list; maybe we can add as a

    under a generic heading like "About CRH". But the instruction says use those headings for section headings; it's not strict that we cannot use others, but we should follow the pattern. Safer to include as a

    after the Benefits section without a heading? But they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we could still have a heading like "About CRH" but it's not in the list; maybe it's okay but better to avoid. Could we incorporate the About CRH description into the About the role section? That would mix company overview with role summary, but maybe acceptable. However the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It doesn't forbid other headings. I'd include a section "About the company" as

    About the company. But the examples didn't list it; but it's not prohibited. However they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not exhaustive. So we can add About the company. Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits, About the company. We need to ensure we don't create empty sections. All have content. Now produce HTML fragment: no /, no markdown fences. We'll output:

    About the role

    We are looking for a highly motivated individual to join our Oldcastle ABP Operational Performance Systems team. The individual is responsible for creating and managing enterprise level analytics and data science solutions that deliver actionable insights. This includes execution of the full development lifecycle and requires a strong background in data, statistics and machine learning, business analysis, and process improvement, along with excellent communication skills. The ideal candidate is an analytical problem solver with solid business acumen who can translate business needs into technical requirements and apply modern data science and AI tooling – including Snowflake Cortex and large language models (LLMs) – to real operational problems.

    Responsibilities

    • Development and support of operational systems, creating SOPs, providing training, and identifying key metrics that measure adoption and utilization.
    • Ability to work independently and with a team, to drive projects forward meeting timelines and objectives.
    • Craft and construct visually engaging, creative, and easy-to-use data delivery solutions including dashboards, scorecards, infographics, and reports that enable users to be more productive and better informed.
    • Partner with the business and IT to identify opportunities where additional insight/metrics could add value
    • Research and provide recommendations for ways to better utilize technology to improve our business operational processes and profitability.
    • Design, build, and deploy data science models – including forecasting, classification, anomaly detection, and optimization – that improve operational and commercial decision making.
    • Develop AI-enabled solutions using Snowflake Cortex and large language models (LLMs), including retrieval-augmented generation, document and text analysis, and natural language access to enterprise data.
    • Establish practices for model validation, monitoring, documentation, and responsible AI use so that solutions remain accurate, explainable, and supportable in production.

    Requirements

    • 2+ years of experience designing, building, and deploying BI/analytical solutions and reports
    • Bachelor’s degree or equivalent in computer science, data science, statistics, engineering, math, or another technical field
    • Advanced data visualization tool knowledge (Tableau)
    • Intermediate to advanced SQL skills, including hands-on work in a cloud data platform (Snowflake preferred)
    • Working proficiency in Python for data analysis and modeling (e.g., pandas, scikit-learn); R also considered
    • Hands-on experience applying data science and machine learning techniques such as regression, classification, clustering, and time series forecasting to business problems
    • Practical experience with LLMs and generative AI – prompt engineering, retrieval-augmented generation (RAG), or embedding-based search
    • Familiarity with Snowflake Cortex (Cortex Analyst, Cortex Search, Cortex AI functions) or comparable in-platform AI/ML services
    • Excellent written and verbal communication skills
    • Ability to travel domestically