Honestly, any pros you get here can be found in any other company:
As a senior, you will rarely get a chance to grow and become more senior. They will continue to dump random management responsibilities on you until you can be a manager.
Some team engineers don't even code all that much; they're too busy worrying about red tape and meetings all day. Sometimes it takes two days of meetings to make one small code change, which gets scrutinized to no end because no one has actual work. Reviewing CRs (PRs) is something they can mention at stand-up.
Some teams genuinely don't do anything, like actual work; they clock in and clock out.
No one has a larger plan until the last minute. Even if there's a large, looming engineering deadline, they won't care until it's too late.
There are too many managers here. They absolutely should not be managers; they have no people skills and no management skills.
The only way to level up here is to become a manager, so smart engineers become managers. But most of these people can't talk to a brick wall or have no idea how to be a good manager. They need classes on developing engineers rather than punishing them for mistakes they should be correcting. I've seen good hires get bad annual reviews from crappy managers because they don't know how to manage.
If you tell HR about an issue with a manager or an issue, they won't do anything. Even if people are leaving in droves from that team and complain about a manager during the exit interview, that person will just stay on the team and sometimes get promoted.
There's a culture of middle managers who are just trying to justify their jobs. Turn them into engineers and give them raises; don't force them to be managers.
Pay here sucks. You might get a good entry offer, but you will not get a raise no matter how you perform.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.