I worked at a place where the test was always to toss a single web page together in 2 hours (candidates were free to spend more time but by 2 hours they had wri

I worked at a place where the test was always to toss a single web page together in 2 hours (candidates were free to spend more time but by 2 hours they had written enough code for us to weigh ability). The candidate we ended up hiring did _not_ finish, because he spent his time documenting both his frontend and backend work. The thoughtfulness that went into each of his functions was apparent, and I knew right off the bat this was someone I could learn from. So I think there's a middle ground that both sides could be happy with, but maybe it needs to be more apparent that interviews are more about the journey than the results (in fact, all 3 candidates we ever hired via this method did not have a complete solution, but had followed enough instructions to be close enough)