Nagarro Software Engineer candidates report mixed online assessments, technical interviews on projects and engineering fundamentals, and occasional HR or managerial follow-up.
$96K
Avg. Base Comp
$109K
Avg. Total Comp
2-3 rounds
Typical Rounds
5-60 days
Process Length
Nagarro Software Engineer reports point to a mixed-format assessment as a common early screen. Candidates described online tests that combined coding or DSA with SQL, Java or framework questions, aptitude, and reasoning. The assessments varied in length and structure, but several accounts describe dense, multi-section formats, so practice moving between question types while keeping enough time to review your work.
Technical discussions often start with your projects. Prepare a clear account of the implementation choices you made, the tradeoffs involved, and the results of recent contributions. Java-focused reports include Java 8, multithreading, Spring Boot, REST APIs, SQL, and design principles. Backend candidates also reported questions about microservices concepts and inter-service communication, including choosing an approach for an e-commerce design scenario.
Problem solving may be conversational or live. Reported prompts include 3 Sum, moving zeroes, finding the kth-largest element with a heap, string manipulation, and linked-list problems. Explain the approach, time and space complexity, and a reasonable alternative. Some candidates were also asked to optimize code from an earlier assessment. HR or techno-managerial follow-up appeared in some accounts, while others described different sequences, so treat the order as variable across roles and seniority.
Synthesized from 9 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.
I cold-mailed their fresher hiring address and got a response within 3-4 days, which was encouraging. The first round was an online assessment covering aptitude, DSA, and core CS fundamentals — took roughly an hour, and I felt reasonably confident going through it.
Then came the technical interview, and they ramped up the difficulty significantly. They asked hard DSA questions focused on dynamic programming and graph algorithms, the kind that require solid problem-solving skills under time pressure. They also dug into my JavaScript background and projects, asking me to walk through my code and reasoning. There was even a system design question about building a login system for something like Amazon.
I actually did pretty well discussing my development experience and projects — that part felt natural and I could articulate my decisions clearly. But those DSA problems, especially the DP and graph questions, really got me. The difficulty level was higher than I'd prepped for, and the timed constraint made it harder to think through cleanly.
Didn't get the offer. The main thing I took away is that they weight those algorithmic problems pretty heavily in the evaluation, and if you can't solve them efficiently, it's tough to advance even if your project work and development skills are strong.
Prep tip from this candidate
Prepare specifically for hard DP and graph algorithm problems in the technical rounds — that's the main difficulty. Project experience won't carry you if you can't solve those problems efficiently under time pressure.
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 | |
| Move Zeros Back | |
| Concurrent LLM Serving | |
| Check Matching Parentheses | |
| Cloud-Agnostic Deployments | |
| The Pirate’s Hunt | |
| Three Indexes Adding Zero | |
| Blob Indexing | |
| Relational Migration | |
| Singly Linked List | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Find the Missing Number | |
| Largest Salary by Department | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Size of Joins | |
| Raining in Seattle |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates reported an online assessment early in the process. Formats differed by role, but accounts included coding or DSA, SQL, Java or framework questions, debugging, aptitude, and reasoning. One Software Engineer candidate reported two 75-minute sections, with three DSA questions in the coding section.
Technical interviews commonly focused on project decisions and core engineering knowledge. Java-oriented reports mentioned Java 8, concurrency, Spring Boot, SQL, and design principles. Candidates also reported explaining DSA approaches or completing coding prompts involving arrays, heaps, strings, or linked lists.
Some candidates reported an HR or techno-managerial conversation after technical evaluation. These discussions covered current-project contributions, role experience, and system or microservices tradeoffs. Other reports describe different sequences, so the final follow-up should not be treated as universal.
