Barracuda Networks Interview Questions
& Process

The interview had two stages. First, a Senior SDET tested my technical skills. Second, it was a managerial round that focused on understanding my technical knowledge and behaviour through 'why' and 'what' questions.

The interview process involved 4 steps: first, an HR interview, then a line manager interview, followed by an interview with the Sales Director, and finally, an interview with the VP of Sales. It was of average difficulty, but the whole process took a long time, about 4 months from start to finish until the job offer was given.

It was a 3 round process. The first was with the recruiter, which was pretty easy. Then I had a second round with the manager, where we talked about my previous role and experience. He was a very friendly and easy-going person. We went over some common interview questions, and at the end, he told me I was moving on to the next round with his manager. She was also very nice. We went over some common interview questions again. I wasn't explicitly told what the next steps were, but basically, I got selected.

So I got this job through a recruiter. First, there was a call where they asked for basic info like my current job, when I can join, salary expectations, and years of experience. Then, another phone call to check my basic Linux skills. A few days later, my first technical interview happened. The interviewer introduced himself and talked about the company. Then came the usual 'tell me about yourself' question, where I talked about my internship and current role, and they asked some follow-up questions based on my experience. I was interviewing for a C++ role, but they were actually looking for a C developer. I mentioned I had some C knowledge and would try. They asked about C structures, memory, and pointers, and a coding question on bit manipulation. Things got tricky when they brought up multi-threading and synchronization, which I had no experience with, so I couldn't answer those. The feedback was that I did well in C++ and most questions, but they needed someone with multi-threading experience in C. The weird thing is, the job description said C/C++, Python, or Java were fine, and didn't mention C specifically or multi-threading. If they had, I would have prepared for it.