LexisNexis Legal & Professional logo
LexisNexis Legal & ProfessionalSoftware Engineer
Updated Feb 11, 2026

LexisNexis Legal & Professional Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at LexisNexis Legal & Professional, newest first and distilled into what to expect across the loop.

Get your personalized LexisNexis Legal & Professional Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
7 months ago
Average Neutral Paris

I had a pretty standard two-part interview flow. First I met with a partner firm, and then I went into a second round with the next level of interviewers—people at N+1 and N+2.

The questions were classic and pretty company-focused. We talked about what I knew about the organization, why I wanted to be there, and how I saw myself projecting into the company over the next three to five years. Even though it stayed high-level, it felt like they were checking motivation and long-term fit more than digging into complex technical problem-solving.
8 months ago
Difficult Neutral United States

My interview route went through a vendor company, and the overall setup felt a bit off from the start. The session itself was challenging in a very specific way: they asked how I would design things like Google Docs, and we talked through implementing functions such as update and delete.

I remember walking away feeling underprepared because I didn’t really know what to expect from the interview. On top of that, the experience was already tense because they had flaked on me once before, so the uncertainty carried into the technical conversation.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Flow

The interview process typically follows a structured flow starting with an HR screening, followed by technical assessments and multiple interviews with varying levels of management. Candidates can expect a mix of behavioral and technical discussions across these rounds, often culminating in a panel interview.

HR screeningTechnical assessmentPanel interview

Behavioral Focus

Many interviews emphasize behavioral questions to assess cultural fit and motivation, often intertwining these with discussions about the candidate's resume and past experiences. Candidates should prepare to articulate their career path and how it aligns with the company's values.

Behavioral questionsCultural fitResume discussion

Technical Assessment Expectations

Technical assessments can vary, with some candidates experiencing coding challenges while others focus on discussing technical concepts related to their past projects. Familiarity with core programming principles and specific technologies like C#, Java, and SQL is often tested.

Coding challengesTechnical conceptsCore principles

Communication & Clarity

Candidates reported varying levels of communication throughout the process, with some experiencing delays and lack of clarity regarding next steps or interview formats. It's advisable to seek clarification on expectations and follow up if communication seems lacking.

CommunicationClarityFollow-up

Interview Environment & Tone

The tone of interviews can significantly impact the experience, with some candidates noting a friendly and conversational atmosphere while others encountered hostility or disorganization. Candidates should be prepared for varying dynamics and focus on maintaining composure.

Interview toneFriendly atmosphereProfessionalism

Timeline & Decision Process

The overall timeline for the interview process can extend from a few weeks to several months, with candidates often experiencing delays in receiving feedback or decisions. Understanding that the process may take time can help manage expectations.

TimelineDecision processFeedback delays