How to Prepare for a Technical Interview (UK Guide)
Technical interviews assess whether you actually have the skills your CV claims you have. They vary significantly by sector — a software engineer's technical interview looks nothing like an accountant's or a data analyst's. But the underlying preparation principles are consistent.
What a Technical Interview Is
A technical interview is any interview that tests domain-specific knowledge or skills, rather than (or in addition to) generic competency questions. It might involve:
- Live coding exercises (software development)
- Case studies or modelling tasks (consulting, finance, data)
- Portfolio review (design, engineering, architecture)
- Knowledge-based questions (law, medicine, accounting, specialist roles)
- Practical demonstrations (engineering, skilled trades)
Some organisations use dedicated technical stages separate from the competency interview. Others weave technical questions into a standard interview format.
General Preparation Principles
Review the job description as a study guide
Every technical skill listed in the job description is a potential interview topic. Use it as a checklist: which areas are you strongest in? Which need refreshing?
Know your own work deeply
Whatever you have listed on your CV — tools, techniques, projects — be prepared to discuss in detail. "I used Python for data analysis" invites the follow-up: "What libraries did you use, and what were the challenges?"
Understand fundamentals, not just tools
Tools change. Interviewers who want to assess genuine understanding often probe the fundamentals behind the tools you have used. Know the why, not just the how.
Practise out loud
Technical knowledge that lives comfortably in your head sometimes falters when you have to articulate it clearly. Practise explaining concepts and approaches as if to a non-specialist — this exposes gaps and improves fluency.
By Sector
Software Development
Coding interviews typically involve solving algorithmic problems using a programming language of your choice. Common preparation resources: LeetCode, HackerRank, Codewars. System design interviews require a different preparation — focus on distributed systems concepts, trade-offs, and architectural thinking.
Data Science and Analytics
Expect SQL questions, statistical concepts, and model evaluation discussions. Preparation should cover data manipulation (pandas, SQL), core statistical concepts, and business case studies where you explain your approach to an analytical problem.
Finance and Accounting
Expect technical knowledge questions relevant to the role: valuation methods (for corporate finance roles), financial statements analysis, accounting standards (IFRS vs GAAP), regulatory knowledge, or Excel/financial modelling tests. Graduate roles often include numerical reasoning tests as a precursor.
Legal
Interviews for solicitor or barrister roles test commercial and legal knowledge. Expect questions on recent cases, regulatory changes in the relevant practice area, and commercial awareness of the firm's clients and market.
Engineering (Mechanical, Civil, Electrical)
Portfolio-based discussion is common. Be prepared to walk through design decisions, explain the reasoning behind engineering choices, and discuss project outcomes. Technical drawing or calculation exercises may be included at some stages.
Consulting
Case study interviews are a distinct format: you are given a business problem and expected to structure your thinking, ask clarifying questions, develop hypotheses, and present a recommendation. Practise using established frameworks (MECE, issue trees, value driver analysis) without becoming formulaic.
Handling Questions You Cannot Answer
It is acceptable not to know everything. The best response to a question you cannot answer:
- Acknowledge that you do not know the specific answer
- Explain how you would find or work it out
- Demonstrate related knowledge that shows you understand the domain
"I have not worked with [specific tool], but I am familiar with [related tool] and would approach learning it by [method]" is a far better answer than silence or guessing.
After the Technical Exercise
In live coding or modelling exercises, narrate your thinking. Interviewers are as interested in your approach as your solution. A wrong answer with clear reasoning often scores better than a correct answer with no explanation.
Use CVCircuit to present your technical skills clearly and credibly on your CV — so that your application accurately reflects the knowledge you are ready to demonstrate in a technical interview.