The foundation course for freshers is too good. You will learn one skill nicely, but it won't have that much use in your future projects.
You will get relaxation because sometimes or many times you won't get much work. This is because in a team, there are more people working than is required.
Food facility, transport facility, and free gym facility are good.
Project parties at least twice a year used to happen.
A long period on the bench is a good option.
Due to overpopulation of employees in a team/project, you won't get much work to learn the technology. You will be doing the same work on Excel and some DB queries.
No leads/seniors want to teach you the technology. Otherwise, according to them, it may affect their job (simply to reduce competition).
Partiality is what I see in my team/project (may not be in small teams/projects) and it is too high. Employee capability is not decided by how much he knows or he can learn; it is all decided by your manager, who sometimes doesn't even know what work you did and how much you know, because you will be working under your leads directly and not under your manager.
The word "Budget" is a well-defined word when your performance cycle comes into the picture. How good or best you did doesn't matter because the project doesn't have a budget, so you won't get a hike or promotion.
Some employees work with their knowledge/learning, and some are habitual sycophants. Beware of such people.
Demotivation from your senior management. They want you to stop learning other skills/technologies because they hire you for their copy-paste work, and they fear if you learn something new, then you may affect their planning for the project.
Please try to manage the number of employees in a team according to work requirements, as it affects individual learning.
Try to keep leads isolated from managers or other seniors to leads during performance discussions. This is because leads are the ones under whom we work, and they know our status better than a manager who never asks what you did or how much you are doing.
1. Call with recruiter, basic questions about the role and how you can fit well into the position. 2. First round interview with 12 behavioral questions, answered with the STAR method. 3. Got scheduled for a third round but was offered another posi
I interviewed for SSRS and it went well. The interview was not difficult as I had interviewed for a junior role. The HR process is also quite fast. 1. Initial screening by HR 2. Technical 3. Manager round 4. Salary discussion by HR
Sharing my interview experience at Accenture Inc. (Philippines) way back in 2015 when I applied for the Software Engineer Analyst role. The hiring process was quite fast. They conducted the initial interview and technical assessment over the phone. T
1. Call with recruiter, basic questions about the role and how you can fit well into the position. 2. First round interview with 12 behavioral questions, answered with the STAR method. 3. Got scheduled for a third round but was offered another posi
I interviewed for SSRS and it went well. The interview was not difficult as I had interviewed for a junior role. The HR process is also quite fast. 1. Initial screening by HR 2. Technical 3. Manager round 4. Salary discussion by HR
Sharing my interview experience at Accenture Inc. (Philippines) way back in 2015 when I applied for the Software Engineer Analyst role. The hiring process was quite fast. They conducted the initial interview and technical assessment over the phone. T