Fourth Round: This was managerial round. More questions on management/conflict/problem. The panel was having very senior people in post. they were very cool and I was bit nervous at the start bit later was comfortable. I do not know how the 1:30 minutes passed. few questions.. Q1: What will you do if someone not listening/doing the coding as per quality ?
Fifth round: This was the final round. This was taken by someone very senior in technical or architect level. He has technical and managerial questions. He gave a problem and asked the solution and testcases.
What is grep in linux?
Do you have experience creating permissions structures, multi-account management structures, and single sign-on in .
Azure DevOps CI/CD,Azure Services,Terraform and Docker
Tell us about a time you worked on a project and... (insert robot question here, boiler-plated)
1.what are sla and rca 2. technical questions on linux and kubernetes and aws networking
Looks like the people on the panel misunderstood what role they were interviewing for. Almost all questions were about IT architecture, probably the only thing the panelist knew and none about devops, cloud or engineering as the job title and role says
What is the purpose of parameters group in RDS
1rd HR - Go through the MBM principles of the KOCH, they will push you to next round. 2rd Technical: Small case studies. Even if you are mid level or average level C# developer you will clear it. Don't worry. Technical interview is not so tough. 3rd Panel: Some behavioral questions and about your current job. 4rd indian Panel(HR will take): Again know the MBM principles thats it. They don't know other than this and the HR who did this was recently joined and he also don't know much.
Viewing 61 - 70 interview questions