Under typical work conditions, in a decent team work environment, there is the planning phase during which one should be able express why and how to solve something in a particular way. This is needed so your peers can review and poke holes at it. This can be done via email, Slack, IRC or in a conf. room. Once the planning phase is done, of course nobody sane wants endless chatter about it. This is the implementation phase, ideally carried out without distractions until done or something big is discovered which requires another round of planning.
Interviews, unlike ordinary day in a coder's life, are more stressful because they combine the two phases into a short time-frame: design (coming up with a solution) and implementation. The interviewer thus has a critical role to ease the pain of the candidate and make her/him feel welcomed, not rushed. Nevertheless the candidate must be able to explain the design/solution because it's part of the phase-1 objective, i.e. to avoid coding mistakes before any code is even written. Establishing if a candidate can describe the design or solution is reasonable expectation and edA-qa's article nailed it.
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.
Under typical work conditions, in a decent team work environment, there is the planning phase during which one should be able express why and how to solve something in a particular way. This is needed so your peers can review and poke holes at it. This can be done via email, Slack, IRC or in a conf. room. Once the planning phase is done, of course nobody sane wants endless chatter about it. This is the implementation phase, ideally carried out without distractions until done or something big is discovered which requires another round of planning.
Interviews, unlike ordinary day in a coder's life, are more stressful because they combine the two phases into a short time-frame: design (coming up with a solution) and implementation. The interviewer thus has a critical role to ease the pain of the candidate and make her/him feel welcomed, not rushed. Nevertheless the candidate must be able to explain the design/solution because it's part of the phase-1 objective, i.e. to avoid coding mistakes before any code is even written. Establishing if a candidate can describe the design or solution is reasonable expectation and edA-qa's article nailed it.