How to Prepare for a Technical Interview

Technical interview preparation is more than memorising questions. You need to understand the fundamentals of your field, explain your own work clearly, and show how you approach a problem you have not seen before.

01 — Understand the role

Before preparing anything, identify from the job description itself:

• The responsibilities
• The core technologies
• The technical areas you will be asked about
• The level of experience expected
• The kind of work actually involved

Preparing for a role you have not read carefully is how strong candidates prepare for the wrong interview.

02 — Revisit the fundamentals

Review the fundamentals relevant to that role. Depending on the position, that may include programming, databases, interfaces between systems, testing, cloud, data structures, general system concepts, and knowledge specific to the domain.

Depth in the areas the role names beats shallow coverage of everything.

03 — Know your own projects

You should be able to explain every significant project on your resume. For each one, prepare:

• What problem you solved
• Why you chose that approach
• What technology you used
• What went wrong
• How you resolved it
• What you would improve now

If you cannot answer the last two, you are describing a project rather than discussing one.

04 — Practise explaining

Technical knowledge is only useful in an interview if you can communicate it. Practise explaining complex ideas in plain language, without unnecessary jargon. Being asked to explain something simply is not a trick; it is the job.

05 — Practise problem solving

When given a problem, work through it in the open:

1. Make sure you understand it
2. Clarify the assumptions
3. Break it down
4. Explain your approach before writing anything
5. Implement or describe the solution
6. Test your reasoning against an awkward case
7. Discuss what you would improve

Interviewers are usually more interested in step four than in step five.

06 — Prepare your own questions

An interview is also how you judge the role. Consider asking about the responsibilities, the team structure, development practices, the technology environment, what is expected in the first few months, and how people learn there.

07 — Review after each attempt

After every practice interview, record the questions you struggled with, the concepts to revisit, where your explanation was unclear, and the technical gaps you found. Then practise again.

This is the step most people skip, and it is the one that makes the next interview easier.

---

Do not prepare to recite answers. Prepare to explain what you know and how you think.

Related reading: how to build a technology portfolio, and the training catalogue.