Real, anonymous reports from people who interviewed for Software Engineer at The Nielsen, newest first and distilled into what to expect across the loop.
After a resume-driven start, I got pulled into a fairly standard sequence of technical rounds. The process felt mostly centered on fundamentals and practical problem solving rather than anything exotic. I remember one coding question that leaned on a hash map approach, and then the later part of the technical portion shifted into core CS topics across operating systems, computer networks, and DBMS.
I went through a two-round technical process that was heavily tied to data engineering. For the first round, I discussed my current project and system design around data pipelines, including the kind of questions that come up for orchestration and processing flows. I also got some PySpark-focused questions, and the overall tone was grounded in real work I had already been doing.
The interview process typically starts with a recruiter call followed by a series of technical rounds, often including a BarRaiser-style assessment. Candidates noted variations in the structure, with some experiencing a more streamlined process while others faced disorganization and scheduling issues.
Candidates encountered a mix of coding questions focused on data structures and algorithms (DSA), system design, and core computer science concepts, such as operating systems and databases. The difficulty varied, but many found the assessments to emphasize practical problem-solving over theoretical knowledge.
Live coding sessions were a significant part of the interviews, requiring candidates to explain their thought process while coding in real-time. This format added pressure, as candidates had to balance reasoning and implementation under time constraints.
Interviews included behavioral questions aimed at assessing cultural fit and collaboration skills, often focusing on past experiences and decision-making processes. Candidates reported that these discussions were generally constructive and less stressful.
Candidates expressed frustration with the communication and feedback process, citing issues with scheduling, lack of updates, and unclear outcomes after interviews. Many felt that better communication could have improved their overall experience.
Most candidates did not receive offers, and many reflected on their experiences as being demanding yet fair. Common takeaways included the need for better preparation in certain areas and the importance of aligning interview questions with their backgrounds.
