Feb 17, 2015
Nagarro Response
11yThank you for taking the time to leave a review here on Glassdoor. And I apologize for taking such a long time respond to it. I was working on investigating some of the points that you have raised in this review. Let me try to answer the points that you raise - some are things that we can start improving right away, others will take longer.
Regarding the salaries received by fresh recruits out of college who join in the Quality Assurance track, we do not have the lowest offers in the industry; nor do we have the highest. But of the companies that we studied, we have the highest annual raise for this track.
The industry trends also drive the disparity between QA and dev salaries - which is also driven by what in general clients pay for these two different services. Having said that, with more automation and advanced QA services, this gap is bound to reduce over time.
Nagarro does have a vision for testing - in the last two quarters, we have creating 3 different acceleration programs specifically for people in the Quality Assurance tracks. One Vice President and one Director are responsible for ensuring that our Quality Assurance services continue to evolve and become one of our strongest offerings. Having said that, it is an incomplete picture that you have when you say that we don't have testing projects. We have dedicated "testing-only" teams for a number of our larger customers - these teams are pushing the boundaries for automation testing as well - focusing on areas such as mobile testing, data quality testing, and performance testing for complex cloud deployment scenarios.
With regards to CTC structure, as you know now, we have made changes to it. We no longer have a retention bonus component, and nor is leave encashment part of the CTC.
In general, our work environment is not that taxing - on average, we spend less than 45 hours a week in office. Having said that, it is the nature of the industry that we work in where there will sometimes be peaks in our work.
From an interaction within teams perspective, we do focus a lot on respect for each other. We focus on a flat organization, and yes, there shouldn't be a sir-ma'am culture. There isn't - we don't want it. But, I concede, we do need to do a more proactive job of rooting it out.
Most people are allocated to projects where the skills that they are good at can be employed. If we didn't do that, it would be very counter-productive for us. However, there will be times when someone is deployed in a project where they either need to only use a subset of their skills or sometimes have to develop new skills. We do need to do a better job of communicating and explaining the context of project assignments to people so that they can understand better why they are assigned to a certain project - this is something that we are working on.
Overall, I believe that the situation is not as bad as you think it is. However, there are areas that we can improve and we are improving. At the end of the day, because you feel this way, it is a failure on our part nevertheless. And this means that we have to work harder so that such experiences are not taking place within Nagarro - and we will.
Let me thank you again to take the time to write a review here.
