Quote:
Originally Posted by spike021
That sounds like a great idea! I do know a lot of people around here dislike take-home style challenges. I feel 50/50 about those too, but done the right way they're much better than someone just being on the phone watching you code via a screen.
I haven't handled the initial challenge for my team, usually I'm part of the on-site interview panel. But I try to take an (subjectively, I suppose) easy problem that really is very easy, and then once a candidate can finish it, I build in the complexity (what if this input is too large to store in memory, etc.) and have them refactor to meet different ends. Helps me see what their mindset is, if they will ask questions that might be useful later from the beginning.
I know a lot of people would say it's too easy a question. But IMO a lot of the time those same people think they're asking easy questions that candidates should be capable of solving, that are really actually quite difficult ones.
It's definitely a tough situation.
|
Considering you’re involved in the whole interview process for software engineers and jobs of that nature, got any tips? Things I should try and focus on as I’m going through university that’ll help me in the long run? Still in first year but I’ve already done major programming (mostly games) and always wonder what else I’ll need to do to be competitive