I submitted my resume online and was contacted by a recruiter two weeks later. She inquired about my interests and matched me with a team for a phone screen. The phone screen consisted of two simple questions coded on a shared document, one based on string manipulation and the other on finding anagrams. In each case, the interviewer had me write multiple solutions and explain the trade-offs between them. He also told me to justify which one I would choose for an actual implementation. I was invited to an on-site interview after two more weeks. This consisted of four rounds of technical grilling alternating between algorithmic puzzles and high-level design questions, with lunch (yumalicious) and a product demo after the third round. The algorithmic portions required a thorough knowledge of common data structures and their speeds, plus some basic graph theory. The design questions definitely continued the trend of the phone screen. The interviewer asked me to explain every choice of abstraction and data structure, which forced me to (a) identify alternatives and (b) adopt or reject them. As an example, I had to choose between storing absolute or relative locations of objects in a mock video game, which was influenced by my methods for collision detection and position updating. I didn't make good progress in the very last round, but the engineer told me I passed because it wasn't so much a test of competence as it was to make sure "you aren't a jerk". Finally, the founder interview. This consisted of basic stuff such as "tell me about this project on your resume" and "why do you want to work here"? I got an offer by email later that night.

3 rounds in total. One is Sql type question. Second is MBB type question and a learning and applying type question-basically builds on the earlier parts.Pretty straightforward just make sure to practice this skills before hand