I applied online. The process took 3 weeks.

The interview process is lengthy, with at least four rounds, but communication is clear and well organized. Before each stage, you receive an email explaining what to expect. My main advice is to prepare carefully for the system design interview, as its focus may differ from what you expect. In my experience, the questions were heavily focused on infrastructure—a focus that was not mentioned in either the job description or the preparation email. I had prepared for application-level system design discussions, but most of the questions centered on topics such as:

• How would you deploy an application on AWS?
• Which AWS services would you choose, and why?
• How would you deploy an application in a private cloud?
• How do proxy servers work?
• How would you secure files stored in S3?

By contrast, we did not discuss topics I had expected, such as handling concurrency, preventing double bookings, designing APIs, or securing them. This unexpected shift in focus made me nervous during the interview, as I had prepared for a different type of discussion. Clearer guidance beforehand would have helped me feel more confident and better prepared. Overall, the process was well communicated, but the preparation guidance could have reflected the interview’s actual focus more accurately. If you are preparing, make sure you cover cloud infrastructure and deployment in depth alongside application-level system design.