Real, anonymous reports from people who interviewed for Software Engineer at Nagarro, newest first and distilled into what to expect across the loop.
My process felt unusually tough right from the start. The aptitude portion stood out as something different from what I’d seen elsewhere—hard, time-consuming questions that really ate into the time I had. After that, the coding round was also difficult, and the problems were scenario-based, which made it harder to just jump straight into standard patterns.
My Nagarro interview kicked off with an online assessment. It was structured as a first round test where I had to work through five coding questions, and that was the main gate to the next step. After I qualified, I moved into a technical discussion stage, and it felt pretty focused on testing-related questions.
The interview process typically begins with an online assessment that includes a mix of aptitude questions and coding challenges, often under tight time constraints. Candidates reported that this initial round can be quite demanding, with some feeling that the time pressure significantly impacted their performance.
Candidates generally experience multiple technical interviews that focus on practical coding skills and core concepts, with questions often centered around data structures, algorithms, and system design. The difficulty varies, but many found the questions to be scenario-based and requiring deeper reasoning rather than just rote memorization.
The final stages usually include an HR round that covers cultural fit, company policies, and career aspirations, often following the technical discussions. Candidates noted that this part of the process was less technical and more focused on personal experiences and alignment with the company values.
Candidates expressed concerns about the communication from recruiters and interviewers, with some feeling left in limbo due to a lack of timely feedback or updates throughout the process. This aspect significantly affected their overall experience, leading to feelings of frustration and unprofessionalism.
The pacing of the interview process can vary, with some candidates experiencing a fast and structured flow while others felt overwhelmed by the intensity and time demands. Generally, candidates appreciated a clear structure but noted that the pacing could lead to a stressful experience.
Many candidates did not receive offers, often reflecting on the experience as a learning opportunity despite the outcome. Common themes included the importance of preparation in core technical areas and the need for clearer communication regarding expectations and performance.