Kind of demeaning interview process. First, I was sent an IQ test type thing. This took about an hour, and was actually kind of fun. Next, I got a 3-hour coding test. Typical hackerrank style questions -- not too difficult, although time is short. After this, radio silence for about a month. I assumed I'd failed the coding test, but finally I was contacted to do a 'video interview'. Basically, I had to spend an hour recording myself answering algorithms questions. AFAIK I got the questions right, but didn't make the cut, and was rejected after this. I have a feeling I was rejected because I didn't go to a big-name school, which they should have known already. So basically, 5+ hours of take home testing, spaced out over months, without EVER talking to a human. Bad experience. Still, here are some interview tips (without giving away questions): - It's ALL algorithms and data structures. So do lots of hackerrank, etc. - They like to give questions with complicated instructions. So be prepared to read and carefully analyze problem requirements. - Know basic algos (e.g., lots of sort algos, binary search, DFS) and data structures (trees, hash tables, heaps) well - Be prepared for a design question -- i.e., you'll need to very quickly understand the requirements of a problem and indicate what algos / data structures are appropriate.

First round was online assessment, it was OOP on Hackerrank. Then you can call with HR, they asked basic behaviorals and computer science trivia questions. next round (which is the final round) was 2 hrs technical with engineers.