How To Prepare for a Technical Interview
What to expect in technical interviews, how to prepare for coding screens, take-home tasks and system design, and how to perform well in remote technical interviews.
Key takeaways
- Find out the format first: live coding, take-home task, system design or a mix, and in which language and tools.
- Practise solving problems out loud; interviewers assess how you think, not just the final answer.
- Clarify the problem before coding, start with a simple working solution, then improve it.
- For remote interviews, rehearse in the shared editor or video tool you will use, with a reliable setup.
Technical interviews test whether you can do the technical work of a role: write code, analyse data, design systems, configure infrastructure or solve problems in your specialism. They can feel intimidating, but they follow recognisable formats, and preparation makes a large difference. This guide focuses mainly on software, data and infrastructure roles, though the principles apply to any technical assessment.
Step 1: Find out the format
Ask the recruiter what the technical stages involve. Common formats:
| Format | What happens | What it tests |
|---|---|---|
| Online coding screen | Timed problems on a testing platform | Problem solving and basic fluency |
| Live coding | Solving a problem with an interviewer, in a shared editor | Reasoning, communication, code quality |
| Take-home assignment | A small project completed in your own time | Realistic work, structure, testing, documentation |
| Technical discussion | Talking through past projects and decisions | Depth of experience and judgement |
| System design | Designing a system at a high level on a whiteboard or diagram tool | Architecture, trade-offs, scale (mostly mid-level and senior) |
| Data or SQL exercise | Querying or analysing a dataset | Data skills and interpretation |
Also ask which language you can use, whether you can look things up, and how long each stage lasts. Most companies are happy to share this.
Step 2: Review fundamentals for the role
Focus on what the role uses rather than trying to cover everything:
- Software engineering: core data structures (arrays, maps, sets, trees), common algorithms, complexity at a basic level, and fluency in your main language.
- Data roles: SQL joins, aggregations and window functions; data cleaning; basic statistics; explaining results.
- Infrastructure and DevOps: networking basics, Linux, cloud services, CI/CD, troubleshooting approaches.
- Front-end: the framework you use, browser behaviour, accessibility, performance basics.
The job description tells you what to prioritise. Role-specific interview guides, such as software engineer interview questions and data analyst interview questions, go deeper.
Step 3: Practise problems out loud
In live technical interviews, how you think matters as much as the answer. Practise by solving problems while explaining your reasoning aloud, ideally with someone listening or recording yourself. A reliable approach for each problem:
- Clarify: restate the problem, ask about inputs, edge cases and constraints.
- Plan: describe your approach before writing code.
- Start simple: get a correct, simple solution working first.
- Test: walk through examples, including edge cases.
- Improve: discuss how to make it faster, cleaner or more robust.
If you get stuck, say what you are thinking and what you would try next. Interviewers often give hints when they understand where you are.
Step 4: Prepare for take-home assignments
- Clarify the scope and time expected, and stay within it.
- Write clear, tested code rather than many features.
- Include a short README: how to run it, your assumptions, trade-offs and what you would do with more time.
- Check it runs from scratch before submitting.
- Be ready to discuss it: many companies follow up with a review call.
If an assignment looks like many days of unpaid production work, it is reasonable to ask about the scope. See take-home assignment tips.
Step 5: System design (for experienced roles)
System design interviews are open-ended. Structure your answer:
- clarify requirements and expected scale;
- sketch the main components and how data flows between them;
- go deeper into one or two areas, such as storage or caching;
- discuss trade-offs, failure modes and how you would monitor the system.
There is rarely one right answer. Interviewers look for structured thinking and sensible trade-offs.
Step 6: Prepare to discuss your experience
Technical interviews often include questions about your past work: a system you built, a difficult bug, a decision you would make differently. Prepare two or three projects you can explain in depth, using the STAR method for structure.
What interviewers usually assess
Many companies score technical interviews against a few common criteria, even if they name them differently:
- Problem solving: breaking the problem down and choosing a sensible approach.
- Technical correctness: a working solution that handles edge cases.
- Code or work quality: readable names, clear structure, reasonable tests.
- Communication: explaining your thinking and responding to hints.
- Collaboration: how you take feedback and questions from the interviewer.
A candidate who communicates well and reaches a good, slightly incomplete solution often scores better than one who silently writes a perfect answer.
On the day
- have water, paper for sketching and your notes nearby;
- join or arrive early and check the tool works;
- repeat the problem back in your own words before starting;
- manage your time: if a part is taking too long, say so and move on.
Remote technical interviews
- Practise in the tool you will use: a shared editor, an online IDE or screen sharing.
- Check your setup: stable connection, working microphone, a quiet room, notifications off.
- Keep talking: silence is harder to read on video than in person.
- Have a backup: a phone number to call if the connection drops.
Our video interview tips cover the setup in detail.
A two-week preparation plan
| Days | Focus |
|---|---|
| 1–3 | Clarify the format; review fundamentals for the role |
| 4–9 | Practise one or two problems a day out loud; review solutions |
| 10–12 | Mock interview with a friend or peer; system design practice if relevant |
| 13–14 | Prepare project stories; check your setup; rest |
Common mistakes
- Starting to code before understanding the problem.
- Working in silence, so the interviewer cannot follow or help.
- Aiming for a perfect solution and never finishing a working one.
- Not testing with examples.
- Pretending to know something; saying "I am not sure, but I would approach it like this" is better.
A question people ask
Can I use AI tools during a technical interview?
Only if the company explicitly allows it. Rules differ widely, so ask in advance. Using a tool without permission, even for small lookups, can end the process.
Next steps
Ask the recruiter about the format, then follow the plan above. For the non-technical parts of the process, see our guide to preparing for an interview. Looking for technical roles? Browse remote software engineering jobs or read how to find a remote software engineering job.