I'm curious about how common Leetcode and systems design interviews are becoming for DevOps positions, particularly at the mid and senior levels. Lately, I've received quite a few recruiter calls advising me to prepare for these types of interviews, which I haven't focused on before. My expertise is mainly in Docker, Kubernetes, CI/CD, Infrastructure as Code, Linux, and Cloud technologies. Can anyone share what a typical interview looks like for a mid-senior level DevOps engineer these days?
6 Answers
It seems like there's a split in the industry right now. Some companies stick to traditional tech interviews focusing on practical skills relevant to the job without the Leetcode nonsense. Others, especially bigger tech firms, are adopting that rigorous Leetcode style for all positions, which isn't always practical for DevOps roles. I honestly find it refreshing when I come across teams that prioritize hands-on experience and skills over algorithm puzzles.
You’re lucky! I’ve faced both ends of the spectrum—from coding tests that were all about DSA to practical tasks. It can be a real mixed bag.
There's a lot of pressure these days for coding skills even in DevOps, but I agree with the sentiment that it's somewhat pointless. We should be demonstrating our actual ability to handle real-world issues, not just passing arbitrary coding tests.
I'm considering a shift into Solution Architecture due to the mixed messages about coding proficiency. While I've got skills in cloud and Kubernetes, they still expect Python coding knowledge, which is tricky since I mostly deal with DevOps tasks. It's a tough spot to be in!
It sounds like you’ve got great skills; maybe just brush up on a few key coding concepts to feel prepared without diving too deep.
I know exactly what you mean. It's about balance—focus on your strengths but be ready to sprinkle in some coding review.
I've been working in tech for a while and never faced Leetcode-style interviews until recently. It’s becoming a trend for mid-senior positions at tech companies, but there are still many roles focusing on real-world skills instead. It's like a game of chance—roll the dice and hope your experience shines!
Exactly! It can really depend on the company culture, and understanding that is key when prepping for interviews.
Yeah, it’s a real shake-up. I’ve had interviews that felt like an endurance test rather than a skill check.
In my recent experiences, live coding interviews are the norm now, and they want you on camera doing coding challenges. I still think it’s a bit ridiculous to have to showcase my coding chops when DevOps is more about process and systems. Best advice is to prepare for both but always lean on your practical experience.
I recently went through an interview process where the focus was primarily on CICD, Kubernetes, and automation. However, I was hit with random Leetcode-style questions that caught me off guard since I've never prepared for those. It feels like expectations are inconsistent across the board, which is frustrating!
Totally get that. I had an interview where all I did was troubleshoot real-world scenarios. Makes much more sense than worrying about algorithms!