3 ms·
We always give some sort of programming test, usually a dumbed down version of a problem we've recently solved ourselves. You shouldn't have to spend more than
by Jemaclus 12y ago
We always give some sort of programming test, usually a dumbed down version of a problem we've recently solved ourselves. You shouldn't have to spend more than two hours on it, if that. Most of the time our applicants say they spent less than an hour on it. It also weeds out a non-zero number of people who aren't really super interested in the position.
- ufmace 12y agoThat sounds fine; it's more a question of the timing. I'm guessing you give your test before the in-person interview? That would make a lot more sense to me than doing it after, which they apparently did to OP.
- Jemaclus 12y agoYes, it's usually "homework" (i.e., send us your resume and your code sample at the same time). I have a "problem solving" task where I expect you to bang out an algorithm (as opposed to code) for the in-person interview. That's mainly just so I can watch you think out loud. I can teach you my project's programming language... I don't have time to teach you problem solving basics.