I've been through a lot of recruiter screens this cycle and the MongoDB one stood out as more substantive than average. Sharing my notes in case it helps anyone prepping.
First: it's not a vibe check. The MongoDB recruiter came in with a clear agenda. It was about 35-40 minutes and covered real ground.
Here's roughly what they covered:
Why MongoDB. Not a throwaway question. They want a real answer. I said something about the pivot toward Atlas as a cloud-native product and how the document model is having a moment with unstructured data use cases in AI/LLM pipelines. They engaged with that. Generic "I love databases" will not impress.
Role-specific background check. For a senior SWE role they asked about my largest-scale distributed system experience, what my role was specifically, and what broke. They want to know you've actually operated things at scale, not just coded them.
Level calibration. They asked directly: "Where do you see yourself leveling in at MongoDB?" They use an internal framework (not L5/L6, they use something closer to SWE, Senior SWE, Staff SWE). Be honest about your current level and don't oversell. They said calibration happens throughout the loop but they want to start aligned.
Timeline and process walkthrough. They explained the loop: OA, hiring manager screen (sometimes), system design, coding, two behavioral rounds. Ask questions here. I asked about the team structure and which Atlas sub-team the role was on, and got good detail.
Salary expectations. They asked. I said "I'm open and more interested in fit, but if it helps, my current total comp is X." They noted it and moved on. Don't lowball yourself here.
Overall: treat this as round 1 of the eval, not a scheduling call. Come in with a clear MongoDB answer and a concrete story about your most complex technical work.