Average to above average salary and perks.
Stable job.
Routine work, which is mostly done by contractors. You can sit idle if you like this approach.
You don't need to work hard to improve your technical skills :-)
Poor work culture.
Hardly any thought process into building good, crisp, intelligent solutions.
Claim to fame is business intelligence; absolutely no work done with predictive intelligence.
Mostly routine work of building useless reports and some dashboards.
If you are a strong/good technical engineer looking to do some good creative work, do not join here.
Plenty of managers who have no vision, no management experience.
Many non-technical senior managers who are extremely proud of not knowing what's happening in the industry and their poor technical skills.
Lots of politics that kill innovation and new ideas as frequently as possible.
Few political honchos who need to approve anything and everything that needs to happen.
Knee-jerk reaction is the long-term strategy mechanism, unfortunately.
No opportunities for employees to grow or build a defined career path.
Plenty of discrimination based on bias and favoritism.
Very minimal diversity in teams. On top of that, as if to promote diversity, they encourage less-than-smart people to grow, which further leads to frustration in engineers if you are good at what you do.
Create managers who can be leaders.
Distinguish between a well-oiled coordinator and a good technical manager.
Create leaders who do not have politics on their agenda and can inspire teams and engineers.
Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Honestly, pretty damn easy, lol. I'm going to try Google next. This was genuinely so simple, I'm amazed a FAANG company would do this. Just practice 300 LeetCode questions and you'll be set!
It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.
Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Honestly, pretty damn easy, lol. I'm going to try Google next. This was genuinely so simple, I'm amazed a FAANG company would do this. Just practice 300 LeetCode questions and you'll be set!
It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.