LexisNexis Risk Solutions logo

LexisNexis Risk Solutions Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 48 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
56.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at LexisNexis Risk Solutions.

Showing 3 of 48
LexisNexis Risk Solutions logo
LexisNexis Risk Solutions

Software Engineer

Engineering · nearly a year ago

Mid Difficult Positive experience Accept offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding Technical

Got a take-home coding task, which was basically continuing a project I'd already started. Had to meet specific goals and be careful about certain things. Then, they reviewed my work and we talked about how I did it, the choices I made, and any assumptions I had. It was one of the few interviews that actually felt relevant to the job and tested the core skills needed.

Confirmed questions1 question
  • Can you explain why you'd pick one REST API framework over a different one?
LexisNexis Risk Solutions logo
LexisNexis Risk Solutions

Software Engineer Lead

Engineering · a year ago

Lead Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Background check
Interview formats
Behavioral Technical

I applied through LinkedIn and the company website. HR from an outsourced firm contacted me for an initial screening based on the job requirements. A few days later, the hiring manager wanted to meet for an informal chat about the role and company. We had a good conversation about how my skills fit the position. I asked about company culture, tech stack, and team dynamics. The hiring manager told me the next steps and that HR would schedule more rounds. After that, I never heard back from HR. I sent emails and even reached out to the hiring manager, but got no response. They should have at least communicated the outcome.

Confirmed questions1 question
  • Can you walk me through your CV and tell me about yourself?
LexisNexis Risk Solutions logo
LexisNexis Risk Solutions

Software Engineer

Engineering · more than a year ago

Entry Easy Neutral experience No offer 2 rounds
Interview process
Phone screen Technical screen
Interview formats
Behavioral Technical

I had a phone screening and then an hour-long final round interview. It was mostly behavioral questions, with a quant brain teaser at the end. They mentioned it wasn't expected to be solved, just to see my thought process. I found the trick and was about to solve it when the interviewer cut me off, saying I was the closest candidate they'd seen. It was early in the process, and I got rejected a week later due to lack of relevant internships and not being a good fit.

Confirmed questions1 question
  • Could you discuss palindromic dates?

LexisNexis Risk Solutions Software Engineer Interview Questions

Quoted word for word from LexisNexis Risk Solutions interview reports.

How do you check disk space usage on a Linux file system using a command?

Read reports

What is the most efficient sorting algorithm in O notation?

Read reports

How would you write a SQL query to retrieve the top N results, incorporating window functions?

Read reports

Could you explain the reasons for using object-oriented programming?

Read report

Can you explain your technical understanding of SQL JOINs and its variations?

Read report

Can you explain why you'd pick one REST API framework over a different one?

Read report

Can you do a whiteboarding exercise to code the OOP example you mentioned?

Read report

Formats, difficulty and experience

Across all 48 LexisNexis Risk Solutions interview reports.

Interview formats

Technical 45.6%
Behavioral 35.9%
Coding 15.5%
System Design 1%
Presentation 1%

Interview difficulty

Easy 33.3%
Average 60.4%
Difficult 6.2%

Candidate experience

Positive 56.2%
Neutral 27.1%
Negative 16.7%