QUOTE(Greatune @ Aug 17 2014, 12:28 AM)
RiddleMeThat, u are totally wrong, those cs algorithm tasks needed to get tested on the spot, to identify the candidate how good their problem solving skill and logic is. those cs stuffs and algorithm logic are extremely important in business world.
you can code this and create this, it doesn't mean u can solve some problems.
RiddleMeThat, i guess u are quite comfort on what u doing? not much challenging tasks been given in your job?
try interview at Jobstreet, see whether u can pass their test, all written in paper and explain how it works to interviewer and tell them why this way is better and faster on the spot.
The problem with people like you is you've never been on the end trying to hire people and lack the experience to evaluate candidates based on other factors and not hardcore technical skills. If you cannot smell bs without a coding test, you're unfit to be an interviewer, period.
I've coded much more complicated routines than ever needed in apps. I've done all those data structures and I find they're not really needed in many of the stuff we do nowadays unless you're doing OS level stuff like SQL server engines, writing OS, compilers, image manipulation software, or even develop games which I used to do. Heck, I don't even bother to remember off the hat code worth over 5 years ago I did last time unless I go back to refresh all those linked list, stacks and others I implemented for a game.
My most challenging code recently deal with queues, stacks and recursion and even that I don't bother to memorize what I did. It's a game related mobile project, but less challenging than my x86 assembly code project 10 years ago.
If I were much younger I would probably use these tests when looking for candidates in such field but I realized I am arrogant and unrealistic to do so, causing me to miss out way too many more competent candidates than necessary to fill the tasks at hand.
I realized that most interviewers who use irrelevant interviewing techniques..
1. Lack understanding of the position hiring for.
2. Has some sort of ego/insecurity/inferiority complex issues that they need to project/bully candidates.
3. Are put in as a shortcut way to get programmers which they could work with instead of what's good for the whole team, maybe because they're so sick of interviewing candidates they just use tests instead of actually talking to every one of them instead.
Never ever put a pure technical/programmer to interview candidates. They're more likely to have extreme bias purely based on that area only and because of their lack of business acumen, people soft skills and foresight, they will not be able to identify the best fit candidate. Fear of competition is also a reason why a programmer may deliberately reject someone better than them for promotion competition so they might deliberately pass on the better candidate.
When my ex-boss forced me to interview all potential candidates, I never make them do coding tests because it was unnecessary. I can easily spot their ability asking them to explain things or data structures. I don't like wasting time making them write code because that environment is not the same as actual working environment.
But i'll always give priority to those who can show me what they did before instead of those who expect me to view their grades.
Coding tests waste their time and my time. I don't even need those to evaluate fresh grads.