Whenever I interview someone, I try to follow these principles:<p>1) Simulate a real work environment. This means a dev machine with full access to the web. One thing I&#x27;m looking for is how good the candidate is a finding information they don&#x27;t know.<p>2) Customize the questions for the job at hand. A software tools dev is a very different position a firmware dev. I wouldn&#x27;t, for instance, expect a firmware dev to know much about regular expressions. And I wouldn&#x27;t expect someone interviewing for a scripting job to know much about alignment on ARM.<p>3) Test your questions on coworkers and friends. You need to get a baseline. Is there enough time to answer the question? Are people coming up with wide spectrum of solutions, or do you keep seeing the same response over an over? Are there parts of the problem that people find unclear?