I am very much in favor of a low time commitment project interview, something that takes maybe 3-4 hours to complete.
I've written a ton of code in my career, and 99% of it is wholly owned by the companies who I wrote it in the employ of, and I don't have the legal right to show it to anyone much less put it on public display. Some people would say the answer to that is doing OSS/other projects in my spare time... but I have hobbies, and other interests, and don't want to spend my whole life writing code.
Give me an opportunity at no cost to you and low (time) cost to me to show what I can do, and we will both be in a better position to evaluate each other.
the intensity of the project should ramp with the seriousness of both sides; we start with a 30 minute phone screen then a very simple 30 minute "make these tests pass" and then bring people in for a day of coding/chatting. requiring a project as a first-pass filter is a bit much to ask of candidates and interviewers.
Yeah, that's essentially what I meant. A coding challenge that takes a handful of hours as a post phone screen/pre onsite screen.. not the first step in the process :)
I've written a ton of code in my career, and 99% of it is wholly owned by the companies who I wrote it in the employ of, and I don't have the legal right to show it to anyone much less put it on public display. Some people would say the answer to that is doing OSS/other projects in my spare time... but I have hobbies, and other interests, and don't want to spend my whole life writing code.
Give me an opportunity at no cost to you and low (time) cost to me to show what I can do, and we will both be in a better position to evaluate each other.