Remote Data Science AI Trainer

We need to output HTML fragment only, with headings

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

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

  for prose. Do NOT repeat the job title as a 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 cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description and extract sections. The posting includes: - Job Description (intro paragraph) - Responsibilities (list) - Essential Skills (list) - Additional Skills & Qualifications (list) - Work Environment (paragraph) - Job Type & Location (maybe metadata) - Pay And Benefits (pay range and benefits list) - Workplace Type (maybe duplicate) - Application Deadline (metadata) - About Actalent (company description) - EEO etc (boilerplate to remove) - San Francisco Fair Chance Ordinance etc (legal boilerplate to remove) - Use of Artificial Intelligence (AI) (boilerplate to remove) We need to include sections only if they have real specific content. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: The intro paragraph describing the role: "This project-based consulting role invites an experienced Data Scientist/Machine Learning Engineer to apply advanced analytical, statistical, and software engineering expertise to evaluate complex machine learning scenarios and real-world business use cases. You will develop and validate models, review analytical workflows, and provide expert guidance to ensure solutions are technically sound, scalable, and aligned with practical applications, all within a fully remote and flexible engagement." That's substantive. - Responsibilities: list of bullet points under "Responsibilities". We'll output

  • each. - Requirements: Could be "Essential Skills" maybe considered Requirements. Also "Additional Skills & Qualifications". Could combine into Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills. We need to decide which to include. We have Essential Skills (5+ years experience, proficiency in Python/SQL, etc). Additional Skills & Qualifications (deep learning, NLP, data engineering, A/B testing, forecasting, visualization, model validation, quantitative research, etc). Also "Work Environment" maybe not a heading but could be part of About the role? But we have headings for Schedule, Pay, Benefits. We have Pay And Benefits: pay range $125.00 - $125.00/hr (so fixed). Benefits list. We have Schedule: mention "Availability for approximately 30-40+ hours per week throughout the engagement." Also "Work Environment This is a fully remote, project-based consulting engagement that offers a flexible schedule and is best suited for professionals available 30 hours per week." So schedule info present. We have Workplace Type: "This is a fully remote position." Could be part of About the role or Schedule? But we have no heading for Workplace Type; we could incorporate into About the role or maybe not needed. We have Job Type & Location: "This is a Contract position based out of Virginia Beach, VA." That's minor metadata; we could fold into a short

    maybe under About the role or separate? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short paragraph about job type and location. Application Deadline: "This position is anticipated to close on Sep 30, 2026." That's metadata; could be short paragraph. About Actalent: company description; could be considered "About the role"? Actually "About the role" is about the role, not company. But we have no heading for "About the company". Could we include it under About the role? Might be okay to include as a short paragraph after role description? But we should not invent sections. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include About the role (we have). Responsibilities (we have). Requirements (we have essential skills). Qualifications (we have additional skills & qualifications). Skills (maybe we could combine essential and additional into Skills? But we already have Requirements and Qualifications; Skills could be redundant. However we could still include Skills if we have specific content: maybe we can list specific skills like Python, SQL, deep learning, NLP, etc. But we already have those in Requirements and Qualifications. To avoid thin sections, we could omit Skills heading and just use Requirements and Qualifications. But the instruction says prefer a few substantive sections over many thin ones. So we could combine essential and additional into one "Requirements" section, and maybe not need Qualifications. However we have both essential and additional; they are both qualifications. Could treat essential as Requirements, additional as Qualifications. That's two sections. We also need Benefits and Pay and Schedule sections if they have real content. Pay: we have pay range $125.00 - $125.00/hr (specific). Benefits: list of benefits (medical, dental, vision, etc). Schedule: we have availability 30-40+ hours per week, flexible schedule. Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include headings for empty or placeholder content. Now we need to format: - Use

    for section headings. - Use

    • for any list of duties/requirements/benefits. - Use

      for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to copy the exact wording from the posting for each bullet and paragraph, but we can format as HTML. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to exclude: - "Application Deadline This position is anticipated to close on Sep 30, 2026." This is metadata but not boilerplate; it's substantive? It's a date. Could be considered minor metadata; but we could fold into a short

      maybe under About the role? However the instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could include a short paragraph for metadata like job type, location, deadline. But we already have sections for Pay, Benefits, Schedule. Could we add a short paragraph under About the role for job type & location and deadline? That might be okay. But we need to preserve ALL substantive information; the deadline is substantive? It's a date; but it's not about the role itself. However the instruction says to fold minor metadata into a short

      or drop it. So we can include a short paragraph after the role description maybe. Similarly "Job Type & Location This is a Contract position based out of Virginia Beach, VA." That's metadata. We could include a

      after the About the role section that says: "This is a Contract position based out of Virginia Beach, VA. This position is anticipated to close on Sep 30, 2026." But we need to check if that duplicates any other info. Not duplicated elsewhere. Now we need to ensure we don't include any legal boilerplate like equal opportunity, San Francisco Fair Chance Ordinance, Massachusetts Lie Detector, Use of Artificial Intelligence (AI). Remove those. Also remove "About Actalent" maybe? That's company description; is that substantive? It's about the company, not the role. Could be considered boilerplate? It's not legal but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. However "About Actalent" is not about the role; but it's still substantive information about the employer. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. It's not legal or EEO. It's a company overview. Might be okay to keep. However we have no heading for "About the company". Could we include it under About the role? Might be odd. But we could add a separate section maybe "About the company" but not in allowed headings list. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a heading for About the company. So we must either fold it into About the role (as a short paragraph) or drop it. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop it, we lose info. If we fold it into About the role, we are still preserving it, just under a different heading. That seems acceptable. Thus we can include after the role description a paragraph that includes the company description. But we need to be careful not to duplicate content. Now let's extract the exact text. Intro paragraph: "Job Description Job Description: This project-based consulting role invites an experienced Data Scientist/Machine Learning Engineer to apply advanced analytical, statistical, and software engineering expertise to evaluate complex machine learning scenarios and real-world business use cases. You will develop and validate models, review analytical workflows, and provide expert guidance to ensure solutions are technically sound, scalable, and aligned with practical applications, all within a fully remote and flexible engagement." Note there is duplicate "Job Description Job Description:" at start. We should remove duplication. The actual content after that is the sentence. We'll keep the sentence. Now Responsibilities list: - Evaluate complex analytical and machine learning scenarios for technical accuracy, scalability, and business relevance. - Develop, validate, and refine statistical models, predictive analyses, and data-driven solutions that address real-world business problems. - Write, review, and optimize Python and SQL code used in data analysis and machine learning workflows. - Design realistic business and analytics use cases based on professional experience and industry best practices. - Assess modeling approaches, underlying assumptions, and analytical methodologies to ensure robustness and reliability. - Create clear, structured documentation and explanations for complex statistical and machine learning concepts. - Identify opportunities to improve analytical processes, outputs, and decision-support frameworks across projects. - Collaborate within structured project guidelines while managing tasks independently and proactively. - Maintain consistent quality, accuracy, and productivity throughout the engagement. - Provide expert insights on machine learning, deep learning, NLP, experimentation, forecasting, and model validation to support next-generation analytical and intelligent systems. - Communicate technical findings and recommendations effectively to both technical and non-technical stakeholders. Now Essential Skills list: - 5+ years of professional experience in Data Science, Machine Learning, Advanced Analytics, Quantitative Research, Data Engineering, or related fields. - Strong proficiency in Python and/or SQL for data analysis, modeling, and workflow development. - Hands-on experience developing, evaluating, or deploying analytical and machine learning models. - Solid understanding of core machine learning concepts and statistical methodologies. - Ability to explain complex technical concepts clearly to both technical and non-technical audiences. - Strong written communication skills for documentation and analytical reporting. - Comfort working independently in a fully remote environment. - Availability for approximately 30-40+ hours per week throughout the engagement.