Interview questions that show who technical candidates really are

Most interviews collect too many answers to too few important questions. This set is kept compact: per goal, one or two questions proven to reveal a lot, with what to read from the answer.

Technical insight

'Walk me through the hardest breakdown you ever solved: what did you see, what did you rule out, where was it in the end?' This single question shows diagnostic ability, depth and honesty at once. Whoever really was there talks about dead ends and doubt; whoever borrowed the story stays at the surface. Probe the details: which measuring device, which value, why that order? A variant for engineers: 'which design would you do differently today, and why?'

Collaboration

'Tell me about a clash with a colleague or manager: what was it about and how did it end?' Pay less attention to the conflict itself than to the tone. Whoever places all blame outside themselves will do the same with you. Whoever shows nuance can reflect. Additionally: 'who did you learn most from in your career, and what exactly?' The answer shows whether someone draws knowledge from colleagues, and will therefore share it too.

Motivation and direction

'What made your best working day of recent months good?' tells you more than 'why do you want to work here?', because the answer cannot be prepared. Then test whether your role can offer that kind of day; that prevents a mismatch that only becomes visible after the start. Whoever beams about independent hands-on work won't be happy in a coordination role full of meetings, however nice the title sounds.

Honesty about limits

'What are you technically least strong at?' Whoever gives a real answer here will also give you real answers later when a project threatens to derail. Whoever serves up a disguised strength warns you in a different way. Follow up with: 'and what did you do about it last year?' You immediately see whether someone works on their weaknesses or lives with them.

How to use the set

Ask the same core questions to every candidate for the same role; only then can you compare answers instead of impressions. Note briefly per question what you heard and score right after the interview, not in the evening. And guard the ratio: an interview in which the candidate talks seventy percent of the time is a good interview. Your questions are the tools; the candidate's story is the material.