Software Engineer Intern

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about Epiq values etc. That could be "About the role" or maybe "Job Summary". The instruction: 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. 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 posting. Content: - Intro paragraph: "At Epiq, your work contributes to complex, global legal outcomes. You’ll join a values‑driven community where integrity guides decisions, relentless service sets the bar, and we thrive on big challenges together. We invest in your growth with enterprise‑wide learning and mobility. We celebrate who you are, and we respect life beyond work with flexibility that’s recognized externally. Enabled by modern platforms and AI, you’ll do the most meaningful work of your career and see your impact at scale." - Then "Job Description: Job Summary The Intern is responsible for supporting various departments within the organization by performing a range of tasks and projects. This role provides an opportunity to gain practical experience, develop professional skills, and contribute to the organization's goals. The Intern will work closely with team members to learn and assist in different areas." - Then "Essential Job Responsibilities" list: bullet points each starting with a verb. List items: 1. Supports technical tasks by providing technical support to team members. 2. Conducts research and analysis to support ongoing projects and initiatives. 3. Participates in learning and development (L&D) activities to enhance skills and knowledge. 4. Communicates effectively with team members and stakeholders to ensure smooth operations. 5. Collaborates with various departments to support cross-functional projects and tasks. 6. Maintains organized documentation and files for easy access and reference. 7. Demonstrates a proactive approach by identifying opportunities for improvement and suggesting solutions. 8. Assists in the preparation of reports and presentations to support decision-making processes. 9. Engages in professional collaboration to foster a positive and productive work environment. - Then "Qualifications & Requirements" with subheadings: Education, Experience, Skills, Certifications, Physical Requirements. Education: Currently enrolled in or recently graduated from a degree program in a relevant field. Experience: No prior experience required; previous internships or related experience is a plus. Skills: Analytical Thinking, Communication, Information Technology (IT), Interpersonal Effectiveness, Learning and Development (L&D), Proactive Approach, Professional Collaboration, Technical Support. Certifications: None required. Physical Requirements: Ability to work in an office environment and perform tasks that may require sitting, standing, and using office equipment. - Then "The Compensation range for this role is $30 - $35 hourly. This will be based on your background and skills alignment with the role." - Then "In compliance with federal law, all persons hired will be required to verify identity and eligibility to work in the United States and to complete the required employment eligibility verification form upon hire. Must be authorized to work in the United States for any employer." - Then "Your specific salary will be determined based on several factors: Location-based market rate for the roleYour abilities in relation to the job specificationPerformance during screening and interviewPay parity with the wider team in the considered location" - Then "Further details about the package will be provided during the initial screening call with the Talent Acquisition Team. Click Here To Learn About Epiq's Benefits." - Then a block about "Epiq Leadership Compass" with subheadings: Fosters Relationships & Collaboration, Engages & Influences, Maximizes Performance, Achieves Operational Success. Each with bullet points. - Then EEO statement etc. That is boilerplate to remove. We need to decide sections. We have: - About the role: could be the intro paragraph describing Epiq and the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We need to include sections only when there is real specific content. We have content for: - About the role: The intro paragraph (At Epiq...). That's substantive. - Responsibilities: The Essential Job Responsibilities list. - Qualifications & Requirements: Could be a combined section "Qualifications" or "Requirements". The posting has Education, Experience, Skills, Certifications, Physical Requirements. We could put them under a single "Qualifications" section with sub-lists? But we must use

  • for any list. Could have multiple lists under same heading? Probably okay. - Skills: Could be separate section "Skills" but we already have skills listed under Qualifications. The instruction says we can have Skills section. But we should avoid thin sections. Perhaps combine Education, Experience, Skills, Certifications, Physical Requirements into a "Qualifications" section. - Pay: The posting states compensation range $30 - $35 hourly. That's specific. So we should include a Pay section. - Benefits: The posting mentions "Further details about the package will be provided during the initial screening call with the Talent Acquisition Team. Click Here To Learn About Epiq's Benefits." That's not specific benefits; it's a link to learn more. No actual benefits listed. So we should NOT create a Benefits section because no specific benefits are stated. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we skip Benefits. - Schedule: Not mentioned. So skip. - Also there is leadership compass content: that seems like company values/competencies. Could be considered "About the role" or maybe a separate section like "Competencies". But the instruction only lists certain headings; we could add other headings if needed? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but we could also use other headings if needed? Probably better to stick to those. The leadership compass content is descriptive of company values; could be part of About the role. Thus sections: About the role (intro + leadership compass?), Responsibilities, Qualifications, Pay. We need to ensure we preserve all substantive information. Let's extract all substantive info and place appropriately. About the role: Should include the introductory paragraph about Epiq values, plus maybe the leadership compass details (Fosters Relationships & Collaboration, Engages & Influences, Maximizes Performance, Achieves Operational Success). Those are substantive and describe expectations/values. We'll include them as a list under About the role? Could be a list of bullet points. But the instruction: Use

    • for any list of duties/requirements/benefits. For About the role, it's not a list of duties/requirements/benefits, but we could still use

      for prose and maybe

      for the leadership compass items if we want. It's okay to use
      for any list; not restricted. We need to avoid duplication. Ensure we don't repeat the job title. We need to remove boilerplate: EEO statement, legal, etc. Also remove "Click Here To Learn About Epiq's Benefits." (that's a link/application instruction? It's not exactly application instruction but it's a link to benefits; we might keep it? It's not substantive benefit detail; it's just a link. Probably we should remove it as it's not substantive detail. Also remove "Further details about the package will be provided during the initial screening call with the Talent Acquisition Team." That's not specific benefit detail; it's procedural. Might be considered boilerplate? It's not EEO but it's about process. The instruction says remove application instructions. This is about screening call; could be considered application instruction. Safer to remove. Also remove "In compliance with federal law, all persons hired will be required to verify identity and eligibility to work in the United States and to complete the required employment eligibility verification form upon hire. Must be authorized to work in the United States for any employer." That's legal boilerplate; remove. Also remove "Your specific salary will be determined based on several factors: Location-based market rate for the roleYour abilities in relation to the job specificationPerformance during screening and interviewPay parity with the wider team in the considered location". That's actually more detail about pay determination; we could keep it under Pay section as it's substantive about how salary determined. It's not boilerplate; it's specific. So we keep. Also remove "The Compensation range for this role is $30 - $35 hourly. This will be based on your background and skills alignment with the role." That's pay. Now we need to format. Let's craft HTML:

      About the role

      At Epiq, your work contributes to complex, global legal outcomes. You’ll join a values‑driven community where integrity guides decisions, relentless service sets the bar, and we thrive on big challenges together. We invest in your growth with enterprise‑wide learning and mobility. We celebrate who you are, and we respect life beyond work with flexibility that’s recognized externally. Enabled by modern platforms and AI, you’ll do the most meaningful work of your career and see your impact at scale.

      Epiq Leadership Compass outlines the behaviors that drive success:

      • Fosters Relationships & Collaboration – Builds trust and alignment through open communication, shared goals, and strong partnerships to drive collective success. Build trust‑based partnerships, nurture long‑term relationships, remove collaboration barriers, celebrate cross‑team success.
      • Engages & Influences – Inspires action and alignment through clear communication, purposeful influence, and a compelling vision. Use storytelling to build buy‑in, align communication with organizational goals, guild alignment through strong engagement.
      • Maximizes Performance – Sets and reinforces performance standards that drive results, ensure accountability, and align with Epiq’s goals. Use data to identify improvement opportunities, make informed decisions, align team goals with boarder strategy, empower teams to manage their own goals, translate vision into clear priorities, prepare for disruptions with strong change management.
      • Achieves Operational Success – Drives continuous improvement and operational excellence through smart processes, data insights, and quality execution. Improve workflows for team efficiency, use clear documentation and expectations, resolve issues quickly using data and feedback.
      Then Responsibilities:

      Responsibilities

      • Supports technical tasks by providing technical support to team members.
      • Conducts research and analysis to support ongoing projects and initiatives.
      • Participates in learning and development (L&D) activities to enhance skills and knowledge.
      • Communicates effectively with team members and stakeholders to ensure smooth operations.
      • Collaborates with various departments to support cross‑functional projects and tasks.
      • Maintains organized documentation and files for easy access and reference.
      • Demonstrates a proactive approach by identifying opportunities for improvement and suggesting solutions.
      • Assists in the preparation of reports and presentations to support decision‑making processes.
      • Engages in professional collaboration to foster a positive and productive work environment