LTIMindtree Devops Engineer Interview Questions
& Process

I applied for the DevOps Engineer role and the process was pretty good and organized. The HR team got in touch with me about a week after I applied. The first call was with HR and it was about my background and projects. The recruiter was nice enough to walk me through the entire interview process. Then, I had a technical phone screen where they asked some basic DevOps questions. This included stuff like Azure DevOps, CI/CD, and basic Terraform. They also asked about my scripting experience, like Shell or Python. The person interviewing me was really nice and encouraging. After I passed that, they set up a panel round for me. This last round was more of an intermediate to advanced technical interview.

The interview questions are centered around fundamental DevOps and cloud concepts, with a particular emphasis on Azure and Kubernetes. The process started with securing an AKS cluster using tools like role-based access control, network policies, and private API endpoints. We also went over managing Terraform state files, covering remote backend setup, encryption, and access controls. Then, questions about Azure’s availability and scalability strategies came up, testing knowledge on availability zones, autoscaling, and load balancing. Kubernetes autoscaling, including HPA, VPA, and Cluster Autoscaler, was another significant topic. A scenario involving managing both public and private VPCs with a single Terraform module was presented to gauge modularity and reusability. We also discussed Git architecture and branching strategies like Git Flow and trunk-based development, alongside Jenkins fundamentals, pipeline design, and its CI/CD setup. Networking questions covered Azure’s Virtual Networks (VNets), VPN gateways, and general connectivity. Further scaling concepts, specifically horizontal, vertical, and cluster autoscaling in Kubernetes, were explored. The interview also touched upon securing Azure resources using RBAC, Key Vaults, and Azure Backup. Finally, some Linux basics were checked, such as the role of the $ symbol in shell scripting, and a practical Git merge conflict scenario was given to assess problem-solving skills. Overall, the aim was to evaluate both architectural vision and hands-on implementation skills.

So after the HR interview, there were 2 more interviews. They asked basic devops stuff and then AWS questions, like boto3 and s3. The interviewers were nice. Finally, there was a salary negotiation, but I passed on it because the person negotiating seemed to lack empathy.