I recently had a technical interview that lasted an hour, but it went 25 minutes over time because I struggled during the live coding section. While I eventually figured things out, the interviewers helped me by giving feedback and emphasized focusing on logic rather than syntax. They also mentioned that there will be a final interview if I progress. I'm curious about what this means from an interviewer's perspective. Does running over time due to difficulty suggest a bad performance, or is it more about how I recovered from those challenges?
5 Answers
As someone who interviews candidates, I'd say the fact they allowed the interview to extend by 25 minutes is a good sign. It shows they were interested in what you were trying to convey. If an interview isn't going well, I often look for a polite excuse to wrap it up—so an extra 25 minutes means they saw potential.
In this job market, going over time isn't ideal, but if you showed potential and the interviewers thought you might be a good fit, they could overlook it a bit. If the interviewer gave you feedback and you found a solution, that could work in your favor. Keep in mind that every interviewer has their own criteria, so it can vary greatly.
True, I guess every candidate gets judged differently.
I think it's more about the process than the code itself. They likely appreciate your problem-solving approach more than just finishing the task. If you communicated your thought process and showed your attempts, that's a good sign. Asking questions and engaging with feedback is key.
I did manage to communicate more once I started figuring things out. I think that helped!
Definitely! Being engaged and responsive is what they look for.
I don’t want to rain on your parade, but generally, interviewers prefer candidates who can complete tasks within the time limit. If they let it run over, they may still have concerns about your ability to perform under pressure. It’s tough out there; make sure to ask for feedback after if you get a second interview.
Good advice! I’ll definitely ask for feedback if I get the chance.
It really can depend on how you handled the struggle. If you were talking through your thought process while going through issues, that shows you're willing to learn. If you just went silent, that might leave the interviewers concerned. It’s all about how you handle pressure and communicate while coding.
I went quiet for a bit, but then I started talking through what I was trying to do, at least.
I get that! It must be hard to just cut someone off, but it does seem kinder to just end it if it's going poorly.