Dealing with challenging problems day to day in a software infrastructure team, and having broad ways of learning.
Training classes are always available at the company.
The formality and "pieocracy" of the company culture.
The complexity of the code structure of some of the legacy code that has been sitting there for a while.
I applied through a recruiter. Coding interviews were not too difficult. I completed 4 rounds: * 3 tech * 1 behavioral Very cooperative interviewers. Solved the problems but could not get past the behavioral round. Very transparent interview proces
1. Technical Phone Screen (45 Minutes) The first interview was a technical phone screen. I was asked to implement a vector in C++. I ended up using a dynamic array approach, increasing the array size as the vector filled. Then, I was asked a few stan
The first 20 minutes of the interview were behavioral, focusing mostly on your resume and past experiences. They also asked a "Why Bloomberg?" question. The next 30 minutes involved a LeetCode Medium question: a graph traversal question with backtrac
I applied through a recruiter. Coding interviews were not too difficult. I completed 4 rounds: * 3 tech * 1 behavioral Very cooperative interviewers. Solved the problems but could not get past the behavioral round. Very transparent interview proces
1. Technical Phone Screen (45 Minutes) The first interview was a technical phone screen. I was asked to implement a vector in C++. I ended up using a dynamic array approach, increasing the array size as the vector filled. Then, I was asked a few stan
The first 20 minutes of the interview were behavioral, focusing mostly on your resume and past experiences. They also asked a "Why Bloomberg?" question. The next 30 minutes involved a LeetCode Medium question: a graph traversal question with backtrac