They have good technology and good engineers, but not good managers.
The salary is reasonably good, and the office is situated in a good location.
Specially in some business units, low-level engineers are good compared to some senior-level engineers.
Managers want work done, and quality doesn't matter. They lack technical skills.
Shows a lot of favoritism for promotions and salary hikes. Due to this, some senior employees stick to the company for a long time and get good perks irrespective of their work.
Some Principal Engineers, who have been there for a long time, don't even help new joiners. On top of that, they do not even know how to code. They are surviving because they are pets to managers. You always find them with managers (for coffee, lunch, etc.) rather than helping others on the project. In the end, they showcase others' work as if they have done everything under the guidance of managers.
I haven't seen anyone give a good technical presentation or good input, or write code, especially in the BU where I have worked. Some Principal Engineers always try to avoid technical discussions, which shows how incompetent they are. But such people are white-collars there for nothing.
Managers don't have a sporting spirit in their reaction to managerial reviews.
Rather, they target engineers during appraisals, layoffs, etc.
Layoffs happen every month, and the only survival point is that you should be a pet to your manager. It was not the case earlier.
Some QA managers are far better than development managers in some groups.
This company has the worst HR team and doesn't address employee comments, especially those of low-level engineers.
Layoffs are very common here. Work is moved under maintenance mode, so there's not much development in some BUs.
It is good to give advice if there are true listeners. And I don't find any here.
I went through multiple rounds and, I must say, people have been working there for ages. They were extremely respectful, approachable, and accommodating. The role was in Bangalore, and the team was in Austin. After the initial tech capacity round, i
The interview process was on-site. Due to the urgency of the hiring, many candidates were present for the interview, and we had to wait a long time before being called for further rounds. Overall, the experience was good in the morning, but due to
The interview process focused heavily on system design principles and a solid grasp of the foundational aspects of the .NET Framework. It wasn't about memorizing syntax; it was about applying architectural thinking and demonstrating depth in platform
I went through multiple rounds and, I must say, people have been working there for ages. They were extremely respectful, approachable, and accommodating. The role was in Bangalore, and the team was in Austin. After the initial tech capacity round, i
The interview process was on-site. Due to the urgency of the hiring, many candidates were present for the interview, and we had to wait a long time before being called for further rounds. Overall, the experience was good in the morning, but due to
The interview process focused heavily on system design principles and a solid grasp of the foundational aspects of the .NET Framework. It wasn't about memorizing syntax; it was about applying architectural thinking and demonstrating depth in platform