Deutsche Telekom Devops Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Deutsche Telekom.
Deutsche Telekom
Devops Engineer
Mid Difficult Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical
Recruiter reached out and asked some basic questions. Then there was a technical round with detailed questions about Kubernetes and cloud architecture. It was quite challenging, and I couldn't answer some of the questions. After that, I didn't hear back.
Confirmed questions1 question
- Could you explain what RBAC roles are in Kubernetes?
Deutsche Telekom
DevOps Engineer
Mid Average Neutral experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Behavioral
The interview process involved three rounds. The first two rounds were technical interviews with a DevOps engineer, focusing on Linux commands and, for the second round, Kubernetes troubleshooting. The third round was with a Director, where we discussed my previous role and responsibilities, and my reasons for seeking a new opportunity.
Confirmed questions8 questions
- Tell me about your previous role.
- Can you show me some Linux commands?
- How do you use sed and awk for parsing?
Deutsche Telekom
DevOps Engineer
Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Technical Technical Technical
I applied via LinkedIn referral in June'23. The HR called me up to check my DevOps knowledge and experience since I had worked as a Support Engineer but had some DevOps knowledge from my 1 year experience. First, there was a 25 MCQs test in 25 mins on Hackerearth. Then, after 2 days, I had my first 45 min technical interview where they asked about DevOps profile, my previous experience (which was a weak point), and tools/tech knowledge. The interviewer suggested I take a placement course and get back to them. After 4 days, I had a second 45 min technical round, similar to the first but with different questions on Github, Ansible, Docker, Linux, and Jenkins. This interviewer was helpful and also suggested I learn Terraform. Two weeks later, the HR called for another technical round with the Director of Engineering. The questions were mostly for 2+ years of experience, even though they were hiring for 0+ years. He also suggested I get good hands-on experience before applying. After a week of no contact, I called the HR and was told they couldn't hire me due to a lack of skills and a not-so-good interview review.
Confirmed questions8 questions
- Which DevOps tools are you most proficient in?
- Can you explain the difference between git reset and git revert?
- How do you check the status of running containers in Docker?
Deutsche Telekom Devops Engineer Interview Questions
Quoted word for word from Deutsche Telekom interview reports.
“How do you check the status of running containers in Docker?”
Read reports →“What is an Ansible inventory?”
Read reports →“What would you do if the .pem key-pair login files for an EC2 instance were accidentally deleted?”
Read reports →“How can I revert to a previous commit (specifically the second of four commits) without creating new commits?”
Read reports →“Can you explain the difference between git reset and git revert?”
Read report →“What are process exit statuses?”
Read report →“What are the different Kubernetes deployment styles?”
Read report →“Can you show me some Linux commands?”
Read report →“How do you use sed and awk for parsing?”
Read report →Formats, difficulty and experience
Across all 7 Deutsche Telekom interview reports.