4 ms·
Thank you for your response! I hope you don't mind me asking some follow-ups. > we send them home with a set of 5 coding tasks. How do you provide these tasks
by zizee 6y ago
Thank you for your response! I hope you don't mind me asking some follow-ups.
> we send them home with a set of 5 coding tasks.
How do you provide these tasks? Via email? Links to GitHub repos?
> come back and conduct a code review of their code with our team
How does that usually work? Does it happen in their editor of choice? On a company machine or theirs? Do they submit a PR? Do you take a look at their submission before inviting them back in?
> They take as many days as they need
Is there an expectation that they would spend days or effort? Or just a few hours? Do you try and adjust expectations of code quality for the time they dedicated to the problem?
> So far, we've had nothing but very strong hires with this approach, and the applicants have all said they very much appreciated how we roll.
That's great to hear it's working so well. Thanks again for the thoughtful response.
- 11thEarlOfMar 6y agoThe five tasks are sent via e-mail. It's about 2 pages. Code reviews are casual. Usually, they plug a projector into their notebook and show us their code in whatever editor they wrote it in. We have 3-5 engineers in the room, they ask questions about the code structure and approach. It's been respectful and positive. We give them days because most are full-time employees and in many cases have long work days. Giving them flexibility allows them to fit the work into their schedule. Note that most wind up spending much more than the 2 hours and in many cases, take the task much further than is required. We've had 2 hours as the least and in one case, 12. We keep the ask small to respect their time, but love to see them get engaged with it.
- zizee 6y agoThat's great info. Really appreciated, thanks!