3 ms·
I agree with you somewhat, but couldn't you just as easily replace "unpaid weekend writing code" with: - unpaid weekend updating resume - unpaid weekend pract
by chucksmash 9y ago
I agree with you somewhat, but couldn't you just as easily replace "unpaid weekend writing code" with:
- unpaid weekend updating resume
- unpaid weekend practicing algos
- unpaid weekend browsing job sites
just as easily? I don't think asking job seekers to be interested enough to give a work sample is an undue burden. If that filters out people playing the numbers by applying to every opening...is that such a bad thing?
- aNoob7000 9y agoIt depends on how far along the interview process you've gotten to with a potential employer and if this is a step away from being hired. If the potential employer is asking for code samples up front, I think that's a bad sign. Let us talk about the work environment, expectations of the position, and then we can focus on my tech skills.
- ng12 9y agoIt's a problem of scale. Spend half an afternoon skimming through CtCI (shouldn't need much more as a seasoned developer) and you're good for N number of job interviews. I'll take that rather than spend 4*N hours on take-home problems in addition to time spent on-site.
- morgante 9y agoIf I spend a weekend updating my resume, practicing algos, or browsing job listings, then that time is useful for all jobs I'm applying to and interested in. If I spend my weekend on a work sample assignment, it's only applicable for that one company which might very easily not give me a compelling offer or be somewhere I'd want to work. At this point, I'll only do work assignments if I'm already very familiar with the company and have reason to suspect they'll give me a compelling offer.