The interview is not just about you solving the problem. A good whiteboard problem and a good interviewer will solve the problem with you. What is being gauged is how well WE work together to solve the problem. Can you communicate something to another engineer? How well do you cope with interruptions? If a requirement suddenly changes, did you think forward enough to be able to handle it, or did you just solve the problem as it was presented to you?
Is "thinking out loud" necessary to assess these aspects/skills? If not, they why use it while putting the interviewees at disadvantage; that's my point.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The interview is not just about you solving the problem. A good whiteboard problem and a good interviewer will solve the problem with you. What is being gauged is how well WE work together to solve the problem. Can you communicate something to another engineer? How well do you cope with interruptions? If a requirement suddenly changes, did you think forward enough to be able to handle it, or did you just solve the problem as it was presented to you?
Is "thinking out loud" necessary to assess these aspects/skills? If not, they why use it while putting the interviewees at disadvantage; that's my point.