3 ms·

I also kind of agree. If I do something for you, it's nice if you do something for me. So if I put work in to thoughtfully apply, I'm kind of expecting you to

I also kind of agree. If I do something for you, it's nice if you do something for me. So if I put work in to thoughtfully apply, I'm kind of expecting you to do more work than flinging a coding exercise at me. As a recruiter, I saw companies spam every candidate with a coding exercise only to never review many applications w/ completed exercises.

meesterdude 9y ago
> I saw companies spam every candidate with a coding exercise only to never review many applications w/ completed exercises. this is my experience - and why i don't do them out the gate. Because there's a strong chance my work won't even be seen or reviewed - and i have had this happen enough times to know that i should just say no.
bartread 9y ago
> As a recruiter, I saw companies spam every candidate with a coding exercise only to never review many applications w/ completed exercises. I'm really sorry you had that experience. For what it's worth I've sat on the other side of the fence: spent a couple of hours working on something only to hear nothing in response. It sucks. I hope I made it clear above, but my very strong recommendation is that if somebody has sent in a solution to a coding assessment, then you should be taking the time to give them personalised feedback rather than some stock response. If that didn't come across then I apologise.