4 ms·

This kind of thing is why the best "code interview" I ever had involved being given a problem (in this case, a small message sending/receiving library) and told

by zyxley 12y ago

This kind of thing is why the best "code interview" I ever had involved being given a problem (in this case, a small message sending/receiving library) and told to work on it over the weekend.

azatris 12y ago
Same here. I've had two of these and they are just so enjoyable, not to mention the incredibly positive feedback.
nothrabannosir 12y ago
This type of work-intensive interview gets old real fast when the umpteenth company declines. I fully understand the pros of looking at a more comprehensive, realistic body of work. But if that's what you're looking for; I got a whole Github profile full of stuff to discuss. Spending every weekend on yet another throwaway application until you get hired; I'd rather not. EDIT: removed some bitterness. :)
- yason 12y ago
  I would assume that a longer programming task would only take place in the very final rounds of interviews, where it's clear that the candidate is a potential hire and the company just wants to be sure that the candidate can do non-trivial work, walk through his code, have it reviewed and discuss the problems found. Starting with a programming problem that takes hours is simply being lazy from the company's part. It's easy to hand out and review but a lot of work for the candidate.
  - personx 12y ago
    that's the dream but there are some companies which send out their pre-baked "weekend projects" after the initial hr screening and I'm talking about large corporations (the new york times for example) which isn't terrible at first but results in lots of trying to look up what practices the company in question follows and prefers and what they are actually looking for personally I really need human feedback rather then 8 hours at my desk guessing and searching for what's being looked for it's one of those situations where I see the value for the interviewer but as the applicant it's completely sucks especially when you have 4 sample projects to write at home while juggling phone interviews and you know having a life/job
- meowface 12y ago
  It's the lesser of the other evils, I think. It's very important that the company is transparent about this process before you even apply, though, so that they don't waste your time and their own time. That way at least you know exactly what you're getting into before you submit an application. If you're sick of work sample tests and if the company clearly mentions this, you can move on and apply elsewhere. Matasano (founded by tptacek) does a good job at this: http://matasano.com/careers/ http://matasano.com/careers/
leovander 12y ago
I got four hours to write a mini-game in C++ as long as I didn't use any libraries. I had a blast, especially since it was relevant to the field in which in the company is in.
ZanyProgrammer 12y ago
Yeah, but then that gets into the realm of doing a lot of work in your spare time for free, for a job you may or may not get.

by zyxley 12y ago

This kind of thing is why the best "code interview" I ever had involved being given a problem (in this case, a small message sending/receiving library) and told to work on it over the weekend.

azatris 12y ago

Same here. I've had two of these and they are just so enjoyable, not to mention the incredibly positive feedback.

nothrabannosir 12y ago

This type of work-intensive interview gets old real fast when the umpteenth company declines. I fully understand the pros of looking at a more comprehensive, realistic body of work. But if that's what you're looking for; I got a whole Github profile full of stuff to discuss. Spending every weekend on yet another throwaway application until you get hired; I'd rather not. EDIT: removed some bitterness. :)

yason 12y ago
I would assume that a longer programming task would only take place in the very final rounds of interviews, where it's clear that the candidate is a potential hire and the company just wants to be sure that the candidate can do non-trivial work, walk through his code, have it reviewed and discuss the problems found. Starting with a programming problem that takes hours is simply being lazy from the company's part. It's easy to hand out and review but a lot of work for the candidate.
- personx 12y ago
  that's the dream but there are some companies which send out their pre-baked "weekend projects" after the initial hr screening and I'm talking about large corporations (the new york times for example) which isn't terrible at first but results in lots of trying to look up what practices the company in question follows and prefers and what they are actually looking for personally I really need human feedback rather then 8 hours at my desk guessing and searching for what's being looked for it's one of those situations where I see the value for the interviewer but as the applicant it's completely sucks especially when you have 4 sample projects to write at home while juggling phone interviews and you know having a life/job
meowface 12y ago
It's the lesser of the other evils, I think. It's very important that the company is transparent about this process before you even apply, though, so that they don't waste your time and their own time. That way at least you know exactly what you're getting into before you submit an application. If you're sick of work sample tests and if the company clearly mentions this, you can move on and apply elsewhere. Matasano (founded by tptacek) does a good job at this: http://matasano.com/careers/ http://matasano.com/careers/

leovander 12y ago

I got four hours to write a mini-game in C++ as long as I didn't use any libraries. I had a blast, especially since it was relevant to the field in which in the company is in.

ZanyProgrammer 12y ago

Yeah, but then that gets into the realm of doing a lot of work in your spare time for free, for a job you may or may not get.