You can get opportunities to work in customer-facing roles.
WFH flexibility can be available, depending heavily on your manager.
Some teams are working with relatively newer Java versions.
Compensation can be good compared to the market.
There is significant micromanagement, with very limited freedom to make technical or implementation decisions unless you are a Principal Engineer—and even then, it depends on your reporting manager.
Some teams continue to work with older technologies and legacy practices.
There can be a strong focus on PIP/performance warnings when things are slightly off.
Cross-team communication is a major challenge. Getting help from other teams or even connecting with the appropriate people can be difficult.
Some Indian team managers appear hesitant to directly engage with developers when issues arise.
There is limited support for cross-team collaboration, and you often have to figure things out yourself.
There does not appear to be a proper exit interview or exit survey process.
Micromanagement is a major issue, with limited freedom to make technical decisions unless you are a Principal Engineer—and even then, it depends heavily on your reporting manager.
Office politics can play a significant role. Senior members may push developers to implement things in a particular way, but if that approach fails, the responsibility can ultimately be placed on the developer rather than the person who directed the implementation.
Some teams continue to work with older technologies and legacy practices.
There can be a strong focus on PIP/performance warnings when things are slightly off.
Work-life balance can be poor, with expectations to work late nights and weekends.
Cross-team communication is difficult. Getting help from other teams or connecting with the appropriate people can be challenging.
Some Indian team managers appear hesitant to directly engage with developers when issues arise.
There is limited support for cross-team collaboration, and developers are often left to figure things out on their own.
Product and Engineering alignment can be poor, with unclear roadmaps and insufficient discussion before features are assigned to developers.
Developers can be expected to handle everything from development to testing and automation without sufficient planning or support.
There does not appear to be a proper exit interview or exit survey process.
1. Technical round - Basic Java/OOPs questions 2. Technical/Managerial round - Technical questions and behavioral questions 3. HR round - Behavioral questions No coding questions were asked. Questions were mostly from technologies mentioned in resum
The technical and aptitude interview process included Java, SQL, and IAM concepts, as well as a technical and aptitude interview process with Java, SQL, and IAM concepts, and a technical and aptitude interview process with Java, SQL, and IAM concepts
The interview was mostly focused on the core concepts like OOPs concepts, core Java, and SQL queries. Since I was interviewing for an associate engineer position, the level of these questions was medium and focused mostly on how much practical under
1. Technical round - Basic Java/OOPs questions 2. Technical/Managerial round - Technical questions and behavioral questions 3. HR round - Behavioral questions No coding questions were asked. Questions were mostly from technologies mentioned in resum
The technical and aptitude interview process included Java, SQL, and IAM concepts, as well as a technical and aptitude interview process with Java, SQL, and IAM concepts, and a technical and aptitude interview process with Java, SQL, and IAM concepts
The interview was mostly focused on the core concepts like OOPs concepts, core Java, and SQL queries. Since I was interviewing for an associate engineer position, the level of these questions was medium and focused mostly on how much practical under