4 ms·
The proposed solution to me, is much worse. > Ask them to build something – anything! > Instead of a coding challenge, ask them to spend a short time building
by syspec 6y ago
The proposed solution to me, is much worse.
> Ask them to build something – anything!
> Instead of a coding challenge, ask them to spend a short time building something they enjoy, and talk about what they did and why.
To me this would be a MUCH more difficult task. A blank canvas is much harder to work with, and downright frightening. Constraints foster creativity.
Having everyone code the same thing helps the interviewer (who is also very busy and has many other things happening in their work life) gauge the different levels of the people applying easily by comparing them on the same task.
- cosmotic 6y agoThe difference is the interviewer is being paid for their time, the interviewee is not.
- ithkuil 6y agoThen pay the candidate! It might seem ridiculous but consider how much time is spent by interviewers, hiring committees etc, giving some fraction of that out even to utterly worthless candidates might not be the worst idea in the world. A side effect of this is that suddenly the cost of a bad screening becomes more intuitive
- ma2rten 6y agoThat would create the wrong incentives.
- justaguy88 6y ago"What do you do for work?" "Oh I just interview a lot, the pay isn't amazing but it is what it is"
- nhooyr 6y agoThat's a problem with the company. We at @cdr pay interviewee's $200 for their take home challenges.
- jordan801 6y agoThis is awesome. I have taken a number of code challenges and walking away with neither, compensation nor explanation is rough.
- gmadsen 6y agoheavily dependent on the job as well. not all software engineers are tinkerers solving basic problems in their lives. I code state of the art motion planning, localization, and robotic algorithms. some of this requires more than a day of tooling around at home building a project