How to Interview Entry Level Software Engineers
This is generally fine but “homework” is a terrible idea (trend?) because it isn’t looking from the perspective of the new hire:<p>1. Unemployment can be extremely stressful and there is a <i>very good chance</i> the person needs a job <i>NOW</i>.  <i>Every</i> little thing you do to dilly-dally instead of making an offer is another hurdle that may send the applicant elsewhere.  Act as soon as possible when you see a résumé you like (get on the phone, find out what you want to know, make a decision; if you bring them to interview and they’re struggling, give feedback immediately; don’t have a system where you wait 3 weeks to tell them yes&#x2F;no).<p>2. Any effort you expect an applicant to spend will be <i>greatly</i> multiplied.  That person is <i>not</i> talking only to you, they’re looking at LOTS of job postings!!  If every potential employer starts assigning “homework”, it becomes a major hurdle and you can bet they’ll look a lot closer at an employer that might provide a paycheck in a couple weeks instead of “homework”.<p>3. You don’t need complex problems to understand if somebody can code.  Let them use whatever language their résumé claims they know, give them something to do for a few minutes and see what happens.  If they get stuck, give them a solid hint and again, see what happens.  You’re trying to assess things like (a) if they appear to know what their résumé claims, (b) if they are the kind of person you can interact with to get somewhere on a problem.