<aside> 👋 The technical interview aims to test your practical skills.
Companies have different approaches and methods. But generally, technical interviews involve writing code, designing systems, either as live interviews or take-home projects, and discussing your background and passions.
Below, we’ve set out some **general advice,** **format-specific pointers,** and **resources** to help you practise and prepare.
</aside>
Solve as many coding problems as possible, and practise explaining your reasoning to others. This will help you become more comfortable explaining your thought process, which is often just as important as the solution itself. At times, finding the correct answer may not even be that important…
Check out these online resources where you can practise coding before a technical test.
During the interview, make sure you're communicating clearly and concisely. Practise breaking down complex problems into smaller, manageable pieces, and explain your thought process as you work through them.
It is crucial to be able to analyze the time and space complexity of your solutions and explain why they have the complexity they do.
Be bold and ask questions to clarify requirements or understand the problem better. It is better to ask questions and understand the situation than to make assumptions and get stuck.
Show your interviewer that you're excited about the opportunity to work with the technology or company, and be open to learning new things.
If you don't know the answer to a question, be honest and explain your thought process of how you would go about finding the solution.
There are several different formats that technical interviews can take, including: