3 ms·
<rant> > the number of times an otherwise great programmer has submitted a 100 line behemoth (for something that should be less than 10) is unamusing. What ar
by PopeDotNinja 8y ago
<rant>
> the number of times an otherwise great programmer has submitted a 100 line behemoth (for something that should be less than 10) is unamusing.
What are your requirements? Short, terse, untested code? Objected oriented code? Bullet proof, modular code capable of handling a never ending stream of inputs?
Interviewers like asking questions that seem simple, but then they like to pile on unstated requirements, or judge code that was written sub-optimally on purpose as if it were production ready. Interviewers also don't usually have empathy for how badly interviewees have been treated by other interviewers, and how easy it is to get nervous as an interviewee when you find yourself talking to yet another interviewer with unstated expectations.
tl;dr...
- garbage in, garbage out
- we're all damaged goods, so be nice by just saying what you really want
</rant>
- ErrantX 8y agoIts a test given pre-interview to do in their time. 90 minutes, 3 questions. It is a gateway; candidates we want to interview a) can easily solve the problem and b) realise that its a 90 minute gateway test and therefore probably doesnt need to be gold plated. In baseline and control testing it has proven entirely effective in screening out the two extremes;those that cannot code and those that over engineer. (btw I agree with your overall sentiment; I put a lot of effort into making sure our interviews are friendlier, more effective and clear)
- PopeDotNinja 8y agoThanks. The context helps.