Beekeeper Interview Questions
& Process

The interview process included an initial screening call with HR. The focus was on previous career path, motivation for the role, and situational questions about customer success, communication, and business understanding. There were also questions about personal decisions made in the last year and how these experiences are transferable to the CSM role. The conversation was structured, professional, and time-efficient.

I went through a really poor experience. I passed two presentations for the final stage, which was all theoretical. They told me my approach was sound in the final interview and gave no feedback about any gaps, but I was rejected for not having 'enough relevant experience'. This was surprising since my experience should have been evaluated earlier. The recruiter was professional and nice, but the whole process felt like a waste of time because of the lack of transparency and consistent evaluation.

The interview process wasn't too bad, but it felt like they were searching for an engineer who could do everything. There were also some concerns about the company culture. The initial interview was technical, involving the VP and another DevOps engineer. I started by asking how strictly they adhered to the listed job requirements, as I didn't meet all of them, which is usually something discussed in an initial HR screening. They specifically mentioned needing 'proficiency'/'mastery' in DBA roles. I clarified that I have basic experience with query optimization and DB maintenance, but they decided to proceed. It turned out that logical thinking was sufficient to answer their questions, which seemed to relate to early product development challenges. This was similar for performance tuning and observability questions. Other questions covered platform, infrastructure, and networking. Some were insightful, like what I dislike about Terraform. Meanwhile, I noticed another job posting from them with a higher salary range. They didn't give a direct answer when I hinted about potentially seeking more, but seemed to understand. The next stage was a live coding session with a developer, which was a positive experience. It focused on general programming and thought processes rather than strict coding or algorithms. I could use the internet but had to explain my thinking. After that, I was given a take-home assignment and could choose a meeting date, which also served as the submission deadline. They struggled to clearly explain that a task expected to take a few hours was given a 3-day window, similar to the 60-minute interview structure. Finally, after I agreed to a meeting, they canceled the process, stating they found someone else who was under more time pressure. It's amusing they were so specific about finding an expert yet ended up choosing someone eager to start immediately.

There were 3 phone interview rounds, all with engineers, no HR. The first was a behavioral interview to gauge cultural fit. Next, a coding interview where I had to write and run a simple program, and if time allowed, write tests. This was done on my own IDE to check practical skills. The last one was a technical interview focused on networking concepts like HTTP and general web workings. If I passed these, I was invited for a 'test-day' at the office. This involved spending the day working on a specific task using the company's tech stack, with direct engineer support and the opportunity to ask questions. I really enjoyed this part, it felt better than typical in-house interviews. The day concluded with a presentation of my work and suggestions for improvement. It was essentially a 6-hour hackathon, which my previous experience helped with.