Most people in upper management are involved in politics.
Developers frequently leave the company. Consequently, people without competency or even technical knowledge are running projects. However, this is the case with a few teams. Ask before joining if you will be led by developers or testers on the project.
Lower salary compared to the market. (However, this again depends on the project).
Huge hierarchy, which makes communication with upper management difficult if you become a victim of office politics or nepotism.
Legacy codebase without documentation and proper design, which makes the learning curve harder.
Service-based mentality in some teams. You are nothing but a resource, and you are expected to provide a solution to a bug/feature without deep analysis or consideration of impact on other components, simply because you are being billed.
Since the people who designed/developed the product are mainly from Germany, you will face a lot of trouble contacting them due to Indian management. They want to show onsite people that they are capable of taking on projects independently. (Yes, right!! They don't want to learn about product design and architecture. Instead, developers are expected to go into complex codebases that run on two platforms and find answers without any help in two days. This is their way of showing capability :-(
Please strive for quality over quantity of product. Look for your hierarchy people with testing backgrounds leading the development. This creates lots of communication gaps among developers and management because they don't understand the complexity of things inside the code.
Two rounds of technical interviews. One managerial interview (discussion about previous job experience and expectations with the new role). Final HR call (salary negotiations, date of availability, discussion about pre-employment medical checkup).
The recruitment team was quick to reach out and schedule the interview. They provided detailed information about the interview process, including: * The format * The people I would be meeting with * What to expect at each stage
The technical round is tough, but you have to be prepared with helpful Glassdoor review questions. Then you will definitely be able to clear the technical round. Java, Spring, Spring Boot, Spring Security, JPA, and Hibernate – these all should be pr
Two rounds of technical interviews. One managerial interview (discussion about previous job experience and expectations with the new role). Final HR call (salary negotiations, date of availability, discussion about pre-employment medical checkup).
The recruitment team was quick to reach out and schedule the interview. They provided detailed information about the interview process, including: * The format * The people I would be meeting with * What to expect at each stage
The technical round is tough, but you have to be prepared with helpful Glassdoor review questions. Then you will definitely be able to clear the technical round. Java, Spring, Spring Boot, Spring Security, JPA, and Hibernate – these all should be pr