Nagarro Staff Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 72 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Nagarro.
Nagarro
Staff Software Engineer
Staff Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding
So basically, it was a virtual interview. They hit me with some Java questions, like how memory management works. Then there were some LeetCode style problems, easy to medium difficulty, like finding the largest sum of a subarray and reversing a string without using any built-in functions. Also got some questions about Spring Boot and microservices.
Confirmed questions2 questions
- Could you find the largest sum of a subarray?
- How would you reverse a string without using built-in methods?
Nagarro
Staff Software Engineer
Staff Average Positive experience Accept offer 5 rounds
Interview process
Take home Phone screen Onsite Background check Offer
Interview formats
Coding Technical System Design Behavioral
The interview process was smooth and well-organized. It started with an online coding test consisting of 2 algorithmic problems, followed by a technical phone screening. After clearing that round, I was invited for an on-site interview which had three stages: Technical Round 1: Data structures and problem-solving questions, whiteboard coding. Technical Round 2: System design and scenario-based questions. HR Discussion: Focused on cultural fit, past experiences, and future career goals. Then background check and offer.
Confirmed questions1 question
- Have you ever built a framework from scratch?
Nagarro
Staff Engineer
Staff Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral
This interview experience with Nagarro was pretty bad. The person interviewing me didn't seem to know much about Flutter, which was supposed to be the main topic. He didn't ask any good questions about Flutter or related stuff, and he was also unprofessional. It felt like he wasn't prepared and was just asking generic questions instead of checking my actual skills for the job. His behavior was really off-putting and gave me a bad impression of how Nagarro hires people. I was expecting a more professional process from them. Honestly, this experience made me question if I still want to work there. Just a thought: just because someone is a lead doesn't mean they know everything about every tech. People solve problems differently. If you don't know how BLOC works, don't argue with someone who actually has experience with it.
Confirmed questions8 questions
- What was the reason for the delay in securing your first job?
- Could you share when you finished your graduation?
- Can you describe scenarios involving Flutter BLOCs?
Nagarro Staff Software Engineer Interview Questions
Quoted word for word from Nagarro interview reports.
“What's the method for sending a document within a POST request header?”
Read reports →“What are the different types of waits in Selenium and their differences?”
Read reports →“For class-based components, what is the execution order of React lifecycle methods?”
Read reports →“For functional components, what is the execution order of React lifecycle methods?”
Read reports →“Can you explain how to perform an HTTP OPTIONS request using .NET web APIs?”
Read report →“What is the behavior of Session/Local Storage across different browser instances or tabs?”
Read report →“In Testing and Selenium, what are the different kinds of waits and their differences? Which wait is best and why?”
Read report →“Can you explain the difference between a primary key and a candidate key?”
Read report →“Could you write a gtrigger to count the number of Contacts associated with an Account?”
Read report →Formats, difficulty and experience
Across all 72 Nagarro interview reports.