What to expect:
1. There will be up to 4 one on one interview sessions of approx. 1 hour each.
2. Some of the interviews will be conducted in English.
3. We will ask you about your previous experience, test your coding skill, look at your software engineer knowledge and see your attitude:
Your past projects, we expect you to reasonably explain the system and why you implement that system. Having the necessary understanding why you choose a particular technology is very important.
For coding session, you will be asked to implement a data structure (for example: arrays, strings, linked lists, hash tables, stacks, queues, trees) or an algorithm (sorting, searching, recursion). If you already master a scripting language (Python), you should have an advantage here. If you are going to use C/C++, you will still be OK, but beware about all of the memory allocation and deallocation inconvenience. Think about how to handle the errors and how to structure the APIs, too, if you are heading for a senior position.
We also expect you to reason about memory and complexity trade-off because embedded software is often resource-constrained and you will face trade-offs when designing software for embedded systems.
Knowledge about the languages you use is very important, too. If you know C, we will expect you to go in-depth on how pointer works and why pointer is used. If you know C++, we will tell you to explain why a destructor should be virtual and should throw no exception. If you use Python, you should be able to tell us about the difference between a set, a list, and a tuple, and in which data structure they are implemented.
There will be questions about cache, memory, computer buses and network, and how operating systems, such as Linux or FreeRTOS, work. For example, SRAM, DRAM, UART, SPI, thread, process, DMA, virtual memory, TCP, UDP, etc.
If you have any other special related skills beside software crafting such as schematic drawing, board layout, CAD software, continuous integration/delivery (CI/CD), knowledge in AI, IoT, etc. please tell us in advance. We will try to arrange an interviewer who can assess that skill. But do not be disappointed if we do not ask that in the interview.
4. Beside that, there may be questions related to your aptitude and cultural fit. Here are what we value at Axon for your advance reading.

Some tips:
1. Don't think about the questions as challenges, each of them will be like a small problem which the interviewer and you will discuss and solve together. Speak up on your thoughts, discuss with the interviewer about the directions, be specific, and tell them the assumptions you want to make.
2. However, please stay focused and follow the lead of your interviewer. Time for the session is limited, both you and the interviewer need to deliver some results for the problem.
3. Feel free to speak out if you wish a few minute break or use the restroom between interview sessions.
4. The interviewers will be your colleagues when you join the team, so take this chance to get to know each other, try to relax, ask questions back.
5. Here at Axon we are a pretty casual bunch. You might see some people in button down shirts and/or t-shirts and jeans. So we recommend wearing business casual—but in all honesty wear what is comfortable for you.
7. If you’re interested in learning more about preparing for coding interviews, we recommend these resources:
Cracking the Coding Interview by Gayle Laakman McDowell
Elements of Programming Interviews by Adnan Aziz
8. Check out Axon Vietnam Facebook Page for more information about our Vietnam team!