Qumulo Interview Questions
& Process

Started with a recruiter call, basically a get-to-know-you. They told me there would be about 6 more interviews, potentially up to the CEO. I interviewed with the hiring manager, then the director of engineering, then the VP of Strategy and Partnerships, then the SVP of North America. I was supposed to meet the CRO but couldn't make the schedules work, then I met the CEO for over an hour. The CEO said if I made it that far, I'd definitely get an offer. I reached out to the recruiter, and after a few texts, she said an offer was coming next week. I talked to the recruiter live 4 days later and she told me the role was changing to include more Public Sector/Fed stuff and there would be no offer. I told her I was frustrated and that this is NOT how serious companies do business. The recruiter then ghosted me after I expressed my frustrations.

The interview process felt slow and somewhat drawn out. It began with a friendly recruiter reaching out. After that, there was a series of individual interviews, with one happening each day. I spoke with the hiring manager, team lead, VP, and four different engineers. These interviews were mostly unscripted and conversational, though they did include some technical questions. After finishing all 8 rounds, I was told the decision would depend on the team's feedback. About a month after my final interview, even though I was really hopeful and pretty sure I'd get the job, I followed up and found out they were still looking for the right person.

The interview process involved a recruiter phone call, followed by a Zoom with the hiring manager. Then there was a take-home technical assessment for a full-stack app. After that, a meeting with the team (hiring manager, PM, engineer) to discuss the assessment and field questions. Next, an algorithms interview with a senior engineer, then a web-coding interview with the hiring manager. The process continued with a leadership interview with the CTO and a system design interview with an EM. I enjoyed the chats, questions, and problems. I always had time for my questions. But after finishing, feedback took 2-3 weeks, and then I got ghosted for another week until they said another candidate was selected. The whole thing took a month for feedback. I understand I could have done better in algorithms and system design, but other companies don't leave candidates hanging for a month without responding.

After an initial phone screen, I was invited to go through the full interview loop for the Scrum Master role. The communication was great and prompt. The recruiting team (Emily, Len, Rick) were really kind and professional throughout. I was prepared for a day of 1:1 interviews, where I would also facilitate a team retrospective and review agile artifacts with the VP of Engineering. The transitions between interviews were smooth, with short breaks and provided lunch and coffee. Each interviewer was engaging. The recruiter clearly outlined the post-interview process, including the timeline for decision-making and notification, which was accurate. The process showed rare diligence and humanity.