My point is advocating refusing to do a task by your interviewer is not in your best interest to get a job. We can be clever all we want with why we don’t need to know or prove something but they decide if you are in or out.
I agree with you in the fact that its probably not the best route in obtaining a job to go. My issue is when an interviewer asks me algorithm question(s) when they never use that in in their daily job. That frustrates me, 'why ask me that if its not an integral part of the job?'.
I can understand that, there are better ways to test someone’s working knowledge or ability to find it. Personally, I’ve worked with HR people and it seemed more personality based than technical based in my experience.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm not advocating "refusing to do a task", btw. I was more getting at demonstrating (without being too pedantic about it) that you can evaluate what you need to do to solve a problem, and how you might go about finding a solution. For something like sorting, Googling or looking on Stack Overflow is likely to be sufficient for most problems. If it was something esoteric, then more effort might be required.
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.
My point is advocating refusing to do a task by your interviewer is not in your best interest to get a job. We can be clever all we want with why we don’t need to know or prove something but they decide if you are in or out.
I agree with you in the fact that its probably not the best route in obtaining a job to go. My issue is when an interviewer asks me algorithm question(s) when they never use that in in their daily job. That frustrates me, 'why ask me that if its not an integral part of the job?'.
I can understand that, there are better ways to test someone’s working knowledge or ability to find it. Personally, I’ve worked with HR people and it seemed more personality based than technical based in my experience.
I'm not advocating "refusing to do a task", btw. I was more getting at demonstrating (without being too pedantic about it) that you can evaluate what you need to do to solve a problem, and how you might go about finding a solution. For something like sorting, Googling or looking on Stack Overflow is likely to be sufficient for most problems. If it was something esoteric, then more effort might be required.