3 ms·
Summary: first interview the candidate to check for culture fit, then pay them to complete a 10-20 hour project. If the culture fit is good and project successf
by mfonda 13y ago
Summary: first interview the candidate to check for culture fit, then pay them to complete a 10-20 hour project. If the culture fit is good and project successful, hire.
As a developer I don't like the idea of having to do a 10-20 hour project as part of an interview, but at least they are compensated for it. I would love to hear thoughts from developers who have done a "project as an interview". Positive or negative experience?
- johnjlocke 13y agoIt happens all the time. Nothing to be afraid of.
- dougk16 13y agoI've done two projects-as-interviews for two different jobs, one paid, one not, both a week deadline if I recall, and around 20 hours. These were both in the midst of applying to a bunch of jobs, getting the interview based on portfolio/resume, and then, due to anxiety, completely bombing out when the technical questions started, or when they sent the do-these-problems-in-an-hour test. I got both the jobs where I did the week-long projects. They took a while, but it was completely stress free, and allowed me to show what I can do under more realistic circumstances. I realize that some "rockstar" programmers might scoff at someone daring to take up so much of their free time, but these are the people who probably do well at the classical interview, so more power to them. Overall, I enjoyed the project-as-interview process. Two things though: (1) I was a youngin at the time without much responsibility. Ask me to do the same thing now, with a family, and it can't be longer than a few hours spread over a week or two, or I just don't have the time. (2) As an interviewer and fellow human being, I'm very respectful of people's time. I'm uncomfortable asking someone to commit so much of it, even though for me personally it was OK.