4 ms·
Yes; this can work well but its a little noisy as a signal. (There's plenty of room with this sort of assessment for personal bias based to creep in based on wh
by josephg 6y ago
Yes; this can work well but its a little noisy as a signal. (There's plenty of room with this sort of assessment for personal bias based to creep in based on whether or not you like the person).
My recommendation is to make a list of attributes you want in a good hire. (My list is something like: coding, debugging, communication skills, CS fundamentals, systems architecture, domain knowledge for the job, ...). Then spend 20 minutes with each of these areas brainstorming simple ways you could assess that skill in 20 minutes or so. (They're all assessable, but you need to get creative). Then after you've done that, design an interview from your notes.
If you've got 1-2 hours for the interview, you'll end up with something much better than just having a chat. (Though on the flip side, if you've only got 10 minutes for an interview, a question like you suggest can be great.)
- acjohnson55 6y agoTotally agree. This is the basic approach I advocate for (https://m.huffpost.com/us/entry/us_7973484 https://m.huffpost.com/us/entry/us_7973484). I'd further argue that one of the best bets is to get someone to tell you how they have applied a skill in the past, rather than to try to figure out how you can get them to perform a facsimile of the skill in 20 minutes.