DEV Community

Discussion on: Why I Stopped Interviewing with Companies That Require a Coding Test

Collapse
 
bradtaniguchi profile image
Brad

It's just daily work stuff.

When I think of daily work stuff I think of doing a feature and PR review.

A common alternative I hear to a whiteboard interview, or a coding challenge is a take home project.

A take home project can not only test more relevant skills, it also provides a more real-world experience for everyone. With PR-like feedback the experience would also provide a similar setup to a work environment, and allow you to uncover all those problems you described above.

This is all without all the stress you'd get from needing to code/solve a problem immediately while someone else watches.

I'm not saying all companies should do this, or that all companies could do this, but it does seem more reasonable and relevant than dropping someone into some "test environment" and pointing out the similarities, rather than just putting them into a real world "work environment" and having a guardrails setup (fake inputs, fake data, relevant but fake project).

Thread Thread
 
skyjur profile image
Ski

With take home tasks problem is that some candidates would spend 1 hr others might spend whole day.

Thread Thread
 
ingosteinke profile image
Ingo Steinke

exactly the same will happen when they are part of your team, no matter if they work from home or sit in an office. Doesn't matter much when they deliver good quality.
Getting paid by time spent is not much better than getting paid by lines of code, but it seems to be the most common measurement in our business somehow.

Thread Thread
 
amantel profile image
Amantel

I think it's the other way around. Company is much more intetested in someone who can do a task in an hour, than in one that can do same stuff in 8 hours.