
Mphasis Devops Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 21 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mphasis.
DevOps Engineer
The interview process was smooth. Below are the rounds of interview which held for me: 1. Technical Round 2. Technical Round 3. Manager - Project : Explanation 4. Client interview 5. HR offer process
- Can you explain the basics of DevOps Tools, GIT, Jenkins, Ansible, and any client-specific tools you might have used?
- Tell me about the basics of DevOps Tools, GIT, Jenkins, Ansible, and if there are any client specific tools.
- What are the basics of Devops Tools, GIT, Jenkins, Ansible and if there are any client specific tools?
DevOps Engineer
The interview process was quite organized, and they responded quickly. An HR person called me first, understood my strengths, and explained the role well. However, the interviewer was really bad, they should really set some standards for how they conduct interviews. I found the difficulty level to be stupid. When asked a question, I politely refused, stating that in real-time, I would mostly use references or documentation, and we should automate manual tasks. The interviewer, however, insisted that even though that might be correct, they have many builds to do and I should memorize it. They even asked me to take time to memorize all the options, which I politely declined. This definitely raised red flags about the project and the organization's processes.
- Can you list the options visible on the left side of the Azure DevOps webpage?
- What approach would you take for authenticating with Azure for a third-party service?
- Explain the steps to create a Service Principal in the Azure portal, including the specific UI elements and options you would interact with.
DevOps Engineer
They said there would be 3 rounds: 2 technical and 1 managerial. The first round covered everything on my CV, and I passed. The second round went deeper into my technical skills. The third round was supposed to be managerial but turned out to be a long, 1-hour technical interview on Docker, Kubernetes, and Jenkins, which I also passed. Then they mentioned another managerial round. This was a 10-minute chat about me and my knowledge. After two follow-ups, they told me I didn't clear the last round, based on that 10-minute non-technical chat.
- Questions from every topic mentioned in my CV
- Questions from depth of my technical skills
- Deep technical interview on docker kubernetes and Jenkins
Mphasis Devops Engineer Interview Questions
Quoted word for word from Mphasis interview reports.
“Factors, Numbers, decimal fractions and power?”
Read reports →“Can you describe the architecture of K8s and its components?”
Read reports →“Explain the steps to create a Service Principal in the Azure portal, including the specific UI elements and options you would interact with.”
Read reports →“Can you list the options visible on the left side of the Azure DevOps webpage?”
Read reports →“What approach would you take for authenticating with Azure for a third-party service?”
Read report →“What are your thoughts on Azure PaaS?”
Read report →“Time, Speed and Distance & Time and Work?”
Read report →“What are the basics of Devops Tools, GIT, Jenkins, Ansible and if there are any client specific tools?”
Read report →“What do you know about Terraform?”
Read report →Formats, difficulty and experience
Across all 21 Mphasis interview reports.