Loads of money, great fun.
kafkaesque, felt useless, and did not have a lot of progress opportunities.
Contacted by a recruiter and then a technical interviewer. The process took two weeks. The interviewer got straight to coding a question – no BS. They were looking for good code, not just a solution. I found it quite annoying that they are purely l
1. Recruiter phone screen 2. Phone interview 3-4. Onsite x2 1. Was not difficult at all. Just make sure you are familiar with the language you choose and Big-O notation of some sorting algorithms and data structures. 2. The problem was easy, but I
Two rounds of campus interviews or two rounds of phone interviews. Then, four rounds of on-site interviews. The interview questions are mostly algorithm problems. The problems for me were harder than those at most other companies I had interviewed wi
Contacted by a recruiter and then a technical interviewer. The process took two weeks. The interviewer got straight to coding a question – no BS. They were looking for good code, not just a solution. I found it quite annoying that they are purely l
1. Recruiter phone screen 2. Phone interview 3-4. Onsite x2 1. Was not difficult at all. Just make sure you are familiar with the language you choose and Big-O notation of some sorting algorithms and data structures. 2. The problem was easy, but I
Two rounds of campus interviews or two rounds of phone interviews. Then, four rounds of on-site interviews. The interview questions are mostly algorithm problems. The problems for me were harder than those at most other companies I had interviewed wi