Where I work we do something similar but it&#x27;s a &quot;homework&quot; question we give to people who pass our initial resume screen (<a href="https:&#x2F;&#x2F;github.com&#x2F;maxmind&#x2F;dev-hire-homework" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;maxmind&#x2F;dev-hire-homework</a>). We tell them not to spend more than 1-2 hours on it. We decide whether or not to interview them based on the quality of the code they produce.<p>In the interview we ask things like:<p>* what is OO and how is it different from procedural programming? (high level conceptual)
* why do you want to leave your current position?
* what appeals to you about this job? what do you think you might like least?
* what is the purpose of testing?
* tell us about the programming languages you&#x27;ve used. what&#x27;s your favorite? what do you like most about it? least?<p>I&#x27;d rather have a more conversational interview after already having established their ability to code.