Technical Interview
Also known as: Skills assessment interview
A technical interview is the part of a hiring process that tests whether a candidate can perform the technical demands of the role. Depending on the discipline, it may involve writing or reviewing code, designing a system on a whiteboard, working through a quantitative case, debugging a fault, interpreting a dataset, or completing a practical exercise. Unlike a general conversation about experience, it puts the candidate in front of a real or realistic problem and watches how they solve it.
A good technical interview measures more than a correct answer. Interviewers look at how the candidate breaks a problem down, the assumptions they surface, the trade-offs they weigh, and how they communicate their thinking as they go. For senior and specialist roles — the kind common in GCCs across engineering, data, and R&D — depth of reasoning and design judgement usually matter more than speed or recall of syntax. Formats range from live sessions to take-home assignments and, increasingly, structured pair-programming.
Technical interviews carry two well-known risks. Poorly designed exercises can test trivia or artificial puzzle-solving that has little to do with the actual job, and interviews that are too long or unpaid can push strong candidates to withdraw. The remedies are to draw tasks from real work the role involves, keep the burden proportionate, brief candidates on the format beforehand, and score against a consistent rubric so results are comparable and fair. Handled this way, the technical interview becomes the clearest evidence of quality of hire; handled badly, it filters for exam technique rather than capability.
Frequently asked questions
What is a technical interview?
A technical interview is a hiring stage that assesses a candidate’s job-specific technical skills through exercises such as coding, system design, case problems, or hands-on tasks. It verifies that the person can do the work, not just talk about it.
What happens in a technical interview?
In a technical interview the candidate works through a realistic problem — writing code, designing a system, debugging, or analysing data — while the interviewer observes how they reason, handle trade-offs, and communicate. The format may be live, a take-home assignment, or a pair-programming session.
How should you prepare for a technical interview?
Preparation means practising the core skills the role requires, working through representative problems out loud, and clarifying the format and tools in advance. Because interviewers assess reasoning as much as the final answer, explaining your approach clearly matters as much as reaching the solution.
What makes a technical interview fair and effective?
A fair, effective technical interview draws tasks from real work the role involves, keeps the time burden proportionate, briefs candidates on the format, and scores against a consistent rubric. Poorly designed ones test trivia or puzzles unrelated to the job and can drive strong candidates away.