The interview had two phases, an informative phase and a technical phase. The technical interview is based on a code challenge that the company sends you to do, the challenge was to build a simple application in Angular, but it forces the candidate to implement concrete concepts of the framework. This code challenge takes between 2 and 4 hours and is available 24 hours before the technical interview. After this challenge, it is reviewed with two people from the company's engineering team. Here, the objective is to analyze the solution, understand whether approaches and best practices were used, and know why something was done in a certain way and not another.
I'll give an example of an interview for an Angular developer, it's important to know how to do it but even more important is why you should do it this way and not any other way. For example, they pay attention to code organization, folder, and file organization, decisions about creating components when necessary, subscription management, etc. This is critical in interview preparation, but it is a very calm and pressure-free interview. I think the investment of time is worth it if you have enough knowledge of the technology in question.
