
Candidates describe a Nagarro Software Engineer interview that usually opens with a timed online assessment, then moves to technical rounds on Java or other stack fundamentals and projects, and often ends with an HR conversation.
$88K
Avg. Base Comp
$107K
Avg. Total Comp
3-4 rounds
Typical Rounds
1-9 weeks
Process Length
Candidates describe the Nagarro Software Engineer interview as a filter that starts early. Several say the online assessment is the hardest gate: one reports 6 sections and 81 questions in 120 minutes, including four coding problems, two SQL queries and output-based MCQs, while another describes a 90-minute test with aptitude, two programming questions and a larger Angular section. Others mention SQL tasks, Java MCQs, aptitude and reasoning modules in the same sitting. Timing practice matters as much as raw skill.
Technical rounds lean on stack fundamentals and your own work. Java candidates report Java 8 features, multithreading, Spring and Spring Boot annotations, Spring Security, REST APIs, SOLID and design patterns. Microservices communication came up in one account through an e-commerce design scenario, and another candidate faced system design alongside cross-questions on projects they had built. Angular candidates report questions on pipes, services and how components share services at startup. Expect to explain project decisions, and one candidate was asked to optimize the code they had written in the assessment.
Coding questions reported are mostly array, string, hash map, linked list and heap problems, such as 3 Sum, Move Zeroes, Kth largest and linked list reversal. Some interviewers cared about reasoning more than finished code.
Process experience varies a lot. Reported timelines run from about 5 days to roughly two months, and some candidates describe slow or inconsistent communication or a role being filled mid-process. Several reports end without an offer, so treat each round as a real filter and prepare for broad coverage rather than one narrow topic.
Synthesized from 26 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Nagarro process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Nagarro
Write a SQL query that creates a cumulative distribution of the number of comments per user with bin buckets of one
| Question | |
|---|---|
| Cumulative Reset | |
| Singly Linked List | |
| Check Matching Parentheses | |
| Relational Migration | |
| Move Zeros Back | |
| Three Indexes Adding Zero | |
| Concurrent LLM Serving | |
| Cloud-Agnostic Deployments | |
| The Pirate’s Hunt | |
| Blob Indexing | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Top 3 Users | |
| Size of Joins | |
| Find the Missing Number | |
| Random SQL Sample | |
| Subscription Overlap | |
| Raining in Seattle | |
| Monthly Customer Report | |
| Duplicate Rows | |
| Largest Salary by Department | |
| Prime to N | |
| Find the First Non-Repeating Character in a String | |
| Find Bigrams | |
| Data Pipelines and Aggregation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a timed first test that mixes aptitude or reasoning with coding and, depending on the track, SQL, Java, Spring Boot or Angular questions. Reported lengths range from about 90 to 120 minutes, and several describe it as the main filter. Practice switching formats quickly.
Candidates typically describe a technical round on language and framework basics plus a walk-through of their projects. Reports mention Java 8, OOP, SOLID, SQL joins, Angular topics, and array, string or linked-list problems. Some interviews were short, and some focused on explaining the logic rather than writing code.
Some candidates report a deeper round covering microservices communication, Spring Boot, Kafka, design patterns or system design scenarios, along with discussion of their current role. The depth varies by track and interviewer, so be ready to defend your architectural choices.
Several candidates mention an HR round at the end, and one had a managerial plus technical discussion that opened with a question about finance background. Follow-up timing varies, and some report slow responses or a role being filled mid-process, so keep following up.