Veeam Software Devops Engineer Interview Questions
& Process

First, I had a chat with the recruiter who wanted to check my CV and see if my skills matched the job description. Then, I spoke with the hiring manager, followed by a technical interview.

The company seemed really eager, which was obvious when I had to reschedule twice and they didn't make a big deal out of it. Then, they said feedback would come by the end of the week, but the next day they emailed and called when I didn't respond right away. The whole recruitment was based on a false premise that I'd join two other DevOps engineers in a QA team, as a new addition, not a replacement. It turned out the role was for three different teams with separate managers, and there were no actual DevOps engineers in QA, just QAs trying to cover the DevOps duties. I suspect I wouldn't have found out until I started working there. They asked technical questions about VMware, Windows, Jenkins, and Ansible. I was honest about not having direct experience with some things, but my general problem-solving skills impressed the technical interviewers. It felt like a red flag when they seemed amazed by my general knowledge and intelligence. I decided to stop the interview process early because I discovered they had misled me. This suspicion stemmed from previous work experiences. Maybe it's better for other roles, but they only talked about this specific position and not about the general work experience at Veeam. Funny thing: they are fully remote in Poland now, but last year when they opened an office in Warsaw, they didn't offer remote work and couldn't find anyone willing to work in the office.

The hiring process for the DevOps role was enjoyable. It began with a LinkedIn message from the recruiter outlining the position and salary. We scheduled a 30-minute call followed by a one-hour online technical interview. The technical interview lasted just over one hour and provided insight into the team's expertise.