Graduate AI Engineer Intern Summer 2027

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 specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key content: - Application window close date: "We anticipate the application window for this opening will close on - 16 Oct 2026". That's a date; could be placed maybe in a short

under maybe a heading? There's no specific heading for dates; we could include a short

at top maybe. - Intro paragraph: "At MiniMed, you can begin a lifelong career of exploration and innovation, while helping make a difference in the lives of people living with diabetes around the globe. You'll lead with purpose, breaking down barriers to innovation for a more connected, compassionate world." - About The Role: heading "About The Role". Content: "Join MiniMed for a summer internship where you’ll do meaningful work, gain hands-on experience, and make an impact on our mission to make every day a better day for people with diabetes. You’ll be part of a collaborative intern community, build your professional network, and gain exposure to opportunities that help you grow both personally and professionally. Our summer internships are full-time (40 hours/week), paid positions lasting 10-11 weeks. We offer competitive compensation, educational and social programming throughout the summer, as well as housing assistance and relocation support for eligible interns." - Then: "At MiniMed, we're transforming how a medical device company operates through artificial intelligence, and we want you to help drive that transformation. As an AI Engineer Intern, you'll be embedded within MiniMed's AI & Data Science team, working at the intersection of cutting-edge AI technology and real-world business impact. This is a hands-on, build-and-ship role, not a research or observation role. You'll own a scoped project from problem definition to prototype development and evaluation, partnering with technical teams and business stakeholders to deliver measurable business value. Your work will span two of our core AI focus areas: AI Agents and Tools: Design, build, and evaluate LLM-powered agents on our MIA stack. You’ll work with industry-standard technologies, including AWS Services, Databricks and LangGraph, to develop reliable solutions for real business needs. Enterprise AI Enablement: Help expand self-service AI adoption across the enterprise by building and deploying reusable agents and function-specific skills. You’ll empower teams to apply AI in their day-to-day workflows and improve how they work. Project Examples May Include Prototyping a domain-specific AI agent for a business function Developing and running evaluation test sets to measure agent quality, detect hallucinations, and identify regressions Building reusable agent skills and applying guardrails to ensure responsible, auditable outputs Along the way, you'll gain practical grounding in evaluation-driven development, exposure to responsible AI delivery in a regulated medical-device environment (privacy, auditability, human-in-the-loop design), and real-world experience translating a business need into a shipped, measurable solution. You'll leave with a strong portfolio of applied AI work and a deeper understanding of how enterprise AI strategy gets executed in a complex, compliance-driven industry." That's responsibilities and description. - Location and Work Model: "Location and Work Model This internship is based in John's Creek, GA. All interns must reside in the U.S. for the duration of the internship. Interns are expected to work onsite a minimum of 3 days per week and participate full time, 40 hours per week, during the summer of 2027." - Must Have: Minimum Requirements: bullet list. - Nice to Have: bullet list. - Physical Job Requirements: some generic text; we might include as a section? It's generic but maybe we can include as "Physical Job Requirements" but it's mostly boilerplate. The instruction: remove boilerplate, duplicated lines, EEO etc. Physical Job Requirements seems generic but maybe we can keep as it's part of posting. However it's mostly generic statements about accommodations. Might be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Job Requirements is not exactly those but could be considered generic. I'd lean to keep it if it contains substantive info? It says: "The above statements are intended to describe the general nature and level of work being performed by employees assigned to this position, but they are not an exhaustive list of all the required responsibilities and skills of this position. The physical demands described within the Responsibilities section of this job description are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. For Office Roles: While performing the duties of this job, the employee is regularly required to be independently mobile. The employee is also required to interact with a computer and communicate with peers and co-workers. Contact your manager or local HR to understand the Work Conditions and Physical requirements that may be specific to each role." That's fairly generic but still part of posting. Might be considered boilerplate but not explicitly listed to remove. I'd keep it maybe under a heading "Physical Job Requirements". However the instruction says "Prefer a few substantive sections over many thin ones." This section is thin and generic; maybe we can omit it. I'd omit. - Benefits & Compensation: includes salary range, benefits description. This is substantive. We'll create sections: Benefits, Pay (maybe combine). The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need Pay and Benefits sections if they have specifics. Pay: they give hourly rate range $26.50 to $45.25 per hour. That's specific. Benefits: they list many benefits (health, dental, vision, HSA, FSA, life insurance, LTD, dependent daycare, incentive plans, 401(k) match, short-term disability, PTO, holidays, ESPP, EAP, non-qualified retirement plan supplement, capital accumulation plan). That's specific. So we can have

