3 ms·

I disagree with one click solutions for homework being viable. In my view, the best way to assign homework would be to take a small feature or an interesting bu

I disagree with one click solutions for homework being viable. In my view, the best way to assign homework would be to take a small feature or an interesting bugfix a current developer already solved, and assign it to the candidate. Of course, this is tough if you want to keep your code secret and can't isolate the component/service/something source code from the rest of the system.

sytelus 8y ago
The core issue in interviewing is exactly this: asking a good efficient question! It doesn't matter if you use whiteboarding or homework or take a long walk together (Steve Jobs style). Most companies cannot expose their internal code base and expect someone to fix bugs in an hour of time. Ultimately you have to simplify the problem, chip away the unnecessary stuff and still it be good enough to evaluate candidate effectively. So if you think about this more deeply, you might realize that whiteboarding or IDEs or just talking is merely a medium to deliver the question and consume the answer. A vast majority of effectiveness of your interview doesn't depend on the medium but actual content of the question.