I applied online and was invited for a phone interview a few weeks later. The interview was standard and was conducted by a software engineer and an executive. It was quite thorough but fair. You need to know your stuff.

A few weeks after the phone interview, I was invited to do a six-hour coding test. This test requires some preparation; it's fair, but if you get stuck on anything, you'll run out of time very quickly.

The deliverables are not just the source code but a fully working system. Therefore, you need to know a bit more than just writing code. They will send more information a few days before the test, so be prepared to use the time beforehand to practice and read all the information carefully. I was able to complete all the required parts but ran out of time for some of the extra credit sections.

A little over a week after the coding test, I was invited for a day of on-site interviews. The day began with a tour of the facility, which is absolutely amazing. Just that was already worth all the time I had invested up to then. After the tour, I had to give a 30-minute presentation to the entire panel. The rest of the day was filled with several one-on-one and two-on-one interviews.

Everybody was pleasant and cordial, but the questions were not easy, so you definitely need to prepare thoroughly. Questions ranged from pure technical programming and system design to more general engineering and management topics. There were no games or brain teasers, which I really appreciated. Be aware that even though you passed a coding test, you will still face technical questions during the on-site interviews. It's a long day, but it was also quite fun.

About two and a half weeks after that, I received a pretty sweet job offer.

Overall, the experience was great. It's a tough interview, so you really need to be ready and prepared to put in the time – it's not a quick process. The only thing I had to do was prompt the recruiting team every once in a while; they seemed very busy, so you need to take the initiative from time to time to keep the process moving.

There's an old book called "Sweaty Palms" that really gave me good insights (and your palms will be sweaty!), as well as a few books about coding and software manager interviews that were very helpful. Read them! Highly recommended.

Tons of technical and engineering questions.

Not one particular question stands out.