The interview process consisted of multiple technical and managerial rounds focused mainly on current project experience, architecture, and cloud infrastructure expertise. The first two rounds were deep technical discussions covering system architecture, application design, scalability, API integrations, database design, cloud services, troubleshooting approaches, and real-time implementation scenarios from current projects. Most of the questions were scenario-based and focused on understanding the candidate’s practical exposure, decision-making ability, and architectural thinking. The third round was more focused on infrastructure and cloud architecture, particularly around GCP services and solution design. Questions included IAM, Kubernetes/GKE, BigQuery, Dataflow, CI/CD, Terraform, security, monitoring, cost optimization, and high-availability architecture. There were also discussions around handling production issues, deployment strategies, and best practices for designing scalable enterprise systems. Overall, the process was technical, experience-driven, and heavily focused on real-world architecture and implementation knowledge rather than theoretical concepts alone.

There was only 1 level of interview for me. I was from a product based company. I expected a Tech Lead or similar role but I was given associate manager. I'm a Java developer. I was asked to write few snippets of code in DSA and Java streams. Questions about deep internals of Java, multithreading, collections as usual.

Its was smooth. 3 rounds of interview . Mostly Managerial level questions were asked. Takes time in rolling out offer letter . Documentation process is tedious. They are strict on following salary bands