Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. Ho sostenuto un colloquio presso Nagarro nel mese di nov 2025
Nessuna offerta
Esperienza negativa
Colloquio nella media
Candidatura
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Nagarro (Bengaluru) nel mese di mag 2025
Colloquio
The process began with an online aptitude test on Mettl. Once I cleared that, I was scheduled for two technical interview rounds. The technical discussions were fairly standard, covering both technical knowledge and practical problem-solving.
However, after completing the two rounds, I did not receive any update from HR. Instead, I unexpectedly received another Mettl test link for a different client under the same company, which I also cleared successfully. Despite this, no further interviews were scheduled.
I tried following up multiple times with the HR team, but there was no proper communication or clarity provided. It has now been around 45–50 days since my interviews, and I still haven’t received any final update.
Overall, the lack of transparency and follow-up from HR was very disappointing. For a company of this scale, one would expect a more professional and candidate-friendly hiring process. Based on my experience, I would not recommend this interview process as it leaves candidates hanging without closure, even after investing significant time and effort.
Domande di colloquio [4]
Domanda 1
Imagine you are working on an e-commerce product where the user flow involves browsing products, adding them to the cart, proceeding to checkout, placing an order, and tracking the order. You are required to design an automation testing framework from scratch. How would you approach this? Please explain your test plan, test strategy, the steps involved in building the automation framework, the ROI expected from the framework, your plan for API testing, how you would leverage tools like TDCI, and finally, how you would ensure end-to-end testing across the entire lifecycle.
Suppose I have deployed my product to production. For the first 24 hours, everything runs smoothly. After that, users start reporting performance issues — for example, they say the site is slow. When I check the system metrics and dashboards, I notice memory usage is steadily increasing. Clearly, something is wrong, though the exact issue is not well defined. What would be your root cause analysis approach to identify the real problem?
Suppose you need to test the analysis logic of an API. For example, there is a product-inventory API that returns large datasets (say 5,000–7,000 records), including fields like price values. You need to validate these values with assertions. How would you approach testing this API and what strategy would you use to put assertions effectively?
After the OA, the interview was scheduled through third party. Nagarro team provides a checklist of areas to brush up. The interview itself was started 10 min late by the panel. It started off with testing my programming skills but nowhere related to the QA level. If I had to have the implementation speed, logic building of that as a developer, I might as well go into software development. But I attempted anyway and interviewer was guiding to build logic (which was the only good thing in the interview).
Then the question moved to how tests are managed, he was not clear in his questions, I was not able to understand him and convince about my automations. Overall very weird experience interviewing with Nagarro.
Domande di colloquio [1]
Domanda 1
input is array number, output should be its words; sub array left - right to be equal; string manupulation.
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto un giorno. Ho sostenuto un colloquio presso Nagarro (Poona) nel mese di lug 2019
Colloquio
The interview experience was really worse. Nagarro came to Pune for hiring for Gurgaon office. The position was QA - Automation.
I went to the interview location and spared a full Sunday for them. The interview location as 30 KM far from my area where I reside. Starting was the registration process. It started with QA test. The questions were related to manual and automation. The test was of intermediate level.
I have cleared the test. Next was the technical interview. Only one QA personnel has been invited for all the candidates. I waited for my turn to come and after 3 hours, I was been interviewed. He was having headphones in his ears and was busy in watching India cricket match. He asked me to write programs and did not check whether it is correct or not. Just asked me the skill set which I carry and noted that in his notebook. He said you are selected and the result is positive, please have a discussion with HR for further rounds.
Last round was about taking important details from me. I gave all the required information. He said HR will contact you tomorrow. I did not get any call from HR and when I contacted her, she said: "I have to check, Maybe the positions are on hold". This behavior was really insane. How can the positions be on hold in just a day? How can one announce a walk-in drive in another city and that too when they are unsure about positions. Really the experience with Nagarro was pathetic.
I would request the HR of Nagarro not to waste anyone's time. Candidates put aspirations and you just send a mail saying "the positions are on hold". Kindly don't announce a walk-in drive before you are sure that you have an ample number of positions in hand.
Domande di colloquio [1]
Domanda 1
1. Smoke testing.
2. Fine prime numbers between 50 and 100
3. A flow in which had to connect to the database.
4. Equivalence class and boundary value analysis.
5. Overloading and Overriding.
6. Upcasting and Downcasting.
