Panzura Interview Questions
& Process

The interview started with a discussion about my project, where they really dug into the test cases – how I came up with them, how I found edge cases, and how I made sure everything was covered. They also asked about any hurdles I ran into while testing and how I got past them. Then came some technical questions, like asking me to talk about test scenarios and the strategies I'd use to make sure the software was good quality. They also hit me with a question about memory management, specifically internal and external fragmentation. Finally, I had to tackle a coding problem: replacing duplicate characters in a string with a *. Throughout the whole thing, the interviewer was great about giving me updates and keeping things clear and organized.

So, they initially picked me for a Java Developer position. But then the interview shifted focus, and they started grilling me on OS topics like synchronization, deadlock, and inter-process communication. After that, they threw in some C and C++ questions, mainly around memory allocation. Finally, they wrapped up with a few Java-specific questions, such as why it's platform independent and what JRE and JVM are, along with method overloading and overriding.

The company was hiring freshers for the first time, and the whole interview process was conducted at their office. They invited students from 4-5 colleges that were shortlisted. The process kicked off at 10 AM. Everyone was welcomed by the staff, and breakfast was provided. The selection started with a written test, where you could choose between Java or C++ based on your preference. This test had questions on OOPs, pseudocode, one coding question, and a mix of MCQs and theoretical questions, totaling 9-12 questions. Out of about 70-80 students, roughly 20 made it to the interview stage, and 12 of those were from my college. I was one of them. Before our interviews, we got to chat with other candidates who had already been interviewed. They said most questions were scenario-based. When it was my turn, I was nervous at first, but I got more comfortable as we talked. They asked me questions based on my CV, including DBMS, OS, SQL, and Linux commands because I'd mentioned using a Linux-based OS. They also asked about my projects, but most questions were scenario-based, which I hadn't really prepared for. The interviewers weren't completely happy with my answers but were still supportive. There were supposed to be two technical rounds, but I didn't get selected for the second one.

I was first sent a technical challenge to do before the actual interview. After I completed it, I was notified that I passed and a phone interview would be set up. I went through with the first phone interview and was told I did well, and then a second phone interview with the director of support was to be set up. After waiting two weeks, I got the details for the second interview. However, just five minutes before it was scheduled, I got a call from a recruiter saying there would be no interview because they had hired someone else. When I asked why, I was told I didn't pass the tech challenge, which contradicted what I was told earlier. It really felt like they had someone in mind already but made me go through the process anyway, which is unprofessional.