I once had an interview where I was given a research paper to read for about 30 minutes after which I was asked to explain the content and then a few follow-up questions. This paper was related to the job I would be doing. It was a straight-forward, no-bullshiting interview. I like interviews that ask relevant questions not a "balance this red-black-tree" gotcha questions. Needless to say, I got the job.
I like interviews that ask relevant questions not a "balance this red-black-tree" gotcha questions.
Yeah I agree. That is definitely part of why I dislike coding questions in interviews: relevance.
I also think it is an unrealisticly stressful situation. Sure some might say the pressure is good but normally you don't lose an opportunity like a job for doing one coding aspect poorly while in a room with strangers who are judging every line. Maybe if the software you are working on is life or death, maybe then it is appropriate...
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 once had an interview where I was given a research paper to read for about 30 minutes after which I was asked to explain the content and then a few follow-up questions. This paper was related to the job I would be doing. It was a straight-forward, no-bullshiting interview. I like interviews that ask relevant questions not a "balance this red-black-tree" gotcha questions. Needless to say, I got the job.
Interesting approach!
Yeah I agree. That is definitely part of why I dislike coding questions in interviews: relevance.
I also think it is an unrealisticly stressful situation. Sure some might say the pressure is good but normally you don't lose an opportunity like a job for doing one coding aspect poorly while in a room with strangers who are judging every line. Maybe if the software you are working on is life or death, maybe then it is appropriate...