Do not join if looking for a career in software. It's okay to join if looking for a career in process engineering or fabrication equipment customer support. The software unit is biased, with no opportunity for growth. Leftover projects from the US are common. Managers are nothing more than admins and have nothing left apart from micromanaging and backstabbing. It's good for 1 or 2 years, but do not stay for a longer period, as favoritism kicks in when one starts expecting growth and better opportunity rewards. In this era of hypercompetitiveness and innovation, do not join this company for software. This is an utter waste of an important phase of your career.
Do not tend to identify talent. Just stick to a couple of favorites. The software organization has become a family business. It does appear like a software company.
No advice can help. Agedness has kicked in.
It was an onsite interview. They called me over to their office. The interview mostly related to C++ and about my past experience and projects that I had worked on. It was more than a one-hour interview.
After applying on campus, the first round was a coding aptitude round, which consisted of three standard languages (Java, C++, Python). On passing, the second and third were technical rounds, which covered basic to advanced implementation of the lang
Basic coding, sound knowledge of previous projects, common mathematical problems, sound knowledge of queues, stacks, arrays, and data structures. Sound knowledge of OOPs concepts: encapsulation, polymorphism, operator and function overloading, file h
It was an onsite interview. They called me over to their office. The interview mostly related to C++ and about my past experience and projects that I had worked on. It was more than a one-hour interview.
After applying on campus, the first round was a coding aptitude round, which consisted of three standard languages (Java, C++, Python). On passing, the second and third were technical rounds, which covered basic to advanced implementation of the lang
Basic coding, sound knowledge of previous projects, common mathematical problems, sound knowledge of queues, stacks, arrays, and data structures. Sound knowledge of OOPs concepts: encapsulation, polymorphism, operator and function overloading, file h