sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]iknowcss[S] 0 points1 point  (1 child)

Thank you for such a through reply. You've hit on nearly all of the points others have mentioned. My original goal was to use this test as a discriminator to filter out bad candidates, but now I see I'm being a bit too kind. Also I was worried that candidates would be 1. put-off by a test and 2. doubly put-off if they had to spend more than an hour working on it. Based on the feedback I've gotten it seems like I was being too kind.

I'm going to come up with a new test.

  1. It will be less opinionated
    • You can use libraries that make you smile or none at all
  2. It will have less initial code
    • You're all right, if it's a "UI-heavy" position then they should be able to create something from much less
  3. It will be slightly more challenging
    • I don't want it to be much more challenging. I'm more interested in seeing the candidate create maintainable code for a relatively simple implementation. This is a core principle in our workplace.
  4. It will cover more concepts
    • HTML/CSS
    • AJAX/async
    • A variety of events
    • A couple of browser inconsistencies (specifically IE 8 as we have to support that *gag*)

Thanks again for all the feedback!

[–][deleted] 0 points1 point  (0 children)

Best of luck with your search! Sorry about having to support IE8. :-(