The most beautiful office you'll ever see, with free health care, smart people, and a very collaborative and friendly environment.
Expect to work with very old code (20-25 years, including Fortran) written in very old C++.
As a first job, it's a good resume builder, but get out after a few years as you'll learn nothing marketable.
The company has a philosophy of "testing in production," so expect to get called in the middle of the night.
The corporate culture is strong, so you'll either fit in or get expelled. Be prepared to drink the Kool-Aid.
Don't bother applying if older than 35.
During my time, I saw no one hired with significant (> 10 years) software development experience.
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.