How to run an interview that convinces technical talent
In a tight market the candidate evaluates you just as hard. A good interview selects and sells at the same time.
Anyone hiring technical talent must realise the interview works in two directions: while you evaluate, the candidate decides whether they want to work for you. In a market where strong profiles have multiple options, the employer who selects and convinces wins.
Structure beats improvisation
Agree beforehand with all interviewers which three to four criteria are truly decisive and who asks what. Without agreements, everyone asks the same general questions and you decide afterwards on gut feeling, with the familiar pitfalls: the smooth talker beats the quiet craftsman. One structured one-hour interview says more than three vague introductions, and score against your criteria straight after the interview, before impressions fade and blur into each other.
Ask about behaviour, not theory
'How would you handle a breakdown under time pressure?' yields a socially desirable answer. 'Tell me about the last time a breakdown wrecked your whole schedule' yields a real story, with details you can probe: what did you do first, whom did you involve, what would you do differently now? For technical roles a short practical case on the work floor often works better than an hour of theory questions; you see immediately how someone looks, thinks and asks. Keep it short and relevant though: half a day of unpaid trial work scares good candidates away.
Sell the role honestly
Show the workshop, introduce the team and be honest about the less pretty sides: the ageing machine park, the peak periods, the standby duty. Candidates see through a story that is too good, and whoever is surprised after starting leaves again; then you've recruited twice for the same chair. Finally, reserve ample time for the candidate's questions; you often learn more from those than from your own list, and a candidate without questions is rarely a convinced candidate.
Decide fast and always communicate
There should be no weeks between a good interview and an offer. The best candidates are off the market within weeks, and a slow procedure reads to them as a preview of slow decision-making in the job. Agree at the end of every interview when the candidate will hear something, and stick to it, even when the answer is no. Every rejected candidate treated properly remains an ambassador; technicians know each other.
Frequently asked questions
How many interview rounds are ideal for a technical role?
Two, three at most: a structured interview with the manager and a technical check or tour, possibly followed by a short closing conversation about package and start. Every extra round costs days of lead time and raises the chance a competitor signs faster.
May I ask a candidate to do a practical test?
Yes, and for technical roles it is often the most predictive part of your selection. Keep it short (an hour is plenty), relevant to the real job and safely supervised. Explain beforehand what you want to see: it is about the approach and the questions someone asks, not flawless performance in an unfamiliar workshop.
Need help with your hire?
Tell us which technical role you're looking for, we'll gladly think along, no strings attached.