News for hackers. Stuff that matters.

A comment on Hiring Is Broken: What Do Developers Say About Technical Interviews?. Parent comment

Re:Hiring Is Broken: What Do Developers Say About Technical ... by grp000 on Thursday August 15, 2019 @08:04PM (#20710926)
I've had very similar experiences like this; the most similar was a supposed '2 to 3 hour' problem that had no time limit and no language restriction. I rushed through it (had an offer for another position with a decision deadline coming up), and it still took 12 hours. I made an error where I didn't capture all cases, which I was fine to be rejected on those grounds, but I got the exact same feedback for more modularity, and when the interviewer pointed out my 'mistake', it was clear they had no idea what the code was doing.
[ Parent | on HN ]
Re:Hiring Is Broken: What Do Developers Say About Technical ... by NeverFade on Thursday August 15, 2019 @08:22PM (#20711027)
Let's think about it for a second: reading code is hard. We all know that. Reading code in "whatever language" that you may not know at all is nigh impossible.

These companies get a ton of candidates and tell them all to submit homework assignments that take at least 5 hours (in your case 12).

Reading 12 hours worth of coding work is intense effort even when you know the language well. If you don't, it can take a multiple of that number of hours.

Some programmer got 10-20+ of these completed tasks dumped in their lap.

I can pretty much guarantee they never really took the time to read and review the code with anything close to sufficient care or attention. Doubly so if it's in a language they didn't know very well.

[ Parent | on HN ]