This sounds like a classic case of testing for rote memorisation of algorithms that seems almost designed to hire either junior devs fresh out of college, or other people who specifically study for the kinds of unrealistic tests encountered in bad interviews.
While I agree that you want to probe for basic computer science understanding, I find these sorts of interviews needlessly stressful, unrepresentative of the normal working environment and most of all, incredibly ineffective.
The sad thing is, a lot of the time the interviewers themselves know that the process is bad, but feel compelled to go along with it anyway. For the most part it's a waste of time for all participants.
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.
This sounds like a classic case of testing for rote memorisation of algorithms that seems almost designed to hire either junior devs fresh out of college, or other people who specifically study for the kinds of unrealistic tests encountered in bad interviews.
While I agree that you want to probe for basic computer science understanding, I find these sorts of interviews needlessly stressful, unrepresentative of the normal working environment and most of all, incredibly ineffective.
The sad thing is, a lot of the time the interviewers themselves know that the process is bad, but feel compelled to go along with it anyway. For the most part it's a waste of time for all participants.