I went to Google Munich for a position more focused on Frontend.

For me, I liked the process. Between phases, they gave me the time I needed to prepare for the interview.

In my case, it was a Screen Interview and the final interview, which consisted of 4 different interviews.

I was very happy with the Screen Interview. I thought the question could be applied to real life, and although I had to solve it with the techniques practiced with Leetcode, the fact that it wasn't so 'mathematical' and that the answer was more open-ended made it much easier for me to show the interviewer my problem-solving techniques, and I was able to explain all the solutions that occurred to me during that half hour.

In the case of the final interview, I wasn't as happy. There were 2 coding interviews, 1 frontend interview, and another cultural interview. The frontend one was good, but I wasn't happy with the two coding interviews. In one, I finished the problem and couldn't optimize it; in the second, I was 10 minutes short of finishing it.

Despite all that, I was frustrated because one of the problems I see Google has in interviews is that 50% of your experience depends on the interviewer you get. Unlike the screen interview, where I consider myself very lucky, in the two final ones, both barely spoke, and one of them even struggled to answer questions to confirm that I had understood the problem.

In conclusion, it was good, but the interview confirmed that I don't want to continue aspiring to a FAANG because it doesn't align much with my way of thinking.

In frontend, they will ask you questions related to asynchronicity, variable scopes, and especially controlling what functions of functions return.

As a complementary task, they might ask you to implement something in HTML that is accessible, interactive, and styled.