←back to thread

Please stop the coding challenges

(blackentropy.bearblog.dev)
261 points CrazyEmi | 2 comments | 15 Nov 24 15:32 UTC | HN request time: 0.4s | source
Show context
factotum ◴[15 Nov 24 16:04 UTC] No.42148112[source]▶
I'm fine with tests, but only if companies pay a standard fee (say, $100) for a dev's time. If a company doesn't respect your time during the interview process, it probably won't while you're on the job.
replies(2): >>42148170 #>>42148251 #
syndicatedjelly ◴[15 Nov 24 16:10 UTC] No.42148170[source]▶
This is such an out-of-touch and ridiculous thing to say
replies(1): >>42148266 #
factotum ◴[15 Nov 24 16:17 UTC] No.42148266[source]▶
And why is that? Do you not agree that time is our most valuable asset?
replies(1): >>42148376 #
exitb ◴[15 Nov 24 16:27 UTC] No.42148376[source]▶
Interviewing is a time investment for both sides. Should the company charge you to evaluate your skills?
replies(3): >>42148611 #>>42149235 #>>42150184 #
1. AnimalMuppet ◴[15 Nov 24 19:44 UTC] No.42150184[source]▶
If someone gives me a take-home assignment that I spend 4 hours on, there is no commitment of time on their side. They may decide to not even look at the results. They may spend five minutes on it.

That's exactly my problem with take-home code challenges. If I go to an interview, and they waste my time, they have to waste their own. But with a take-home assignment, they can waste my time without wasting their own. That may lead them to be more wasteful of my time.

replies(1): >>42150947 #
2. exitb ◴[15 Nov 24 20:57 UTC] No.42150947[source]▶
If that’s the case - sure. But that’s not inherent to code challenges. I evaluate results of challenges at work, they require 2-3 hours of candidate time and it rarely takes less than half of that time to fully evaluate and form a recommendation.