Intern - Software Developer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. Key info: - Company: Labcorp - Position: Software Development Intern - Location: Durham, NC, hybrid work schedule - Work Schedule: Monday - Friday, 40hrs per week - Job Responsibilities: bullet list? It says: "Participate in software development from requirements gathering to final product on the ServiceNow ITSM Module and Platform Integrations" - Minimum Qualifications: "Current enrollment in a Bachelor’s degree program in Software Engineering" - Additional Job Standards: list: Good Communication skills, both written and verbal; Interest in IT Service Management tools and methodology; Proactive individual who is curious to learn how their work translates to user experience and operational efficiencies; Maintains professionalism, including punctuality and appropriate conduct - About The Team: description of ServiceNow development team. - About The Program: description of internship program details (learning experiences, leadership exposure, etc.) - Internship Details: Duration: 12 weeks, full-time; Dates of Internship: May 24, 2027-August 13, 2027; Compensation: Paid internship; relocation assistance available for qualified candidates; Eligibility: Preferred candidates are rising juniors and seniors (Dec 2027 through June 2029 graduation) who are currently enrolled in a relevant degree program; however, all current students pursuing related studies are encouraged to apply; This position is not eligible for visa sponsorship now or in the future. - Benefits: paragraph about benefits for employees regularly scheduled to work 20+ hours per week; interns get 401(k) only? Actually says: Employees regularly scheduled to work 20 or more hours per week are eligible for comprehensive benefits including: Medical, Dental, Vision, Life, STD/LTD, 401(k), Paid Time Off (PTO) or Flexible Time Off (FTO), Tuition Reimbursement and Employee Stock Purchase Plan. Employees regularly scheduled to work less than 20 hours, Casual, Intern, and Temporary employees are only eligible to participate in the 401(k) Plan. Thus interns (likely less than 20? but they work 40 hrs per week, so they'd be eligible for comprehensive benefits? Actually they work 40 hrs per week, so they'd be eligible for comprehensive benefits. But the text says interns are only eligible for 401(k) Plan? It says "Employees regularly scheduled to work less than 20 hours, Casual, Intern, and Temporary employees are only eligible to participate in the 401(k) Plan." However they work 40 hrs per week, so they'd be >20, thus eligible for comprehensive benefits. But ambiguous. We'll just preserve the benefit text as is. Pay: Not explicitly stated beyond "Paid internship". No specific salary. So we should NOT create a Pay section because no specific pay amount. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Paid internship" but not amount. Is that enough? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Paid internship" which is a statement about pay. However they also say "Compensation: Paid internship; relocation assistance available". That's a statement about compensation. So we could include a Pay section with that statement? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation: Paid internship. So we could include a Pay section with that content. However they also said "Prefer a few substantive sections over many thin ones." Might be better to include Benefits section (since benefits are stated) and maybe Schedule section (since work schedule stated). Pay maybe we can include as part of Benefits? But they said separate sections for Pay, Schedule, Benefits. We have schedule: Monday - Friday, 40hrs per week. So we can include Schedule section. Pay: we have "Paid internship; relocation assistance available". That's specific enough? It's not a number but it's a statement. I'd include Pay section with that sentence. Benefits: we have the benefits paragraph. Now other sections: About the role (maybe we can combine the introductory paragraph about Labcorp and the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have: - About the role: could be the introductory paragraph describing Labcorp and the role? The posting starts with Labcorp description then "Labcorp is seeking a Software Development Intern to join our ServiceNow Development Team located in Durham, NC, with the flexibility of a hybrid work schedule!" That's about the role. We'll put that in About the role. - Responsibilities: bullet list: "Participate in software development from requirements gathering to final product on the ServiceNow ITSM Module and Platform Integrations". That's one responsibility. - Requirements: maybe Minimum Qualifications? Or Additional Job Standards? The headings: Requirements vs Qualifications vs Skills. We need to decide mapping. Usually Requirements = minimum qualifications. Qualifications = preferred or additional. Skills = specific skills. We'll allocate: - Requirements: Minimum Qualifications: "Current enrollment in a Bachelor’s degree program in Software Engineering" - Qualifications: Additional Job Standards: list of communication skills, interest in ITSM, proactive, professionalism. - Skills: maybe we could list "Good Communication skills, both written and verbal" etc. But we already used those in Qualifications. Could also put them under Skills. But we need to avoid duplication. Let's think: The posting includes "Good Communication skills, both written and verbal", "Interest in IT Service Management tools and methodology", "Proactive individual who is curious to learn how their work translates to user experience and operational efficiencies.", "Maintains professionalism, including punctuality and appropriate conduct". Those are more like skills/qualities. We could put them under Skills. Then Qualifications could be empty? But we need to only include sections with real content. So we could put those under Skills. Then Requirements = Minimum Qualifications. Qualifications maybe we could put "Preferred candidates are rising juniors and seniors (Dec 2027 through June 2029 graduation) who are currently enrolled in a relevant degree program; however, all current students pursuing related studies are encouraged to apply". That's from Internship Details eligibility. That could be Qualifications. Let's see. We have eligibility info: "Preferred candidates are rising juniors and seniors (Dec 2027 through June 2029 graduation) who are currently enrolled in a relevant degree program; however, all current students pursuing related studies are encouraged to apply". That's a qualification/preference. Thus we can have: - Requirements: Minimum Qualifications: Current enrollment in a Bachelor’s degree program in Software Engineering - Qualifications: Preferred candidates are rising juniors and seniors (Dec 2027 through June 2029 graduation) who are currently enrolled in a relevant degree program; however, all current students pursuing related studies are encouraged to apply - Skills: Good Communication skills, both written and verbal; Interest in IT Service Management tools and methodology; Proactive individual who is curious to learn how their work translates to user experience and operational efficiencies.; Maintains professionalism, including punctuality and appropriate conduct But we also have "About The Team" and "About The Program". Those could be part of About the role? Or maybe we could create a separate section like "About the team" but not in allowed headings. The instruction only lists those headings; we should not create other headings. So we need to fit that content somewhere. Perhaps we can include it under About the role (expanded). Or we could put under Responsibilities? Not appropriate. Better to include under About the role a paragraph about the team and program. Thus About the role will include the introductory description, plus details about the team and program. Now Benefits: we have the benefits paragraph. Pay: we have "Paid internship; relocation assistance available for qualified candidates". Also maybe mention "Compensation: Paid internship; relocation assistance available". We'll put that. Schedule: we have "Work Schedule: Monday - Friday, 40hrs per week". Also maybe mention hybrid work schedule. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not repeat the job title as a heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the EEO paragraph, accessibility, privacy statement, etc. Also remove "Apply now to launch your career..." etc. Also remove "Join Labcorp’s 2027 Global Internship Program..." maybe that's part of About the role? It's substantive? It's about program. Could keep. But we need to avoid duplicated lines. Let's extract substantive content: - Intro paragraph about Labcorp mission etc. Might be considered boilerplate? It's generic but maybe part of About the role. We'll keep a concise version? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the exact sentences? It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, not summarizing. However we can remove boilerplate like EEO etc. The mission statement is not boilerplate; it's substantive about company. We'll keep it. But we need to avoid duplication: there are repeated sentences about "Join Labcorp’s 2027 Global Internship Program..." and later "Internship Details Duration: 12 weeks, full-time..." etc. We'll keep each unique piece. Let's compile sections: About the role: We'll combine: "Labcorp is a global leader in laboratory services, providing the insights and answers that help healthcare providers, patients, researchers, pharmaceutical companies and health systems make confident decisions and improve outcomes. Through our unparalleled science, data, technology and laboratory network, we advance diagnostics, accelerate innovation and help address some of the world’s most important health challenges. As we shape the future of healthcare, we are leveraging advanced technologies, intelligent digital solutions and data-driven innovation across our operations to enhance how work gets done and deliver greater value to customers and patients. With our global scale and deep expertise, you’ll have the opportunity to do meaningful work, grow your career and make a real impact on people’s health around the world. Together, we’re improving health and improving lives. Labcorp is seeking a Software Development Intern to join our ServiceNow Development Team located in Durham, NC, with the flexibility of a hybrid work schedule! Work Schedule: Monday - Friday, 40hrs per week" But we already have Schedule section separate, so maybe we shouldn't duplicate schedule in About the role. However the instruction says preserve ALL substantive information; we cannot remove the schedule mention if it's in the original text. But we can move it to Schedule section and not duplicate? The instruction says preserve ALL substantive information; does that mean we cannot omit any info? It says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep all info, but we can reorganize. If we move the schedule sentence to a Schedule section, we still preserve it, just not duplicated. That's okay as long as we don't lose it. However we must not duplicate. So we can include schedule sentence only in Schedule section, not also in About the role. But the original text includes it; we can relocate. That's preserving the