LexisNexis Software Engineer interviews typically mix a recruiter or hiring-manager conversation with technical rounds covering SQL, ReactJS, C#, data structures, or system design, based on five candidate reports.
$120K
Avg. Base Comp
$155K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
LexisNexis Software Engineer interviews typically start with a short recruiter or HR phone screen focused on background and motivation, followed by one or two further rounds that mix behavioral conversation with hands-on technical work. The technical bar shifts by team: one candidate worked through a two-hour session combining a ReactJS sorting exercise with SQL inner joins and C# questions, while another candidate's final round paired easy-to-medium LeetCode-style problems with a high-level system design question about building authentication for a service like Uber. One candidate found the frontend task looked simple at first before ramping up quickly, so it's worth rehearsing SQL joins and basic data-structure traversal even if the opening questions feel easy.
Not every track is heavily technical. New-grad and intern candidates describe behavioral-only rounds centered on past projects, presentations, and genuine interest in the company. One also faced an unusual palindromic-date brainteaser that the interviewer said upfront wasn't expected to be solved, so the focus was on reasoning rather than a correct answer. Hiring-manager conversations in two reports come across as informal and focused on team fit and the tech stack rather than a technical gate.
Post-interview communication is inconsistent: candidates report waits of about three weeks, slower-than-expected feedback, and in one case no follow-up at all despite a positive conversation. With only a handful of reports available, treat these patterns as a general shape of the process rather than a fixed script.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Lexisnexis process.
I went through three rounds total, starting with a phone screen where the interviewer asked me some straightforward questions about data structures and linked lists to gauge my fundamentals. It was conversational, which helped me feel at ease, though I wish I'd spent more time reviewing basic traversal patterns beforehand. The questions felt like easy LeetCode level—nothing that required advanced algorithmic thinking, but the interviewer made sure I could explain my approach clearly.
The second round was with the hiring manager, which was less technical and more about understanding my background and how I'd fit with the team. I got to ask them questions about day-to-day work and the engineering culture, which was valuable. They were genuinely interested in learning about my experience and were open to a back-and-forth conversation.
The final round brought me into a coding session with team members. I tackled a couple of problems—one or two easy-to-medium difficulty LeetCode-style questions—and then moved into a high-level system design question about implementing authentication for a service like Uber. That caught me off guard a bit because I hadn't prepped as much for design, but the team was patient and asked guiding questions rather than expecting a perfect answer off the bat. The interviewers throughout were genuinely nice and collaborative. The main frustration was the timeline after the interviews—feedback took a while to come back, so there was a period of waiting that felt a bit long. Overall though, the technical bar wasn't extraordinarily high, and the process felt like they were assessing both competence and how well I could communicate my thinking.
Prep tip from this candidate
Focus on linked list and data structure problems, especially traversal and loop-based manipulations. Be ready for a system design component—even a high-level one like authentication—so review basic design principles and don't hesitate to ask clarifying questions during that round.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Lexisnexis
Write a query to display the top three users by downloads each day
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| String Shift | |
| Comments Histogram | |
| Random SQL Sample | |
| Find the Missing Number | |
| Prime to N | |
| Rectangle Overlap | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Minimum Change | |
| Scrambled Tickets | |
| Project Pairs | |
| Integer to Roman | |
| Sum to N | |
| Total Spent on Products | |
| The Brackets Problem | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Target Indices | |
| Level Of Rain Water In 2D Terrain | |
| Triplet Counting |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report starting with a roughly 30-minute phone screen with HR or an outsourced recruiter, covering background, experience, and motivation for the role. One new-grad applicant described this stage as entirely behavioral, with standard questions like describing a time they made a mistake and no technical content. Another candidate's phone screen instead covered easy data structure questions on linked lists.
Two candidates describe a hiring-manager round framed as an informal conversation about background, the tech stack, team dynamics, and culture rather than a technical gate. One SWE Lead candidate said this stage felt collaborative and was followed by a relatively light second round on legacy code, after which the company reportedly never followed up.
Technical content varies by track. One Software Engineer candidate completed a two-hour session combining a ReactJS sorting task with C# and SQL inner-join exercises, and found the frontend task ramped up quickly after a simple start. Another worked through one or two easy-to-medium LeetCode-style problems in a coding session with team members. Practicing SQL joins and basic data-structure traversal is worthwhile preparation.
In one Software Engineer candidate's final round, the team asked a high-level system design question about building authentication for a service like Uber, offering guiding questions rather than expecting a polished answer. A separate new-grad candidate instead faced a palindromic-date brainteaser they were told upfront wasn't expected to be solved, used mainly to observe reasoning.
Turnaround after interviews is inconsistent across reports. One candidate waited about three weeks for a final answer, and another described feedback taking longer than expected. A third reported no follow-up at all after a seemingly positive hiring-manager conversation and second round. Candidates may want to follow up proactively rather than assume silence signals a final decision.
