Hacker News new | ask | show | jobs
by theamk 2020 days ago
You give a very simple question, generous time frame (like a 40 minute slot for a 5-minute question), and prepare set of discussions / more complex scenarios. Also don't require compileable code -- getting all the syntax errors out is boring and stressful. Do the thing on the piece of paper, whiteboard, or online editor without compilation functionality. Tell them you don't care about exact function names or typos.

If the interviewee does not work well under pressure, they'll have 30 minutes to do the question. Hopefully they'll worry less during the interview, and perform better.

If the interviewee breezes through your question, you give them next, more complex variation ("and now you cannot assume X anymore"). Make sure you have a few of those.

Basically, don't be a computer. Your goal, as an interviewer, is to get the candidate to show off their skills. Putting extra pressure does not help with it.

(and yes, this is pretty scalable. we are still having a single meeting for each candidate)