In case you want a real answer here: > What difficulty of questions will be asked? Easy? Hard? Easy to medium depending on the position or any number of facto

In case you want a real answer here: > What difficulty of questions will be asked? Easy? Hard? Easy to medium depending on the position or any number of factors. MAYBE hard if you've done really well and solved the questions quickly. > Do people actually want to "hear the thinking process" or do they just want an optimum answer regurgitated quickly? Thinking process is far more important than getting the optimum answer. You have to talk your thought process out loud. Think less "find the best answer" and more "gather requirements and optimize within the given time window". It's far better if you treat questions as applicable to real world scenarios where you only care asymptotic complexity as a tool, because you have real resource/network constraints. It is still important to know how to analyze asymptotic complexity. It is not important to get the most optimal answer, but it is important to be able to optimize on the trivial (brute-force) answer which you should always state to begin with. Depending on the interviewer, they'll ask you go further and maybe prod you with hints. It's really really important to communicate and make sure you're solving the right problem and that the interviewer is on board; this is also a skill that you pick up. It also very much applies on-the-job "I did exactly what was asked" is probably the wrong thing to say if you're not taking ownership to clarify the issue and solve the root problem, because that's what's ultimately important. All of this can be learned with practice, and it is 100% expected that you study and practice. > Do I need to practice "regular" interview questions also ("What's your greatest weakness?")? Yes, behavioral questions are also important as long as you can pass the technical portion. The idea here is to understand how you would deal with situations. You answer these in a STAR (Situation, Task, Action, Result) or SAR format, and you should have these STAR format answers prepared for any types of questions they would ask. Depending on the company's guiding principles you would formulate your answers to display how you exhibited a particular principle in each of your stories. Don't be humble -- use "I" language rather than "we" language here (I had to practice this). Data based answers are best here ("grew user engagement as measured by replies by X%" vs "grew user base"). Impact is important but unfortunately that's not always within your control. The end-result isn't necessarily important but your learning is (e.g. if the project flopped, what important things did you learn that you'll never make the mistake of repeating again, and how can you pass that knowledge on to your team). Lastly, these interviews are designed to weed out false positives so even if you're more than qualified luck still plays a part and it can be a numbers game, so keep trying.