I won’t provide a number of questions to practice because everyone’s familiarity with coding interviews differs, but I must say that the fundamentals must be mastered. You should be able to understand and solve all the common/top interview questions. If you can, and have a solid grasp of the fundamentals, you can succeed in your algorithm interviews.
Don’t just put things on your resume to make it look fancy and/or complete. If you put something on (a project, experience, concept) make sure you understand it in great depth. They will ask you very specific questions about things on your resume, and failure to answer the question with confidence will be a major red flag. This means everything on your resume should be things you worked on in depth and can explain thoroughly.
Again, reviewing the common problems here will be a great starting point. Be sure to practice with a whiteboard as this is something many people fail to do and can’t adjust to during the interview. Framework wise, start from a high level, design a workable solution, and refine components one by one.
This is all about storytelling, not the theoretical. Study the common questions and prepare script or stories ahead of time. If you are seeking an entry level role, you should run through your responses with experienced professionals. You might think your response shows you in a good light, but your response might seem immature or show a major flaw to your interviewer.
If your response has something to do with technology (past project, conflict, etc.), make sure you get the details right. If your answer shows a lack of understanding, it again will be a red flag.
Most important tip for the interview:
Always over communicate! Ask clarifying questions, repeat the question to make sure you didn’t misinterpret it, and get organized. The interviewer wants to see your thought process and communication abilities. If you get stuck, don’t just freeze up and stop talking. Continue to ask questions and communicate what you’re thinking.
A final tip, if your interviewer starts asking you questions about your method or asks you about other methods or solutions, this is a warning for you to zoom out and think if your solution really is the right solution. If you insist on continuing with your method, this shows that you can’t take feedback and will result in negative interviewer feedback—especially if your solution ends up being completely wrong.