I had a tough experience during a coding interview yesterday, and it's still bothering me. I've been studying hard and have solved over 300 coding problems, feeling pretty confident. The interview started well with an easy warm-up question. But then I was presented with a medium-level graph problem, and I completely froze. I recognized the concept but couldn't articulate my thoughts. The interviewer was watching, and every moment of silence felt eternal. I ended up rambling about BFS and DFS without making real progress. When the interviewer offered a hint, it felt humiliating and only added to my pressure. I received a rejection email this morning, and it's disheartening after applying for four months and feeling prepared each time only to falter under pressure. Has anyone else faced this mental block? Is this a sign that this company isn't right for me, or can I change my approach somehow?
6 Answers
The pressure during interviews really is a different beast. It might also be helpful to reframe how you think about interviews—like, instead of viewing it as a test, think of it as a collaborative effort. Ask questions, brainstorm together, and just take it step by step!
I’ve been there! One thing that really helped me was to have a fallback strategy. When I get stuck, I take a breath and say something like, 'Let me think through this aloud.' It buys time and shows the interviewer I’m still working through the problem instead of freezing.
Just remember, one bad interview doesn't define your abilities! Interviewing is its own skill, and with practice, you’ll improve. Each setback teaches you something new. Keep pushing through and keep learning—your opportunity will come!
It sounds like interview anxiety got to you—it happens to everyone! Try practicing mock interviews with friends or online platforms to simulate the real pressure. When you blank, it helps to verbalize your thoughts or break problems into smaller steps with your interviewer, showing them how you think.
Don’t be too hard on yourself! It’s totally normal to blank during interviews. Many candidates don’t hit the nail on the head even when they get a hint. If you can make progress after a hint, that's often seen as a positive, showing that you can adapt and problem-solve. Remember, the interviewer is more interested in your approach than just naming algorithms.
That’s true! Sometimes interviewers just want to see how you tackle problems, even if your first solution isn’t optimal.
As someone who interviews candidates, it’s super common for people to blank. Don’t take it personally! Focus less on the names of algorithms and more on how you can solve real problems. Being stuck isn’t the end; just talking through your thought process can keep the conversation going, which is what they really want to see.
I totally agree! I often suggest that candidates focus on collaborative problem-solving during the interview, treating it like pair programming.
Exactly! It’s all about showing intent, not just coming up with a perfect answer.