|
|
|
|
|
by glvn
2649 days ago
|
|
My team uses a coding test with a bit of a twist. We provide the candidate with a simple application such as an address book or Todo list. We then ask them to either implement a feature or fix a bug that we point out. The example uses current industry standards and practices and is built in a language that the candidate is applying for. Complexity varies depending on candidate, if it's a junior role we ask they implement a simple feature or fix a simple bug, more senior devs may be asked to implement something more complex or fix a harder bug. We usually have one of our engineer that is interviewing them pair with them for about an hour on the issue during which time they can use all tools at their disposal. Our process puts the candidate in a place where they can really show their skill, a real-world (or as close as we could get) problem with all the tools they would normally have. Additionally having just the one engineer pair with them for an hour or so usually gives us pretty good feedback as to not just coding skill but also as a general fit on our team. It takes a bit more time in preparation and the interview but it's been a good ROI for us. |
|