I do a lot of interviews and that's what we do for the more technical interview: * give a written problem description with some reading time * ask some

I do a lot of interviews and that's what we do for the more technical interview: * give a written problem description with some reading time * ask some questions about the problem and the tasks, so we all have the same idea what is needed * treat the candidate as a team member in the lead role, support him/her * let him/her explore the problem and a possible solution design using the whiteboard * support him/her * use a computer/ide to sketch an implementation while he/she has Internet access and can ask any question. There is not a single solution we are looking for. Let the candidate explore his/her approach. * interview team sees a mirror of the screen, and the candidate explains what he/she is thinking/doing * try to get something useful running with some tests written. A complete solution is not needed. Working, tested, well written code > full solution. * do a quick feedback/review round * if the candidate is junior, didn't get that far, but shows some promise, he/she gets the problem as homework and can send in a complete and tested solution within a week We like to see: good communication skills, teamwork and excellent coding skills. We know though, that the combination of all three isn't that common.