4 ms·

What he is calling "spec work" would be better described as a "challenge project". I think these provide a lot of insight that you wouldn't have the opportunity

What he is calling "spec work" would be better described as a "challenge project". I think these provide a lot of insight that you wouldn't have the opportunity to receive via the standard portfolio/github and interview process. If you give a job candidate a small project (3-5 hours tops), you're able to see how they solve problems and most importantly, how they interact with your team. I've asked "A player" candidates to perform challenges, and I have happily performed them myself to get a job. And as a candidate, there have been a couple of time where I've realized via the challenge process, that I wouldn't want to work with a particular group. It's a smart use of time by both parties to quickly determine if the candidate is indeed a good fit for the position. Spec work, as in completing a project to receive consulting work, is an entirely different debate.

pbiggar 14y ago
I feel that companies should pay people to complete these "challenge projects". Once I interviewed with 3 different companies that asked for a challenge project, which were expected to take 2 days in one case, a week in another case. If you're paying, I'll do it happily.
- feverishaaron 14y ago
  I feel your pain. Two days to a week is "free work", not a challenge project. I too would respectfully decline if I wasn't getting paid.
stevoyoung 14y ago
I agree, "challenge projects" is closer to what I am talking about. To be clear, I not debating that it isn't useful for the employer. If the employee gets to interact with the team (which I think is rare) it could be useful for the employees too. I'm just suggesting that it's not necessary and the upside leans heavily on the employers side. Why can't you bring in an existing design / engineering problem into the interview and discuss it. This would give you more than enough insight into someone's technical chops and problem solving ability. I've done it when interviewing people and it's worked wonders. These types of conversations also gives you much more info on a candidate.

pbiggar 14y ago

I feel that companies should pay people to complete these "challenge projects". Once I interviewed with 3 different companies that asked for a challenge project, which were expected to take 2 days in one case, a week in another case. If you're paying, I'll do it happily.

feverishaaron 14y ago
I feel your pain. Two days to a week is "free work", not a challenge project. I too would respectfully decline if I wasn't getting paid.

stevoyoung 14y ago

I agree, "challenge projects" is closer to what I am talking about. To be clear, I not debating that it isn't useful for the employer. If the employee gets to interact with the team (which I think is rare) it could be useful for the employees too. I'm just suggesting that it's not necessary and the upside leans heavily on the employers side. Why can't you bring in an existing design / engineering problem into the interview and discuss it. This would give you more than enough insight into someone's technical chops and problem solving ability. I've done it when interviewing people and it's worked wonders. These types of conversations also gives you much more info on a candidate.