4 ms·
I interviewed a candidate who just could not pseudocode and talk at the same time. It was a little strange at first and I caught on to it and backed off to let
by partisan 11y ago
I interviewed a candidate who just could not pseudocode and talk at the same time. It was a little strange at first and I caught on to it and backed off to let him work on the task. It wasn't held against him. Everyone is not cut from the same cloth and it doesn't mean you can't contribute in amazing ways.
What I did hold against him was that he seemed to get frustrated and a bit angry by it. In a collaborative environment, you are going to have to talk to people and sometimes it interrupts you and your coding.
My advice is to develop some techniques for dealing with the issue. Namely, gather your thoughts on your approach, pick the first task, explain it to the interviewer so they know where you are going and will likely let you be for some time, and then write the code. Then discuss it and repeat the steps until you reach your solution. In this way, you are controlling the points at which you are switching contexts from coding to talking to the interviewer.
- muddyrivers 11y agoThank you for your advice, especially on controlling the points at which to switch context. I can listen, think, and talk. So I have no problem in meetings and discussions on either technical or non-technical matters. I am pretty good to go through code line by line with colleagues to trace down bugs. Only when it comes to the point to write down real code of a dozen lines or more that I have to be quite. I don't even mind my surroundings are loud or not.