3 ms·
This is terrible advice for companies and interviewees. We've successfully used "homework" project when a candidate had potential, but didn't do well in-person
by gedy 8y ago
This is terrible advice for companies and interviewees. We've successfully used "homework" project when a candidate had potential, but didn't do well in-person for various reasons (nervousness, time pressure). In many cases we've hired them when they can produce something and talk over it afterwards.
Without this, they wouldn't have received an offer.
While I get they said "which are not sufficiently interested in them." but it's still an interview process to see if we should/should not hire.
- pmiller2 8y agoThis is something I support, provided the time involved for the candidate is roughly the same as the onsite interview. I can talk about code I’ve written in advance much more easily than anything can pull DP algorithms out of my ass on the spot.