Intern, Data Science, Machine Learning & AI-Remote

We need to output HTML fragment with sections: Overview? The instructions: use

for section headings (e.g. 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 (the page already shows it) and 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 decide which sections to include based on content. We have: - Overview: description of organization, internship program, etc. Could be "About the role" or "Overview". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for overview. - Internship Overview: includes Time Commitment, Duration, Location, Salary. That's schedule and pay. We can create sections: Schedule (Time Commitment, Duration) and Pay (Salary). Also location maybe part of schedule? Could embed in schedule. - Internship Outcomes: list of outcomes. Could be under "Responsibilities"? Actually outcomes are what intern will gain. Could be "Responsibilities" or "Learning Outcomes". But instruction only lists certain headings; we can use "Responsibilities" for duties, and maybe "Qualifications" for required qualifications. Outcomes could be part of "Responsibilities"? Might be better to have a section "What you'll learn" but not in allowed list. However we can still use "Responsibilities" for tasks; outcomes maybe not needed as separate section if we can incorporate into responsibilities? But we must preserve all substantive information; we cannot drop outcomes. Could put outcomes under a heading like "Internship Outcomes" but that's not in the allowed list; but instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those as examples. Probably we should stick to those headings where appropriate. Could treat outcomes as part of "Responsibilities" (they are what you will do/learn). But responsibilities list tasks; outcomes list what you will gain. Might be okay to have a separate section "Learning Outcomes" but not in list; risk of being considered filler? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict headings to only those examples. So we can add a heading like "Internship Outcomes". However 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 those types of content. But we can also add other headings if needed. Safer to stick to those headings and map content accordingly. We have: - About the role: overview paragraph(s) about organization and internship. - Responsibilities: list of tasks (the "Responsibilities" section). Use

  • . - Qualifications: list of qualifications (the "Qualifications" section). Use
    • . - Skills: maybe we can extract skills from qualifications? But qualifications already include skills. Could combine. - Benefits: there is a "Compensation & Benefits" section with details about benefits: Heart U, ERG, mentoring, Healthcare Benefits (Teladoc, EAP), etc. Also compensation: salary $23.00 per hour. So we need Pay and Benefits sections. Pay: salary. Benefits: list of benefits. - Schedule: Time Commitment: 20-25 hours per week; Internship Duration: 1/25/27-5/7/27; Location: Remote. Also Minimum availability of 20 hrs/wk, M-F between 8:30am-5pm. Must be legally authorized to work in US, etc. That's schedule info. We also have "Required Equipment: Reliable WiFi Connection." Could be part of schedule or qualifications? Probably schedule/requirements. We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "The job application window is expected to close: October 16, 2026." That's application instruction? Might be considered metadata; we can drop. Also "Visit Rewards & Benefits to see more details." That's generic; maybe drop. Also "Apply Today ..." etc. Also "In accordance with local and state laws..." EEO boilerplate; drop. Also "#AHAWAYUP", etc. Also "Join our Talent Community!" etc. Also "Software Powered by ICIMS Default: Location : Location US-TX-Dallas Posted Date 57 minutes ago (9/21/2026 3:53 PM) Requisition ID 2026-18243 Job Category Administrative Support Position Type Part Time" - drop. We must preserve all substantive information: overview paragraphs, responsibilities list, qualifications list, compensation, benefits, schedule, location, time commitment, duration, required equipment, legal work authorization. We need to format as HTML fragment. Let's draft:

      About the role

      Since our founding in 1924, we've cut cardiovascular disease deaths in half, but there is still so much more to do. To overcome today’s biggest health challenges and accelerate this progress, we need passionate individuals like you. Join our movement, be part of the progress, and help ensure a healthier future for all. You matter, and so does the impact you can make with us. The American Heart Association’s Internship Program provides college students an opportunity for hands-on experience in various facets for individuals interested in gaining work experience with a non-profit, voluntary health organization. This internship supports the Data Science team and provides hands-on experience in machine learning and artificial intelligence, with a primary focus on large language models (LLMs), generative AI, and agentic AI. The intern will build foundational knowledge of how LLMs work and apply LLMs to modeling, analytical workflows, and research use cases. Working with data scientists and cross-functional partners, the intern will help develop reproducible AI-enabled workflows and learn how to evaluate, validate, and document LLM-based solutions for clinical and biomedical research settings. The Association offers many resources to help you maintain work-life harmonization through your changing needs and life situations. To help you be successful, you will have access to Heart U, our award-winning corporate university, as well as training and support locally and through our National Center. #TheAHALife is more than a company culture; it is our way of life. It embodies our commitment to work-life harmonization and is guided by our core values where our employees can thrive both personally and professionally. Discover why you will Be Seen. Be Heard. Be Valued at the American Heart Association by following us on LinkedIn, Instagram, Facebook, X, and at heart.jobs.

      But we need to remove hashtags? The hashtag #TheAHALife is part of culture; it's substantive? Might keep but it's not essential. Could keep as text. We might want to remove the social media discovery sentence? It's still substantive about culture; but maybe it's okay. Now Responsibilities:

      Responsibilities

      • Support the design and development of LLM-powered applications and agentic AI workflows for clinical, biomedical, and operational research use cases.
      • Apply LLMs to modeling and analytical tasks, including information extraction, classification, summarization, question answering, and workflow orchestration.
      • Experiment with prompt design, structured outputs, retrieval-augmented generation, embeddings, vector search, tool use, and multi-step agent workflows.
      • Prepare, clean, organize, and document data used in LLM and generative AI experiments.
      • Develop reproducible prototypes and workflows using Python and approved AI/ML tools and platforms.
      • Design and perform evaluations of LLM systems using clearly defined criteria and appropriate quantitative and qualitative measures.
      • Conduct validation, error analysis, robustness testing, and comparison of model or workflow alternatives.
      • Assess issues such as hallucination, factual consistency, relevance, reliability, bias, privacy, and reproducibility.
      • Document methods, assumptions, prompts, evaluation results, limitations, and recommended improvements.
      • Contribute to technical documentation, presentations, abstracts, manuscripts, and cross-functional project discussions.
      Qualifications:

      Qualifications

      • Currently pursuing an MS or PhD degree in Computer Science, Artificial Intelligence, Biomedical Informatics, Data Science, Statistics, Engineering, Public Health, or a related quantitative field
      • Coursework or project experience with LLMs, generative AI, natural language processing, retrieval-augmented generation, or AI agents.
      • Experience using APIs or open-source frameworks to build and test LLM applications.
      • Programming experience in Python and familiarity with common data analysis or machine learning libraries.
      • Ability to understand and apply core LLM concepts such as tokens, context windows, embeddings, prompting, retrieval, and generation.
      • Strong analytical, problem-solving, organizational, and attention-to-detail skills.
      • Commitment to reproducible research, responsible AI practices, data quality, and clear documentation.
      • Ability to communicate effectively and collaborate with both technical and non-technical colleagues.
      • Experience working with cloud computing and/or high-performance computing environments (e.g., AWS, Snowflake, Azure, GCP).
      • Familiarity with model evaluation, experimental design, error analysis, version control, or reproducible workflow practices.
      • Experience with healthcare, clinical, or biomedical datasets is preferred.
      • Ability to work in a fast-paced, dynamic environment managing multiple priorities involving multiple entities.
      • Intermediate to excellent proficiency in Microsoft Word, Excel, Outlook, PowerPoint.
      • Required Equipment: Reliable WiFi Connection.
      • Minimum availability of 20 hrs/wk, M-F between the hours of 8:30am-5pm.
      • Must be legally authorized to work in the United States for any employer without sponsorship, now or in the future.
      • For any roles working remotely, the work must also be performed inside the United States, not in a foreign country.
      But note: some of those items are more about schedule/requirements; we might split schedule separately. However qualifications list includes availability and work authorization; those are not qualifications per se but still substantive. Could keep them there. But we also need a Schedule section: Time Commitment, Duration, Location. Could also include Minimum availability etc. However we already included those in qualifications; maybe better to move them to Schedule to avoid duplication. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay? It says remove duplicated lines. So we should avoid duplicating same info in multiple places. So we should not repeat Minimum availability etc in both Qualifications