The interview felt rushed and tightly packed. It was scheduled for 1–2 PM, and while it started on time, the last part became a rapid-fire round of technical questions. I felt pressured and ended up saying “I don’t know” just to get through the final stretch, especially since I had to start work immediately after. They had said I’d have time to ask questions, but only 4 minutes were left by the end. I was hoping to learn more about the team I’d be working with, so it felt like a missed opportunity. I was also surprised to receive short notice the night before asking me to prepare two architecture diagrams of previous projects—even though the role was for DevOps Engineer, not a solution architect. The interview questions also spanned everything from infrastructure to architecture, suggesting that the team operates with very broad responsibilities and little role separation. To top it off, I followed up after the interview but never heard back—no update even two weeks later, which felt unprofessional and disappointing. Overall, the interview wasn’t terrible, but the experience felt rushed, unclear in expectations, and poorly closed out.

The process consisted of three interviews: an initial screening, a technical interview, and a final interview with the team. The initial interview focused on confirming your skills and experience. After that, you’re asked to prepare an architectural diagram of a system you’ve built or contributed to - something like a simple flowchart is sufficient. The technical interview centers around this diagram, with interviewers diving deep into different components. They clearly have strong expertise, so expect detailed questions. Topics included cloud technologies, AKS, system design, CI/CD, and general DevOps concepts. They won't ask questions that are clearly outside of the list of skills they posted in the job post or unrelated to the system you presented. The final interview was more of a casual introduction to the team. Overall, all interviews were conducted in a relaxed manner. The technical portion is challenging, but manageable if you have a solid understanding of the system you’re presenting - which you should, since it’s based on your own experience.