4 ms·
I strongly disagree. If that happens then the interviewer is not doing their job. You don't ask the applicant to solve and then explain, you ask them to solve
by Jare 9y ago
I strongly disagree. If that happens then the interviewer is not doing their job.
You don't ask the applicant to solve and then explain, you ask them to solve and think aloud while they do it. If this doesn't come naturally to the candidate, which is totally fine, you must ask questions, suggest doubts, propose alternatives or request clarifications to encourage thinking aloud.
If you realize the candidate already knew the solution and is in fact just explaining it, then you have failed to prepare a sufficiently interesting question, and must come up with another.
- watwut 9y agoI was always pretty good at these questions, honestly enjoyed them and I would never tell you my actual thought process. Of course I would answer questions (which are basically fun side quests), but especially if you interrupt me with them, you are not getting anything remotely resembling my thought process. You have me answering your questions and my thinking+behavior are heavily influenced by them and by what I see in socially appropriate behavior.
- ivanche 9y agoSounds totally reasonable because 95% of the time software developers simultaneously write code and speak loudly about what they're doing at each step, while some timer is ticking in the background. Oh, wait...