Re:On asking job candidates to code
by Lawtonfogle on Tuesday March 15, 2016 @04:08PM
(#11292580)
>3. 2-week paid trial doing real work.
That could work for those without a job, but if I'm securely in a job, if I'm going to be switching to a 2 week contract, there needs to be a significant bonus attached.
It's #3 that makes all the difference: a task that means something, and makes it worth one's while.
Duolingo wanted a functioning nontrivial (albeit sparse) app, expected to take 10 hours to write. I found it amusing on its own, but interviewed & got multiple offers elsewhere in less time.
Re:On asking job candidates to code
by ThrustVectoring on Tuesday March 15, 2016 @05:20PM
(#11293101)
That's actually harmful for getting quality candidates - "hot" prospects nope out of the process when they get an offer elsewhere.
A clever option is emailing the recruiter at Duolingo with something like "hey, I've got a competing offer, so the 10 hour coding challenge is really not something I have time for at the moment. Is there any other way to proceed through the hiring process?" Either way they answer, you're okay with.
I did that before during an interview with a pretty good company overall and the employer refused to accelerate the process or make an exception and just stopped the process.
1. Phone screen amounting to about 45 minutes.
2. Skype interview with small code samples between two interviewers at 45 minutes each.
3. 2-week paid trial doing real work.
I had #2 yesterday and am currently waiting to hear back from them about moving onward.