Recruiter Phone Screen - You should be answer to basic questions about joins, loops. Coderpad tech interview - Fairly easy questions involving SQL joins, aggregates, python loops, and string manipulations. If you can solve most of the medium and hard SQL and Python questions on leetcode without looking up anything, this part should be easy. But do verbalize your thoughts so as to leave a good impression on the interviewer. In Person Interview - 3 whiteboard interviews. The most important thing to practice is to rapidly solve common logic / programming problems on a white board. You will not be asked obscure functions or modules, the relative efficiencies of sorting algorithms, and they are not "trick" questions. They are practical problems, not theoretical or academic problems. Don't waste time memorizing every sorting algorithm. You have to quickly identify the problem and write the optimal (or extremely efficient) answer. I say rapidly because in an hour interview, you may only have 20 minutes per problem between introductions, talking, and explaining. It also may be difficult to understand your interview's accent or handwriting. One interviewer I found particularly bad about interrupting, explaining boundaries, and constantly had me change my variable names, losing lots of time and understanding. Although they say they insist on perfect SQL, one interviewer told me I could not use a multi-part join condition and insisted I use two different joins. Hmm... Also it's a whiteboard, so syntax and and setup matter far, far less than your logic. The interview cares way more that you grasp the essential problem and solution than if you remembered a colon or to import the right module at the beginning. "Product Sense" - I got feedback that my product sense was not strong enough. Not sure, perhaps study problems faced by huge companies such as facebook such as very large scale data processing, or brainstorm all of the edge cases faced by a user before designing your solution, rather than letting the interviewer hint the edge cases.