3 ms·

> Though it is clearly a simple problem, I've not had to reverse a list in any of the code I've written in the past 20 years. So I am not 'familiar' with the pr

> Though it is clearly a simple problem, I've not had to reverse a list in any of the code I've written in the past 20 years. So I am not 'familiar' with the problem. I think I'd be able to solve it pretty quickly under normal work circumstances (even crises), but as many have said here already, working on something you've never done before with three strangers looking over your shoulder is a whole other dimension. What's your point? You just want to repeat what everyone else has already said? And how low do you think the bar should be? What would be reasonable questions that actually still separate people who can code from people who can't, since reversing a list is too hard according to you? > It's real and it totally wrecks the interview for the interviewee and the interviewers, who lose out on a potentially good employee. Or they hire someone else who might actually be just as good or better. It's not like companies have an unlimited number of open positions.

frankzinger 9y ago
I was responding to the words I quoted from your post. I was not aware that somebody had already made the point that even apparently simple problems may not be 'familiar' to all candidates.
- tytytytytytytyt 9y ago
  It doesn't have to be 'familiar'. A fair bit of the point is to judge your problem solving skills, not your memorization skills.
  - frankzinger 9y ago
    For sure. I never said all interview questions have to be 'familiar'. I'm not the same guy you were talking to earlier.
frankzinger 9y ago
> And how low do you think the bar should be? What would be reasonable questions that actually still separate people who can code from people who can't, since reversing a list is too hard according to you? I'm not saying anybody should lower any bars. Just don't immediately fail somebody who struggles with a simple problem. Don't just automatically declare them incompetent. Help the candidate be the best version of themselves. It's in your best interest as an employer. Try to figure out ways to make your interview atmosphere as realistic as possible. Some of these people who choke on trivial problems may have aced the same test on a better day.

frankzinger 9y ago

I was responding to the words I quoted from your post. I was not aware that somebody had already made the point that even apparently simple problems may not be 'familiar' to all candidates.

tytytytytytytyt 9y ago
It doesn't have to be 'familiar'. A fair bit of the point is to judge your problem solving skills, not your memorization skills.
- frankzinger 9y ago
  For sure. I never said all interview questions have to be 'familiar'. I'm not the same guy you were talking to earlier.

frankzinger 9y ago

> And how low do you think the bar should be? What would be reasonable questions that actually still separate people who can code from people who can't, since reversing a list is too hard according to you? I'm not saying anybody should lower any bars. Just don't immediately fail somebody who struggles with a simple problem. Don't just automatically declare them incompetent. Help the candidate be the best version of themselves. It's in your best interest as an employer. Try to figure out ways to make your interview atmosphere as realistic as possible. Some of these people who choke on trivial problems may have aced the same test on a better day.