Interview questions that show who technical candidates really are
Not more questions, better ones. A compact set per goal, with what the answer tells you.
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 toughest 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. Those who were really there talk about dead ends and doubt; those who borrowed the story stay at the surface. 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.
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 can't be prepared. Then check whether your role can offer that kind of day; that prevents a mismatch that only shows after the start.
Honesty about limits
'Where are you technically least strong?' Whoever gives a real answer here will also give you real answers when a project threatens to derail. Whoever serves up a disguised strength warns you in a different way.
One closing advice: ask the same core questions to every candidate for the same role. Only then can you compare answers instead of impressions.
Frequently asked questions
Should I run a technical test or do questions suffice?
For hands-on technical roles a short practical test on the shop floor often says more than an hour of questions. Combine both: the interview for thinking and collaboration, a compact case for craftsmanship. Keep the test short and relevant; half a day of unpaid test work scares strong candidates away.
How many interviews are ideal for a technical hire?
Two well-prepared rounds almost always suffice: one substantive interview with the technical lead and one about collaboration and conditions. Every extra round extends lead time and raises the chance a competitor is faster.
Need help with your hire?
Tell us which technical role you're looking for, we'll gladly think along, no strings attached.