Stable company, with lots of products and groups to move throughout.
Large company, hard to get anything done or fixed. Management has no real power. Decisions come down from Directors who often have no clue. When something goes wrong, they just re-org and shuffle things around to make the illusion of stuff being fixed, but the same old problems still exist. Cycle and repeat.
You hire technical engineers to solve problems, but you don't listen to them. You listen to some hotshot new director who has no clue about the problems or the solutions. Listen to the technical people you pay.
Speak with the recruiter, then with the hiring manager, then with someone on the team who does a job similar to mine, and finally, a technical panel with the rest of the team. The recruiter was the main point of contact.
I went through two rounds and was rejected for an unknown reason. Round 1 - I was asked one coding problem and about Java basics. Round 2 - I was interviewed by a person who is from a QA background. He asked very basic questions, and I learned that
This is not a lengthy review, but preparation is needed. There is a lot of focus on industry knowledge, so be prepared for questions on that front. I also found some questions on behavioral analysis. All the best for the interview!
Speak with the recruiter, then with the hiring manager, then with someone on the team who does a job similar to mine, and finally, a technical panel with the rest of the team. The recruiter was the main point of contact.
I went through two rounds and was rejected for an unknown reason. Round 1 - I was asked one coding problem and about Java basics. Round 2 - I was interviewed by a person who is from a QA background. He asked very basic questions, and I learned that
This is not a lengthy review, but preparation is needed. There is a lot of focus on industry knowledge, so be prepared for questions on that front. I also found some questions on behavioral analysis. All the best for the interview!