MongoDB Recruiter Interview Questions
& Process

The company has solid product and service offerings, respected by engineers. It's a good size, offering exciting work scope and variety. One interviewer emphasized well-being. However, the 30-minute interviews felt too short and rushed, not allowing time to break the ice. In one instance, an interviewer seemed to be reading my resume for the first time during the interview, and another didn't appear to have prepared questions, making it feel freestyle.

This recruitment process is a lot like a sales process. We'll look at your drive, motivation, and intelligence. Then, we'll check your qualification skills – like listening, empathy, and if your questions are relevant. We want to see if you can build champions in the company. Finally, we'll assess your closing skills, including your ability to give feedback and define next steps.

The interview process was straightforward, starting with a recruiter screening interview, followed by a loop of four one-on-one interviews with the hiring team. The process was alright; they have a really cool and handy candidate portal. However, the interviewers were quite poor. They attempted to emulate Amazon's Leadership Principles competency-based format but seemed to lack proper training. Their indifferent approach to managing questions felt disrespectful, as they demonstrated no understanding of the difference between neutral and professional versus indifferent and snobbish. They really need to improve significantly to reach Amazon's assessment standards. I wasn't offered the position, and to this day, I haven't received an outcome or feedback call/email, despite them sending an interview process feedback survey, which felt like gaslighting. If an offer had been made, it would have been an easy 'no.' The team appears to be highly toxic.