In the first round, they mainly asked about my previous experience - my responsibilities, day-to-day duties, and the types of projects I handled. In the second round, they focused on a technical deep dive into cloud infrastructure (best practices, Kubernetes, migrations, API Gateway). The second part of that interview included coding and Git questions, which didn’t seem very relevant to the actual day-to-day work
Scripting, Docker, AWS, Ansible and Terraform
Technical questions about infrastructure, kubernetes, and coding. Also about databases
What are they main drawbacks of load tests
Tell me about a problem and what you would do differently if you could do it again
Find the lowest common prefix.
lots of scenarios like questions. tell me a time you did, x,y,z very plain and robotic
Provided a diagram and asked to provide a high-level system design
What are the feature adoption methods that you have implemented in past. Then some generic questions post which the director tried scaring how unrealistic the targets are
There were three rounds 1. Immediate manager - Associate Director - Here they test your client-facing experiences & understand if you are tech savvy. They would touch on areas in CV which can speak to the above 2. Senior Director - Strategic questions, how would your prioritize you accounts, how would you predict churn etc. 3. VP - Value added questions. Strengths weakness, biggest loss & learning, how have you changed from your first job, what's your motivation 4. HR & final negotiation - testing team work & scenario based value added questions
Viewing 741 - 750 interview questions