> Number 2: No One Believes Anyone Can Actually Code
It's about the level and structure of your code. They don't think you _can't_ code, they want to know how _well_ you code.
When I'm interviewing people I let them solve a simple problem as well - it doesn't need to work, it doesn't need to be perfect. I just want to know where the interviewee stands. Case in point - I've had a young-un just out of school in for an interview and his code was clean, commented and had structure.
On the other hand I've had an older bloke in with roughly ten years of experience as a programmer. His code was an absolute mess from start to finish with K&R-style initialization etc.pp.
That is why I want to see how they approach and what code they produce - someone may have been writing code since they were born, but if they never went through a review their code will likely be bad.
> Number 3: Coding Tests Can Trip Up Even Good Engineers
That is true, hence a coding test should not be measured on the completion but rather on the approach the interviewee took.
> Number 10: You’ll Never Really Know Why You Weren’t Hired
True and bad. I dislike companies who don't give the applicants feedback - or even worse false feedback. Much like in a review - if all you hear is 'no, wrong, bad, ...' you won't improve. You need explanations to single out the issues you can work on (primarily in the short term).
It's about the level and structure of your code. They don't think you _can't_ code, they want to know how _well_ you code.
When I'm interviewing people I let them solve a simple problem as well - it doesn't need to work, it doesn't need to be perfect. I just want to know where the interviewee stands. Case in point - I've had a young-un just out of school in for an interview and his code was clean, commented and had structure.
On the other hand I've had an older bloke in with roughly ten years of experience as a programmer. His code was an absolute mess from start to finish with K&R-style initialization etc.pp.
That is why I want to see how they approach and what code they produce - someone may have been writing code since they were born, but if they never went through a review their code will likely be bad.
> Number 3: Coding Tests Can Trip Up Even Good Engineers
That is true, hence a coding test should not be measured on the completion but rather on the approach the interviewee took.
> Number 10: You’ll Never Really Know Why You Weren’t Hired
True and bad. I dislike companies who don't give the applicants feedback - or even worse false feedback. Much like in a review - if all you hear is 'no, wrong, bad, ...' you won't improve. You need explanations to single out the issues you can work on (primarily in the short term).