Jobs · Engineering · North Carolina

Software Engineer Internship

LexisNexis · Raleigh, NC · 1 mo ago
Engineering$22–$34/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Benefits? The posting says "This position is not eligible for benefits." So we should not create a Benefits section because it's not stating benefits; it's stating no benefits. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that it's not eligible for benefits, but that is still stating something about benefits. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about benefits (not eligible). Should we include a Benefits section? The instruction: "Prefer a few substantive sections over many thin ones." Also "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')". Here "not eligible for benefits" is specific content, not filler. So we could include a Benefits section with that statement. However they also say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (not eligible). So we can include Benefits section with that line. Pay: they have Salary Range $22-$34 per hour. So we should include Pay section. Schedule: they have Start Date, Duration, Location, Relocation assistance, Graduation Requirements. That's more like program details, not schedule per se. The rule: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can also have other headings? Probably we should stick to those headings if content matches. For program details like start date, duration, location, relocation assistance, graduation requirements - those could go under Schedule? Not exactly. Could be under "About the Internship Program" but we are told not to repeat job title as heading and not to put Job ID etc. We can create a section like "Program Details" but not in the list. The instruction says use those headings 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 for section headings (e.g...). Likely they expect us to use those headings where applicable. For program details, we could put under "About the Internship Program" but that's not in list. However we could incorporate that info into About the role or maybe a separate section like "Internship Program Details". But to be safe, we could create a section "Program Details" as a heading (

) even if not in the list? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none evident besides maybe the hashtags #AIFluent #internship and the salary line includes hashtags. We should keep substantive info. We need to preserve all substantive information. Let's extract: - About Our Team: description of LexisNexis Legal & Professional, RELX, employee count, AI leadership, technologists count, Responsible AI Principles link. - About Our Internship Program: hands-on experience, practical product and engineering work, weekly development sessions, exposure to engineers, product managers, UX, data science, customer-focused teams. Interns will learn modern development practices, including agile delivery, AI-assisted software development, secure coding, testing, observability, responsible AI use, evidence-based product iteration. - Program Details: Start Date: June 7, 2027; Duration: 11-12 weeks; Location: On-site in Raleigh, NC.; Relocation assistance: NOT provided.; Graduation Requirements: Applicants must have a graduation date AFTER June 2027 to be eligible. - About The Role: Software Engineer Intern will gain hands-on experience building software for AI-enabled legal and professional products. Work with senior engineers to learn and apply best practices in coding, testing, debugging, documentation, responsible use of AI development tools. Successful interns will contribute to product features, internal tools, APIs, reusable services, automation, prototypes that support faster experimentation and high-quality delivery. - Responsibilities: list bullet points. - Requirements: list bullet points. - About The Business: description of LexisNexis Legal & Professional services, digital pioneer, Lexis and Nexis. - Salary Range: $22-$34 per hour, depending on level of degree. #AIFluent #internship - This position is not eligible for benefits. We need to output HTML fragment with sections: maybe About the Team, About the Internship Program, Program Details, About the Role, Responsibilities, Requirements, About the Business, Pay, Benefits. But we should prefer few substantive sections over many thin ones. Could combine some: About the Team and About the Business could be merged into "About the Company". But we have headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the Team or About the Business. However we could still include them as sections if they have substantive content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include sections for About the Team, About the Internship Program, Program Details, About the Role, About the Business, Pay, Benefits, Responsibilities, Requirements. That's many sections but each has substantive content. We need to use
  • for any list of duties/requirements/benefits. So Responsibilities and Requirements become lists. Benefits: we have a statement "This position is not eligible for benefits." That's not a list but could be a

    . Could also be a list with one item but better as

    . Pay: we have salary range; could be

    . Schedule: we have program details (start date, duration, location, relocation assistance, graduation requirements). Could be a

      list. We must not repeat the job title as a heading. The job title is "Software Engineer Intern". Not used. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment, no /, no markdown fences. Let's craft:

      About the Team

      LexisNexis Legal & Professional serves customers in more than 150 countries with 11,800 employees worldwide and is part of RELX, a global provider of information-based analytics and decision tools for professional and business customers. The company has been a long-time leader in deploying AI and advanced technologies to the legal market to improve productivity and transform the overall business and practice of law, deploying ethical and powerful generative AI solutions with a flexible, multi-model approach that prioritizes using the best model from today’s top model creators for each individual legal use case. The company employs over 2,000 technologists, data scientists, and experts to develop, test, and validate solutions in line with RELX Responsible AI Principles (https://stories.relx.com/responsible-ai-principles/index.html).

      About the Internship Program

      Our internships provide hands-on experience through practical product and engineering work, weekly development sessions, and exposure to engineers, product managers, UX, data science, and customer-focused teams. Interns will learn modern development practices, including agile delivery, AI-assisted software development, secure coding, testing, observability, responsible AI use, and evidence-based product iteration.

      Program Details

      • Start Date: June 7, 2027
      • Duration: 11-12 weeks
      • Location: On-site in Raleigh, NC
      • Relocation assistance: NOT provided
      • Graduation Requirements: Applicants must have a graduation date AFTER June 2027 to be eligible for consideration

      About the Role

      The Software Engineer Intern will gain hands-on experience building software for AI-enabled legal and professional products. The intern will work with senior engineers to learn and apply best practices in coding, testing, debugging, documentation, and the responsible use of AI development tools. Successful interns will contribute to product features, internal tools, APIs, reusable services, automation, and prototypes that support faster experimentation and high-quality delivery.

      Responsibilities

      • Collaborate with engineering, product, UX, and data science team members to design and develop software solutions.
      • Develop high-quality, well-structured code for web applications, APIs, services, product integrations, and internal engineering tools.
      • Use AI-assisted development tools responsibly to prototype, document, test, and improve code while validating outputs through human review.
      • Participate in code reviews and provide constructive feedback on readability, reliability, security, accessibility, and maintainability.
      • Assist in troubleshooting software issues, writing tests, improving observability, and resolving defects.
      • Contribute to AI-enabled product capabilities such as workflow automation, tool orchestration, evaluation harnesses, telemetry, and reusable platform components.
      • Document software designs, technical decisions, experiment results, and development processes so work can be reused by global teams.

      Requirements

      • Be a currently enrolled student pursuing a degree in computer science, engineering, computer engineering, or a related field of study.
      • Demonstrate programming fundamentals in languages such as Java, Python, C++, JavaScript, or TypeScript.
      • Be familiar with software development methodologies, Git, testing practices, APIs, cloud concepts, and collaborative development tools.
      • Demonstrate AI fluency or curiosity, including awareness of generative AI, large language models, prompt patterns, model limitations, and responsible AI practices.
      • Demonstrate effective problem-solving, critical-thinking, verbal, and written communication skills.
      • Be detail-oriented and able to work both independently and collaboratively with others.
      • Demonstrate an interest in learning, experimentation, and staying current with software engineering and AI-enabled development trends.

      About the Business

      LexisNexis Legal & Professional® provides legal, regulatory, and business information and analytics that help customers increase their productivity, improve decision-making, achieve better outcomes, and advance the rule of law around the world. As a digital pioneer, the company was the first to bring legal and business information online with its Lexis® and Nexis® services.

      Pay

      Salary Range: $22-$34 per hour, depending on the level of the degree.

      Benefits

      This position is not eligible for benefits.

      We should ensure no extra whitespace at start/end. Output only HTML. Check for any duplicated lines: none. Check for boilerplate: we removed hashtags? The salary line had #AIFluent #internship. Should we keep? It's not substantive; it's likely a tag for internal tracking. Could be considered boilerplate? It's not navigation/legal/EEO. It's a tag but could be considered metadata. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Hashtags are not

Similar jobs