Full-Stack Developer
Interview Date
Not Specified (Implied recent, from 2025 article)
Result
Selected
Difficulty
Medium
Rounds
4 rounds
Drive Type
On-Campus
Topics asked
Detailed experience
College: Not Specified (On-Campus)
Interview Date: Not Specified (Implied recent, from 2025 article)
Interview Type: On-Campus
Result: Selected
Difficulty: Medium
Rounds: 4 rounds
Topics Asked: Aptitude, Coding (String, Sorting), Behavioral, Projects (Deep Learning), SQL (Constraints, Joins), OOPS (Polymorphism, Abstraction), Data Structures (Arrays vs Linked Lists), Puzzles (Water Jug), Networks (Protocols), Front-end, Python (Backend)
NielsenIQ visited the campus for a Full-Stack Developer role, with around 500 students applying.
This round consisted of 30 aptitude questions to be solved in 30 minutes. The questions were generally easy and covered topics like work and time, percentage, ratio proportions, data interpretations, and verbal and logical reasoning.
This round had 3 coding questions. One was a string-based question, and another involved sorting techniques. The candidate was asked to explain and optimize the code after solving the questions.
The interviewer asked questions about the code written in the previous round, including optimization. Simple coding questions were given on-screen to solve and explain the output. Behavioral questions were also asked, along with discussions about deep learning projects (if any). Questions included: "Have you ever faced conflicts with your teammates? If so how did you try to resolve them?" and "If you are given any other role other than the one mentioned in the job description, will you be able to work?"
This round started with a self-introduction, followed by a smooth conversation about internships and projects. Technical questions covered SQL (constraints, check constraints, joins), OOPS (explain, static vs. run-time polymorphism, function overloading with same name/parameters/return type), Data Structures (difference between arrays and linked lists, how linked lists are better). A puzzle was asked: "Measure 4L using a 3L and 5L bucket." Network protocols were also discussed. Behavioral questions included "Why NielsenIQ?", "What do you prefer, a job or higher education?", and "What are your plans for the future?". The candidate also shared their GitHub profile link.
12 students were selected, and the candidate was among them.