I applied through a recruiter. The process took 1 week. I interviewed at MongoDB (Palo Alto, CA) in Mar 2016
Interview
I was referred in through a recruiter. The mDB recruiter replied within a day, and we did a 30 minute phone screen. The first phone screen was non-technical, mainly just asking about my past experiences, why I'm looking to move, what I'm strongest in, etc. This was followed up with a second phone interview with an engineering manager. This one was more technical, but overall still pretty straightforward. A coding challenge followed, and then I was brought in for the in-person, which was a group of interviewers all afternoon.
Overall, the interview experience was great. I wasn't a good fit for the role, so I didn't get an offer, but the team was very friendly and really smart.
Interview questions [1]
Question 1
Given two arrays, return a single array with the objects contained in both of the initial arrays.
Interviewer had a particular solution in mind that took a different approach from my own. My solution was algorithmically correct but not one that they were familiar with and preferred a non-closed form solution.
Interview questions [1]
Question 1
API design question with some standard library usage required.
I applied through a recruiter. I interviewed at MongoDB
Interview
Process was: Recruiter screening, Phone Screen, 5 Virtual Onsite. The whole process took a long time. I loved each interviewer, they were really friendly, nice and passionate with their work. The interview questions were unique and on the harder side but well organized.
I applied online. The process took 3 weeks. I interviewed at MongoDB in Oct 2025
Interview
Recruiter phone interview, a technical screen, then multiple technical interview rounds. I've gone through non-concurrent programming, concurrent programming, algorithms and the design one; didn't make it to the behaviorial and final interviews,
The process is well explained, and I have even got feedback afterwards.
Interview questions [2]
Question 1
Concurrent interview: design a concurrent expriring queue
