Real, anonymous reports from people who interviewed for Software Engineer at LexisNexis Risk Solutions, newest first and distilled into what to expect across the loop.
Get your personalized LexisNexis Risk Solutions 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.
I was contacted by HR and given both the job description and a separate document that outlined what they wanted to hear—things like what I had done on my last project and why I was interested in the company. The job description itself felt a bit vague, with broad expectations that seemed to include DevOps and system-administration alongside software engineering.
Once I joined the interview call, the tone shifted immediately. The two interviewers dug into the infrastructure I’d worked on and kept cross-questioning me, repeatedly asking about tools I hadn’t used. I felt like they weren’t really hearing my answers, which made the whole conversation feel more like a grilling than a technical discussion. I left with the strong impression that the goal was to find fault rather than to evaluate what I actually brought to the table. I wasn’t offered the role afterward, and honestly the experience left me pretty frustrated because it didn’t feel aligned with how an engineering interview should run.
7 months ago
Difficult Positive Leeds, England
The most memorable part of my process was a take-home coding task. It wasn’t just a generic exercise—it was described as a continuation of an already started project, and it came with specific guidelines spelling out the goal and the precautions I had to follow.
When they reviewed my work, I ended up discussing my implementation choices in detail, along with the assumptions I made. Even though it took time, it felt fair in a way that a lot of interviews don’t: the task was applicable to the role and it tested the basic skills that would matter day to day. I didn’t end up getting the offer, but the experience felt like one of the few parts of the process that actually matched the job.
11 months ago
Average Neutral Dublin, Dublin
My process started with an HR screening where we covered the basics of the company and the role. After that, I had a pre-phone screen assessment that …
> 1 year
Average Positive Alpharetta, GA
I started with an HR call that was about 30 minutes, then I met with the hiring manager, and after that I went through a tech panel round where a fina…
> 1 year
Difficult Positive Mumbai
My process consisted of two interviews. The first one I participated in lasted over an hour and a half on Microsoft Teams, and it ended with me being …
Unlock every Software Engineer 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 & Timeline
The interview process typically starts with an HR screening followed by technical rounds, which may include phone interviews and onsite assessments. Candidates noted varying timelines, with some experiencing quick feedback while others faced prolonged waiting periods without updates.
HR screeningtechnical roundsfeedback timeline
Technical Assessments
Candidates often faced a mix of practical coding tasks and theoretical questions, with a focus on technologies like SQL, C#, and front-end frameworks such as Angular and ReactJS. The technical discussions were generally grounded in real-world applications rather than abstract algorithms.
coding tasksSQLfront-end frameworks
Behavioral & Fit Evaluation
Many interviews included behavioral questions aimed at assessing cultural fit and communication skills, with interviewers often asking about past experiences and how candidates approached various challenges. This aspect was emphasized alongside technical evaluations.
The tone of interviews varied significantly, with some candidates describing a supportive environment while others felt pressure and adversarial questioning. Experiences ranged from relaxed discussions to more intense grilling sessions, impacting overall candidate perception.
interview tonesupportive environmentpressure
Feedback & Communication
Candidates reported mixed experiences regarding feedback and communication post-interview, with some appreciating timely updates while others faced ghosting or lack of closure after interviews. This inconsistency affected overall candidate satisfaction.
feedbackcommunicationghosting
Preparation for Technical Depth
Candidates noted the importance of being well-prepared for a broad range of technical topics, including specific programming languages and tools relevant to the role. Some felt that the depth of technical questioning was higher than expected, especially in areas like PHP and SQL.
technical preparationprogramming languagesdepth of questioning