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.
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.
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 was more technical than I expected for an early step. It included MCQs focused on the tech stack, with questions spanning things like Java, Kubernetes, and Linux.
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.
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.
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.
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.
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.