3 ms·
I had an opposite experience - years ago, I drove 8 hours for an interview. Got there, was asked some basic perfunctory stuff that could have been done over th
by mgkimsal 13y ago
I had an opposite experience - years ago, I drove 8 hours for an interview. Got there, was asked some basic perfunctory stuff that could have been done over the phone (they knew I lived in a different state). I'd brought a printed portfolio (laptops weren't too common, wasn't sure if I would have wifi access, etc). I had printed code samples ready to discuss, and offered them, but was told "no, that wouldn't be fair to the other candidates who can't bring example code".
I was slightly flabbergasted to say the least. That said, I was offered a job (after a second 8 hour drive to meet the owner the following week), and I took it, and it was a pretty darn good gig for the first year. But... "not fair to the others" is just odd reasoning.
Like you, I think understanding if someone can do at least basic programming ('basic' relative to the skill level you're hiring for) should be a non-issue. How it's done - automated tests, screen sharing, etc - may be up for debate.
- rvivek 13y agoThis is true and a lot of people relate to automated testing as something to ask about hard competitive style programming challenges. It can be fun too. Eg: http://www.itasoftware.com/careers/puzzle_archive.html http://www.itasoftware.com/careers/puzzle_archive.html