I fail to see how this interview problem does anything other than play "stump the chump." Realistically interviews are about determining if a person's skills, and personality are a fit for the team, and the work being done. How does this accomplish any of that? I can't think of a single time that this scenario would be applicable to an actual project. And I am of the belief that at any interview, "you are interviewing them, as much as they are interviewing you." This would speak volumes to me as part of a terrible "Know-it-all" / gate keeper culture that I would not want to be a part of.
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.
I fail to see how this interview problem does anything other than play "stump the chump." Realistically interviews are about determining if a person's skills, and personality are a fit for the team, and the work being done. How does this accomplish any of that? I can't think of a single time that this scenario would be applicable to an actual project. And I am of the belief that at any interview, "you are interviewing them, as much as they are interviewing you." This would speak volumes to me as part of a terrible "Know-it-all" / gate keeper culture that I would not want to be a part of.