Netcracker Technology reviews

1. Work can start even if proper trainings is not provided or done. 2. Sometimes, no proper documentation is found to speed up your work. 3. No domain learning. No end to end customer requirement/solution is explained to you. 4. A task is assigned to you and you should finish it even if end to end customer requirement/solution is not explained to you. 5. No team bonding. 6. No rewards/recognition/bonus for extra hours put in. 7. In the Engineering Side, the ratio of non-developers to developers is like 1:2. The company has too many leaders/managers. So, no chance of career growth/promotion. Most managers are useless because they just talk/suggest nonsense and wont provide the solution and wont code also. 8. Managers/HR/Bangalore Management are puppets to senior NetCracker management. They have zero power in the company. They just say "YES" to their boss. 9. Most managers are selfish and just want their own goals to be achieved. They dont care about subordinates’ happiness or career growth. They mostly just use their subordinates for their own personal project success. 10. There are projects that has good deadlines or tight deadlines or extremely bad “mission impossible” deadlines or you might be in on bench also. This depends on your luck on which project you work for. You might be on bench for weeks/months in a worst case scenario. 11. Most work is repetitive or boring or frustrating. 12. Some Business Analysts/Managers/Architects dont know how to plan projects accurately. So, the developers will have to slog to achieve deadlines. 13. Some Business Analysts/Managers/Architects agree to impossible customer requirements blindly. So, the developers will have to slog to achieve deadlines. 14. Some Business Analysts/Managers/Architects make design defects in the design. So, the developers will have to slog to achieve deadlines. 15. If deadlines are missed or if the tasks are not achieved, then the developer is blamed for it. 16. You are compared to the smartest Russian developers who are well trained and skilled and it is almost impossible to compete with them. Negative Feedback given by the manager is hidden from the developer. This is not debatable and the feedback is final. 17. If you have negative feedback from company for 2-3 projects, then the company will make you leave within less than a week. No job security. 18. You are expendable to the company if you are not assigned to any project. 19. For every project that you work on, you are reevaluated on performance and a feedback is given. 20. Before joining any project, there is an interview. If you fail it, then you cant join the project. 21. Because of the interview process, you can never improve your programming language skill set also. 22. This company is not suitable for 9:00 A.M. to 5:30 P.M. people. Be prepared to work extra hours into the night also to sync up with the Russian/Ukrainian time zone. 23. Most of the working days does not have work life balance. 24. Salary is just average but not great. 25. 90% of things that you learn in NetCracker is useless once you leave the company. 26. Since, there is no domain knowledge gained, no new language skills learned and no promotions/career growth, you are the exact same person when you join and leave the company. It is really really hard to crack any job interview. 27. Irrespective of your job title, whether you have 2 or 5 or 10 or 15 or 20 years IT experience, if the company wants you to code, then you have to code. You will be evaluated in it and a feedback will be given on it. 28. Irrespective of your job title or promotion, you will still continue to work as a developer and there will be no subordinates reporting to you but only additional extra expectations by manager on faster delivery dates. Your job title has zero value in the company. 29. There is many projects which has micro management on every task and sub-task. So, there will be daily tasks (sometimes with impossible deadlines) that has to be met everyday. 30. There is even micro management to even how the code is written based on some imaginary guidelines. You will be wasting time by reworking code thousands of times just to please some people and still, you might get negative feedback as they will claim you wrote the stupid code in the 1st place. 31. The company is not meant for average and below average developers. This company is meant for the selfish lone wolf who is an extremely smart coder and who is here not to make friends but to solve problems. 32. This company is not meant for fun/friends/culture but only for true professionalism in work. 33. There is no forum in NetCracker to address your concerns. 34. Zero clue as how appraisals/ratings/hikes/promotions are decided. Looks like a lottery ticket or must be Rock-paper-scissors game. 35. To get faster access to information or to get work done faster, it is good if you knew Russian. 36. Almost all the lead/managers positions available for projects in NetCracker Bangalore Office are given to Russians either from Bangalore Office or Russian Office. So basically, the lead/manager positions are taken by Russians and the Bangalore office is just stuck with the coding development. So, basically, lack of job growth opportunity irrespective of whether your job title deserves it or not. 37. Don't be surprised if people younger than you by so many years is your lead/manager and they will have no hesitation to make you work like a slave and give negative feedback if you don't perform as per their expectations (sometimes impossible expectations). 38. You will just remain a coder forever if you stay in the company. 39. Most of the Russian leads/managers prefer to work with only Russian colleagues and they are just forced to work with Bangalore team just to please senior management. So, there is always a sense that you are working in a place/project where they actually don't want you there, so you will feel alienated in some of the projects. The delivery of your work is affected if your Russian colleagues don't chat English well. 40. Since you jump from project to project, maybe, 3-6 projects in a year, it is hard to forge long-term permanent friendships because each new project is always a new team and most of the projects will not have time for any non-work interaction. So, basically, you become alienated even in your own company. 41. There is no reward for being a team player. So, finish your work first always because you will only rated based on your work only. Help others only if it helps in your feedback/ratings. This is the perfect company for selfish people. 42. Don't expect any reward for finishing work faster or achieving a deadline. They just assign the next task. So, if you finish the tasks faster; then you are just rewarded with more tasks. So, it is better to finish the task only on the final date. 43. 50% of the people in the engineering side wants to manage/lead a team but there is not enough developers in the company to delegate the work to or there is not enough projects in Bangalore Office. So, they have converted the extra managers/leads into developers or business analysts as a workaround. How will NetCracker deliver any solution if it does not have enough really experienced talented skilled developers (who do not want to lead/manage the team) in the NetCracker Bangalore Office? Because it is a known fact that nothing can be delivered to the customer without the developer. So, there is some useless people in the company who don't code but talk nonsense and just give orders/suggestions. So, there is some senior people (paid extremely high salaries) in NetCracker Bangalore who only talk but adds zero value in the company but just boss you around.

