> How else are you supposed to assess a candidate's ability to do the job, if not to pose them a problem and watch them work? Unless the job is responding to p

> How else are you supposed to assess a candidate's ability to do the job, if not to pose them a problem and watch them work? Unless the job is responding to problems and being watched while you work, the argument here is that you're not actually assessing anything that's very useful. Most engineers/developers, for example, spend a lot of time thinking about a problem or trying out their ideas (many of which quickly get thrown out). If you do this in most programming interviews, you're going to fail them.