Pay

with

containing the hourly rate range and note about determination. And

Benefits

with

• list. - Schedule: they mention full-time (40 hours/week), 10-11 weeks, onsite minimum 3 days per week. That's schedule info. Could be a Schedule section. But we already have some schedule info in About the role (full-time 40h/week, 10-11 weeks). Also location and work model includes onsite 3 days/week. So we could create a Schedule section summarizing: full-time 40 hours/week, 10-11 weeks, onsite minimum 3 days per week. That's specific. So include Schedule. - About MiniMed: description of company; could be a section "About MiniMed". That's substantive. - Also there is a line: "Location and Work Model". Could be a section "Location". But we already have location in Schedule? Might be separate. However we can combine location into About the role? The instruction: prefer few substantive sections over many thin ones. We could have sections: About the role, Responsibilities (maybe we already covered in About the role?), Requirements, Qualifications, Skills, Benefits, Pay, Schedule, About MiniMed. But we need to avoid duplication. We have content that maps to: - About the role: we have a heading "About The Role". We'll keep that. - Responsibilities: we have detailed description of what you'll do (AI Engineer Intern tasks). Could be under Responsibilities. - Requirements: Minimum Requirements (Must Have) and Nice to Have (maybe Qualifications/Skills). We could split: Requirements (Must Have) and Qualifications (Nice to Have) or Skills. - Skills: maybe we can put Nice to Have as Skills. - Benefits: as above. - Pay: as above. - Schedule: as above. - About MiniMed: company overview. We must not repeat job title as heading. The job title is "AI Engineer Intern". Not used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO etc. At the end there is a long EEO statement; we must remove that. Also the "Physical Job Requirements" maybe borderline but we can remove as it's generic. Also remove "About MiniMed Benefits Overview" link etc. We'll keep the About MiniMed paragraph. Also remove "MiniMed Benefits Overview" line? Actually there is a line: "For further details about our comprehensive benefits, we encourage you to visit the link below. About MiniMed MiniMed Benefits Overview". That's just a link reference; we can remove. Also remove "It is the policy of MiniMed to provide equal employment opportunity (EEO)..." etc. Remove all that. Also remove "Please note that “regular employees” refers to those who are not temporary staff, such as interns, and some benefits may not apply to employees in Puerto Rico." That's part of benefits but maybe we keep? It's a clarification about benefits not applying to interns. Might be relevant but it's a note. Could keep but it's not filler. However it's a clarification that some benefits may not apply to interns. Might be worth keeping as part of Benefits section? But we already have Benefits section describing regular employees; we could note that interns may not be eligible for some benefits. The posting says: "Regular employees working 20 or more hours per week are eligible for a robust benefits package..." then later "Please note that “regular employees” refers to those who are not temporary staff, such as interns, and some benefits may not apply to employees in Puerto Rico." So we should include that note maybe as a

  after benefits list. Also note: "Compensation and benefits information pertains solely to candidates hired within the United States (local market compensation and benefits will apply for others)." Keep that. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  We anticipate the application window for this opening will close on 16 Oct 2026.

  About the role

  Join MiniMed for a summer internship where you’ll do meaningful work, gain hands-on experience, and make an impact on our mission to make every day a better day for people with diabetes. You’ll be part of a collaborative intern community, build your professional network, and gain exposure to opportunities that help you grow both personally and professionally. Our summer internships are full-time (40 hours/week), paid positions lasting 10-11 weeks. We offer competitive compensation, educational and social programming throughout the summer, as well as housing assistance and relocation support for eligible interns.

  Responsibilities

  As an AI Engineer Intern, you'll be embedded within MiniMed's AI & Data Science team, working at the intersection of cutting-edge AI technology and real-world business impact. This is a hands-on, build-and-ship role, not a research or observation role. You'll own a scoped project from problem definition to prototype development and evaluation, partnering with technical teams and business stakeholders to deliver measurable business value. Your work will span two of our core AI focus areas:

  • AI Agents and Tools: Design, build, and evaluate LLM-powered agents on our MIA stack. You’ll work with industry-standard technologies, including AWS Services, Databricks and LangGraph, to develop reliable solutions for real business needs.
  • Enterprise AI Enablement: Help expand self-service AI adoption across the enterprise by building and deploying reusable agents and function-specific skills. You’ll empower teams to apply AI in their day-to-day workflows and improve how