[on_and_off]

This is why we use a timer on our take home exercise.

You are only supposed to spend 6 hours on it, we give a 24 hours timer so you are not too pressured for time (you can take breaks, have diner, a walk, etc) .

So far it works pretty well.

I have not yet seen any applicant writing tests. Just delivering the project with the requested features and acceptable code (no memory leaks, crashes, unreadable mess, etc) is more than enough to go to the next step.

If you demonstrate enough proficiency during this step, we will probably skip most tech questions and focus on fit in the next step.

[janephilipps]

This seems like a good happy medium type of take-home challenge. Out of curiosity, how many applicants have you had?

[on_and_off]

Wow, I don't know, I would say 5 challenges / week.

That's our third step though, first our recruiters filter applications (I have no idea how many people are funneled out at this point)

Then we have a 30 minutes phone call to discuss experience and presell the company. We also try to answer all their questions at this point and explain the challenge. Something along the lines of : "so the next step will be a take home test. We just want to see how you code, don't put too much pressure on you, just do your best in the time given"

Historically we have only been looking for pretty senior engineers, although we are relaxing this a bit.

The company has also been sponsoring a lot of visas (even with very interesting salaries, senior mobile engineers are hard to recruit .. most of them are already happy where they are), I think that take home are a good way to handle this case.

The applicant can take the exercise whenever he wants (the only limitation is that we might not be available to answer their questions in the middle of the night) and shows us what they can do.