Real, anonymous reports from people who interviewed for Software Engineer at Nielsen, newest first and distilled into what to expect across the loop.
After a recruiter touchpoint, I got pulled into a pretty classic virtual flow: an OA first, then back-to-back technical rounds. The online assessment felt like it mixed targeted problem solving with fundamentals—one question leaned on graph reasoning, and another was more DP. A few days later I did the next stage where I had to solve two DSA problems, and the rest of the time was filled with core CS topics like Computer Networks, Operating Systems, and DBMS.
My interview process was shorter but very focused on data engineering systems. I went through two rounds that both started from the angle of system design tied to the kind of pipelines I had worked on—things like data pipelines—and I also had to answer PySpark-related questions. The first round felt like it stayed close to my project context.
The interview process typically begins with an online assessment that includes data structure and algorithm (DSA) questions, often focusing on dynamic programming and fundamental concepts. Candidates should prepare for a mix of problem-solving and core CS topics like graphs, linked lists, and basic algorithms.
Following the OA, candidates undergo multiple technical interviews that assess both coding skills and system design knowledge. Expect a focus on core computer science principles, with questions often tied to previous projects and resume details.
Candidates will face behavioral interviews that explore team dynamics, leadership experiences, and situational responses. These rounds often follow technical assessments and are designed to gauge cultural fit and communication skills.
The overall difficulty of the interviews is generally medium, with a structured approach that helps candidates understand what skills are being evaluated. While the process can feel rigorous, hints may be provided during coding challenges to ease pressure.
Throughout the interviews, clear communication and the ability to explain thought processes are emphasized. Candidates should practice articulating their reasoning and connecting concepts to real-world applications, especially during system design discussions.
Candidates often receive feedback on their performance, which can help clarify areas for improvement even if they do not receive an offer. The interview process is described as fair, but some candidates express disappointment with the final communication regarding outcomes.