I recently interviewed with S&P Global for a DevOps Engineer position. The initial screening round was fairly standard, covering background, experience, and general DevOps knowledge. However, the technical interview that followed was unexpectedly challenging and frustrating. The session was conducted by two engineers based in South Asia. Instead of focusing on DevOps-related skills, the job description, and relevant tooling (such as CI/CD pipelines, containerization, infrastructure as code, cloud services, etc.), the majority of the questions were deep-dive Python programming challenges, the kind you'd typically expect in an interview for a Python Developer role, not DevOps. I clarified multiple times that while I do work with Python and scripting in my role, I am not a Python software engineer. Despite repeating this, the line of questioning didn’t change. It felt more like a misaligned technical screen, possibly suggesting they were not seriously hiring for the role. The experience did not reflect a clear understanding of what the DevOps discipline or the job description actually requires. I’d recommend aligning the technical evaluation more closely with the stated role and creating a more relevant and constructive interview process.

The process started with a phone screening after which for technical interview, there was a panel of people taking the interview, they asked relevant questions to the Job and also inquired about past experiences from CV.

The interview was very good. The panel was very experienced and understood the field very well. It was a pleasant experience overall. Questions were all related to the core field and my pervious experience.