2 ms·
>It all comes down to writing code on a whiteboard or in a notepad. Thanks for elaborating but that's sad news. I thought we had all collectively decided this
by Clubber 10y ago
>It all comes down to writing code on a whiteboard or in a notepad.
Thanks for elaborating but that's sad news. I thought we had all collectively decided this was a horrible way to interview people. If a company absolutely must have code written, assign all interviewees a programming task and have them submit it through GitHub or on your site. Something that shouldn't take more than 30 minutes for a moderate developer. Anyone who doesn't complete it gets filtered, and you get a good example of their thinking, style, sloppiness, comment habits, etc. If you think they nicked it from the internet, have them make a slight change.
I've always considered the ability to be able to design a piece of software or module from nothing to something complete in a moderately elegant way was way more important than if someone had memorized how some algorithm works without ever having the need to implement it.
It's akin to asking a painter how to build various types of brushes and how to harvest paint, or an author how to make pens. That ability isn't useless, but certainly don't make that the focus of your interview.
I want experienced software designers, they can learn anything they are lacking with whatever stack we use in house in just a few weeks. I'll just stick to using my methods and wait until the industry catches up. :)
- bsvalley 10y agoWhat you're describing is the perfect way to evaluate a developer. That's exactly what I promote to my employers. That's what I ask at the last step of the hiring process if we still have a doubt. we should use this evaluation only and get rid of the extras. Then we should talk about life and work in general for an hour rather than a stupid algorithm question just to make sure the candidate isn't a d*ck.