J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez MongoDB (Palo Alto, CA) en mars 2016
Entretien
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.
Questions d'entretien [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.
Questions d'entretien [1]
Question 1
API design question with some standard library usage required.
J'ai postulé via un recruteur. J'ai passé un entretien chez MongoDB
Entretien
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.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez MongoDB en oct. 2025
Entretien
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.
Questions d'entretien [2]
Question 1
Concurrent interview: design a concurrent expriring queue