This company suits neither for a fresher nor an experienced java developer. I'll tell the reasons. 1. If you are hired into the firm from non-software backgrounds in engineering, such as electronics, electrical, etc, you will have a tough time getting adjusted to. They initially hire you for your c/c++ skills, but expect to work in java. For that, they give something called 'training', which is nothing but waste of time. What happens here is : the trainer writes a program on his laptop, you see it from the projector, copy it into your system, execute it , if it runs successfully, Lo! you have completed the day's training ! The rest all associated frameworks like spring, gwt, etc have to be learnt by ourselves by browsing the net. So here training serves no purpose. 2. After your training is over, you will be inducted into a project, months later. But again with an interview. The manager will ask non-answerable questions like 'why you were sitting simply months after the training was over ?', 'you had training, but you seem to be less knowledgeable on java xyz ?', etc. Man, too many interviews here to pass over every stage in the company, even if your job is confirmed. 3. They expect you to start working on the project, using their 'NC Framework'. But never an introduction is given on what the project is, it details, the current status, work done till now, where are we to start from , what is this framework, how it is works, etc. Immediately they start assigning tasks, with due dates too. You are hellbound on what to do, Absolutely no guidance, no mentorship, no tutorial, no training, no documentation on the kind of work you generally do here. You have to literally beg other senior developers who know a little to explain what is going on. They will be busy and you have to jump from one guy to the other. At last helpless, you approach the manager and explain him the situation, he'll respond 'You have to EXPLORE and learn by yourself'. This 'explore' thing doesn't work as simple. It is like telling someone to explain the relation between the characters of a movie, who has started watching it from the second half. 4. Very less java work. All job is done by the NC Framework. Rather than using it to accomplish your task, 95 % of your time will be devoted to 'exploring', analysing and inferring how the framework works, through trial and error, and fixing bugs in the framework itself ! Now, this framework is of nil value once you exit the company, because it is not generic. Even if you have some java work, that will be just editing huge classes written by someone else, before you figure out what the class is supposed to do, where you should introduce your small fix, understand the dependent sea of classes, your due date will be over. We are not supposed to write javadoc too ! 4. Next thing is they will throw assignment tickets on your head like garbage. Never an estimation of the employee's capability and experience is gauged before giving the work. A fresher who is just into the project will be given (thrown) a complicated piece of work and blamed for not accomplishing it properly. You can join this company if you are able to tolerate all above mentioned in the name of 'learning and experience'.