You're working for a top software company, so it's nice to have on your resume.
Boring work. If you expect that you will be handling Java in this company, there's a high chance that you won't. Most likely, you will be dealing with proprietary tech, and in the worst case, you might even have to rely on a slow IDE on a VM to work on it. Debugging will be a headache because you won't find solutions on Google.
It starts fine during training, but once you're in the project, there's no work-life balance. There were many times that I did not sleep due to releases, and there was no overtime pay.
Pressure from work will burn you out.
They asked me one question each on DSA, OOPs concepts, and SQL. They asked me to write the code and then explain it. Additionally, there was a discussion on one of my projects.
The interview was moderate and consisted of four rounds, including an HR round. It focused mainly on DBMS, OOPs, and DSA. This was an on-campus interview where VPs and managers conducted the 3rd and 2nd rounds, respectively. Overall, it was a nice
The interview process consisted of four rounds. The first round was an online test, which included 35 questions: 33 multiple-choice questions and 2 coding questions. The first two rounds were technical interviews, followed by two HR rounds.
They asked me one question each on DSA, OOPs concepts, and SQL. They asked me to write the code and then explain it. Additionally, there was a discussion on one of my projects.
The interview was moderate and consisted of four rounds, including an HR round. It focused mainly on DBMS, OOPs, and DSA. This was an on-campus interview where VPs and managers conducted the 3rd and 2nd rounds, respectively. Overall, it was a nice
The interview process consisted of four rounds. The first round was an online test, which included 35 questions: 33 multiple-choice questions and 2 coding questions. The first two rounds were technical interviews, followed by two HR rounds.