| I can really echo the idea of a mock interview with a friend. Find a friend who will let you do a mock interview with them over a screenshare for 45 minutes. They do not even have to know how to code. Give them a link to the leetcode problem list or similar, tell them to filter the page by <your chosen difficulty>, and select a problem at random and message you the link. Solve the problem in front of them like you would in a real interview. I created a small cheatsheet for my friends who did this for me, as non of them were professional programmers. My cheatsheet was essentially Step 1: I will read the problem back to you, probably paraphrased in my own words and then ask you to confirm some assumptions. You can say "yes" to every assumption I ask you. Step 2: I will verbalize my thought process to solve the problem. This may involve writing a tiny bit of code to layout the task, but there should not be much code or any yet. Step 3: I will start actually coding the solution. If I write code for more than 30 seconds without verbalizing my thoughts, alert me. If I'm not writing code but silent for more than a minute, alert me. You don't need to understand what I'm saying or writing, just make sure I am almost always talking. Step 4: I will try to walk through my finished code step-by-step and make sure it works. Again, you don't need to understand what I'm saying, just make sure I'm always saying something. -- One last thing that may help ease your mind a bit. Maybe I've just been very lucky with my interviewees, but I've found that communication skills and being able to lay out very clean code as my final answer is just as helpful as actually being able to quickly solve the problem. I've needed a hint from the interviewer a lot of times to solve my question. Simply asking for a hint is obviously not good, but saying something like "This code won't work in the case where all 3 points make a parallel line, and I'm trying to come up with a solution for that... I feel like there's another way I can visualize this that I'm not seeing right now" is better. Good luck, coding tests suck. But you gotta do what you gotta do. |