3 ms·

> those who are competent and eager enough That's one way to put it! It's obviously none of my business, but I can't help but be curious whether you are curre

by j_s 9y ago

> those who are competent and eager enough That's one way to put it! It's obviously none of my business, but I can't help but be curious whether you are currently responsible for hiring decisions, and if so whether or not you use take home assignments, and finally if so whether or not it is paid for. Or perhaps as an employee the process worked out for you. In either case, more details documenting how take home assignments work best in practice would always be appreciated! A take home assignment beats many alternatives, but places the entire burden on the potential employee (employers love it!).

kylequest 9y ago
This is my position on both sides. I'll pick a homework assignment anytime when I have a chance as a candidate. I have lots of life commitments and this is one of the big reasons why I like it. I also like it because it's an opportunity to shine and be creative (it depends on the assignment, of course). Yes, it's not perfect because you can end up dealing with somebody who doesn't like how you comment your code or they don't like your tests... It's actually a good thing in most cases because it also filters out the companies where you wouldn't want to work anyways. It's an opportunity to have a meaningful and relevant conversation.
- j_s 9y ago
  > It's an opportunity to have a meaningful and relevant conversation. This sounds like the key and something many who complete take home assignments don't get. [edit] Thanks for taking the time to add a bit more context.
  - kylequest 9y ago
    Not all assignments are created equal. Like with anything it has to be well done. When I hire people I craft the assignments for each candidate depending on the role and the person on the other side. It's also important to communicate the expectations and the desired outcomes. And it's also important to give an opportunity to the candidate to have a follow up requirements discovery step where they can ask any questions about the assignment.

by j_s 9y ago

kylequest 9y ago

This is my position on both sides. I'll pick a homework assignment anytime when I have a chance as a candidate. I have lots of life commitments and this is one of the big reasons why I like it. I also like it because it's an opportunity to shine and be creative (it depends on the assignment, of course). Yes, it's not perfect because you can end up dealing with somebody who doesn't like how you comment your code or they don't like your tests... It's actually a good thing in most cases because it also filters out the companies where you wouldn't want to work anyways. It's an opportunity to have a meaningful and relevant conversation.

j_s 9y ago
> It's an opportunity to have a meaningful and relevant conversation. This sounds like the key and something many who complete take home assignments don't get. [edit] Thanks for taking the time to add a bit more context.
- kylequest 9y ago
  Not all assignments are created equal. Like with anything it has to be well done. When I hire people I craft the assignments for each candidate depending on the role and the person on the other side. It's also important to communicate the expectations and the desired outcomes. And it's also important to give an opportunity to the candidate to have a follow up requirements discovery step where they can ask any questions about the assignment.