If I give you three numbers, The advantage to solving it without code first is that 1) it gives you fragments and solvable pieces to build your code, 2) it proves your solution works, and 3) it shows the interviewer that you do actually know how to solve the problem, which gives you some points in their book, even if you can't code it in time.
It also shows the interviewer that you can hold a good conversation, solving a problem out loud.
It's been said that problem finders are dime a dozen, but problem solvers are worth their weight in gold.
Point being, people who can fix problems are much more valuable, and rare, than people who can simply identify problems.
Interviewers want to see someone who takes pride in knowing that their solution is correct!
Once you know you have a solution, finish explaining anything that wasn't covered in the earlier steps.For myself, I wasn't so much concerned with school as I was anxious about the beginning of .😱 It was a magical time when I would call up and message every technical friend I knew asking for references to their companies, and I would apply to every internship opportunity on Intern Supply, which BTW, is a great website for finding all the available applications for internships.Before you even start writing or thinking about any code, take your examples that you created, and solve the problem verbally.So many Computer Science students skip this part and jump straight into the code, only to wind up at a dead end or confused, which just wastes more precious time.When does a situation or circumstance become problematic? Additionally, explain how you conducted risk management. Lesson learned Explain in detail what was accomplished and what strategies proved effective.What factors must be considered before the problem can be properly analyzed? Analyze the Problem Describe in detail how you gathered data, facts, and other information needed to develop solutions. Generate Possible Solutions Describe in detail how you: Got to the heart of the problem? Conclude your answer by explaining how you developed professionally from the experience and what you will do differently in the future.I was frustrated, because I was never good at explaining my thought process on the technical problems they gave...until it dawned on me that I was overthinking everything and didn't go into the interview with any strategy.The steps below have helped me numerous times and I can attest to their ability to aid in landing that big job or internship! The interviewer will give you whatever technical question they have in mind.I was fortunate enough through the end of high school and into college that I had enough experience to in an interview.My first year, I landed interviews with Facebook, Google, Digital Ocean, and more, but I didn't get past the second (technical) round for any of them...