Intern – Network Infrastructure & Automation Engineering

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 only include sections where posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key info: - Company: Labcorp - Position: Network Infrastructure & Automation Engineering Intern - Location: Durham, NC with hybrid work schedule - Work Schedule: Monday - Friday, 40hrs per week - Job Responsibilities: list bullet points (many) - Minimum Qualifications: Current enrollment in a Bachelor's degree program in Computer Science, Information Technology, Computer Engineering, Network Engineering, Information Systems or Electrical/Computer Engineering - Preferred Qualifications: 3-6 months experience in TCP/IP networking, Routing and switching, Linux; 3-6 months experience in Python; 3-6 months experience in Automation or scripting, APIs; 3-6 months experience in Cloud computing, Cybersecurity; 3-6 months experience in Git or source control - Additional Job Standards: list of technologies you may work with/learn: Data Center Networking - Arista EOS, CloudVision as a Service, Arista AVD, ANTA, and DMF; Application Delivery - NetScaler VPX, NetScaler Console, and Venafi certificate management; Core Network Services - Infoblox NIOS, DNS, DHCP, IPAM/DDI, public DNS, internal DNS, NTP, and enterprise integrations; Automation & DevOps - Ansible, Bitbucket, Linux, APIs, Infrastructure-as-Code, Network-as-Code, and automated validation; Observability - ExtraHop and network telemetry/analytics platforms; Work directly with senior network and infrastructure engineers; Participate in architecture and design discussions; Learn how engineers troubleshoot complex production issues; Understand enterprise change-management practices; Receive code and configuration reviews; Learn how technical decisions are communicated to leadership; Develop technical documentation and presentation skills; Explore different career paths within networking, automation, cloud, security, and infrastructure engineering; Example summer projects: Network Automation, Automated Network Validation, Infrastructure Health Dashboard, Configuration Compliance, DNS / DHCP Automation, Network Observability, Infrastructure-as-Code Lab - About The Team: description - About The Program: description - 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: 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. For more detailed information, please click here. (We need to include benefits section if posting actually states them. Yes, they have benefits description. So include Benefits heading.) - Pay: Not explicitly stated beyond "Paid internship". No specific pay amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, we have only "Paid internship" but no amount. Is that considered stating pay? It says "Compensation: Paid internship; relocation assistance available for qualified candidates". That's a statement that it's paid but no amount. The rule says: 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. "Paid internship" is not a specific amount, but it's stating that it's paid. Is that considered filler? It's not a specific number, but it's stating that compensation is paid. Might be considered not specific enough. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Paid internship". So we could include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to combine Pay into Internship Details or Compensation. But we have separate headings allowed: Pay, Schedule, Benefits. We already have Schedule (they gave Monday-Friday 40hrs). So we can include Schedule section. For Pay, we could include a short

