Good opportunities. Large company with hands in every financial industry domain, so you can get good exposure. Nice culture, good technology stack.
There's a lot of red tape to get anything done in time. If you work hard and deliver, you can expect to get burned out. There's a very uneven distribution of knowledge, and a large chunk of the tech organization is absolutely unproductive.
Streamline the tech organization. Separate architecture teams in each BU are mostly useless and unproductive.
Our interview process begins with an initial screening to assess basic qualifications, followed by a technical assessment tailored to the role's requirements. Candidates then proceed through a series of interviews, including technical, problem-solvi
I was referred and submitted my application through a referral link. There was a phone interview that asked me about my general knowledge and the four OOP principles. Then, I had a coding interview that was extremely simple and just involved pseudoco
Basic behavioral questions and the interviewer was very kind throughout. The coding part was mainly a review of my previous work. At no point did I feel anxious, and I felt confident that I was given the opportunity to show the best of myself.
Our interview process begins with an initial screening to assess basic qualifications, followed by a technical assessment tailored to the role's requirements. Candidates then proceed through a series of interviews, including technical, problem-solvi
I was referred and submitted my application through a referral link. There was a phone interview that asked me about my general knowledge and the four OOP principles. Then, I had a coding interview that was extremely simple and just involved pseudoco
Basic behavioral questions and the interviewer was very kind throughout. The coding part was mainly a review of my previous work. At no point did I feel anxious, and I felt confident that I was given the opportunity to show the best of myself.