I'm asking this in the context of code tests that are used during the interviewing/hiring process.
There is a general consensus that generic code tests that are frustrating and time-consuming for the developers, but that it also doesn't give the company too much insight into someone's skill set.
One thing we thought of was to replace those tests with contributions (or bug/issue fixes) to a company's open-source project.
Obviously, if it were an easy to implement idea, more companies would be doing it already. And so we're trying to figure out what are the obstacles and barriers to this.
We also created a typeform survey in case you have a few minutes to spare (6 mins is the average completion time)
https://workshub.typeform.com/to/OqzTZS
There is a general consensus that generic code tests that are frustrating and time-consuming for the developers, but that it also doesn't give the company too much insight into someone's skill set.
One thing we thought of was to replace those tests with contributions (or bug/issue fixes) to a company's open-source project.
Obviously, if it were an easy to implement idea, more companies would be doing it already. And so we're trying to figure out what are the obstacles and barriers to this.
We also created a typeform survey in case you have a few minutes to spare (6 mins is the average completion time) https://workshub.typeform.com/to/OqzTZS