stating "Paid internship; relocation assistance available for qualified candidates." That is substantive enough? It's not a number but it's info. I'd include Pay section. - Benefits: we have details. - About the role: maybe we can have an "About the role" section summarizing the role description at top: "Labcorp is seeking a Network Infrastructure & Automation Engineering Intern to join our Enterprise Infrastructure team located in Durham, NC with the flexibility of a hybrid work schedule!" That's substantive. Could be About the role. - Responsibilities: we have list of job responsibilities bullet points. - Requirements: maybe Minimum Qualifications. - Qualifications: maybe Preferred Qualifications. - Skills: maybe Additional Job Standards (technologies) could be Skills. But we need to avoid duplication. Let's decide sections: - About the role (short paragraph) - Responsibilities (ul list) - Requirements (Minimum Qualifications) - Preferred Qualifications (maybe as Qualifications) - Skills (Additional Job Standards list) - Benefits (ul list) - Pay (p) - Schedule (p) We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, privacy, accessibility, etc. Also remove "Apply now..." etc. Also remove "Join Labcorp’s 2027 Global Internship Program..." maybe that's part of About the Program? Actually that is part of About The Program? The posting includes: "Join Labcorp’s 2027 Global Internship Program and take the first step toward a meaningful career in healthcare innovation! We’re looking for motivated students to be part of a dynamic 12-week paid internship where you’ll work on impactful projects and gain real-world experience, all while supporting our mission to improve health and improve lives. Internship 2027 Dates: May 24, 2027-August 13, 2027 About The Team ..." That seems like introductory fluff. Could be part of About the role or About the Program. We'll incorporate relevant info into About the role or About the Program. We need to preserve all substantive information. So we need to keep details about program: 12-week paid internship, dates, relocation assistance, eligibility, etc. Those we already have in Internship Details section. We also have About The Team and About The Program sections. Those are substantive. Should we include them as separate sections? The allowed headings list does not include "About The Team" or "About The Program". But we could incorporate their content into existing sections like About the role or maybe we could create a section "About the team" but not in allowed list. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should stick to those headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. So we need to fit About The Team and About The Program content into maybe About the role or maybe we can create a section "About the role" that includes description of team and program. Or we could have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. That's it. Thus we need to distribute: - About the role: include overview of role, location, hybrid, mission, maybe mention program details (12-week paid internship, dates, relocation assistance, eligibility). Also mention that it's part of Labcorp's 2027 Global Internship Program. - Responsibilities: list of job responsibilities bullet points. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: Additional Job Standards (technologies you may work with/learn) plus maybe the bullet points about working with senior engineers, etc. Those could be considered skills/experience. - Benefits: benefits description. - Pay: compensation statement. - Schedule: work schedule. We must not include filler like "commensurate with experience". We have none. We need to ensure we don't repeat content unnecessarily. Let's extract bullet points for responsibilities: From posting: Learning how enterprise data center networks are designed and operated using Arista EOS and CloudVision-as-a-Service Exploring Infrastructure-as-Code and Network-as-Code concepts using Ansible and Arista AVD Building and testing network validation using Arista ANTA Developing scripts or automation to eliminate repetitive operational tasks Learning how application traffic is delivered through Citrix NetScaler VPX Working with enterprise DNS, DHCP, IP address management, and NTP services Exploring network telemetry, packet visibility, and analytics using platforms such as ExtraHop and Arista DMF Learning how infrastructure changes are developed, reviewed, version-controlled, tested, and deployed Working with Bitbucket, Linux, APIs, YAML, JSON, and Python-based tooling Building dashboards, reports, or automated infrastructure health checks Assisting with infrastructure documentation and operational runbooks Participating in troubleshooting exercises and root-cause analysis Learning how enterprise infrastructure integrates with security, cloud, compute, and application teams Participating in engineering design discussions and change reviews Presenting the results of your summer project to engineers and IT leadership That's a list. Minimum Qualifications: Current enrollment in a Bachelor's degree program in Computer Science, Information Technology, Computer Engineering, Network Engineering, Information Systems or Electrical/Computer Engineering Preferred Qualifications: 3-6 months experience in TCP/IP networking, Routing and switching, Linux 3-6 months experience in Python 3-6 months experience in Automation or scripting, APIs 3-6 months experience in Cloud computing, Cybersecurity 3-6 months experience in Git or source control Additional Job Standards (technologies you may work with/learn): Data Center Networking - Arista EOS, CloudVision as a Service, Arista AVD, ANTA, and DMF Application Delivery - NetScaler VPX, NetScaler Console, and Venafi certificate management Core Network Services - Infoblox NIOS, DNS, DHCP, IPAM/DDI, public DNS, internal DNS, NTP, and enterprise integrations Automation & DevOps - Ansible, Bitbucket, Linux, APIs, Infrastructure-as-Code, Network-as-Code, and automated validation Observability - ExtraHop and network telemetry/analytics platforms Work directly with senior network and infrastructure engineers Participate in architecture and design discussions Learn how engineers troubleshoot complex production issues Understand enterprise change-management practices Receive code and configuration reviews Learn how technical decisions are communicated to leadership Develop technical documentation and presentation skills Explore different career paths within networking, automation, cloud, security, and infrastructure engineering Example summer projects: Network Automation, Automated Network Validation, Infrastructure Health Dashboard, Configuration Compliance, DNS / DHCP Automation, Network Observability,