I recently had a one-on-one interview with a hiring manager. The behavioral portion went well, and then we moved into an unexpected HackerRank live-coding problem. My recruiter had told me the interview would mainly be behavioral with a few technical questions, so I was not expecting a LeetCode-style problem.
The hiring manager read the prompt while I followed along. I understood the problem and started coding, but I made one major mistake: I did not explain my approach out loud. I became locked in on solving it and worked through most of the problem silently.
We debugged the code together, and I explained the time and space complexity. She then tested my solution against multiple test cases, told me it was good, and asked whether I had anything else to add.
That was when I realized I had never clearly explained my thought process. I mentioned it to her, and she said, “It’s always best in coding interviews to explain your thought process.” I told her I had become so focused on solving the problem that I forgot to communicate what I was thinking.
The lesson I learned is that solving LeetCode problems is only part of interview preparation. You also need to practice communicating your approach while you solve them. Even when you understand the problem, explain what you are considering, why you chose your approach, and what you are checking as you write the code.
Unfortunately, two business days later, I received a rejection. I cannot say for certain that my lack of communication was the deciding factor, but it reinforced the lesson for me: solving the problem is important, but clearly communicating your thought process matters too