Software Engineer applicants have rated the interview process at MongoDB with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 45% positive. To compare, the company-average is 67.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 60 user submitted interviews for this role. To compare, the hiring process at MongoDB overall takes an average of 33 days.
Common stages of the interview process at MongoDB as a Software Engineer according to 60 Glassdoor interviews include:
Phone interview: 49%
One on one interview: 18%
Skills test: 12%
Presentation: 7%
IQ intelligence test: 3%
Personality test: 3%
Background check: 2%
Group panel interview: 2%
Drug test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at MongoDB (New York, NY) in Mar 2021
Interview
Standard first round behavioral phone interview asking about past experiences and projects I worked on.
After about a week, was followed up by a second round 1 to 1 technical hosted by a software engineer from their team.
Interview questions [1]
Question 1
Implement a list class that keeps track of a max or min value and implement methods that would efficiently pop those values from the list when invoked.
I applied through a recruiter. I interviewed at MongoDB (Toronto, ON) in Apr 2026
Interview
I interviewed with a employee from New York and during my coding round, I gave brute force and also optimized solution, wrote the code within first 20-30 mins. I felt like it stopped being about evaluating my solution and turned into him continuously changing the problem. I'd answer one question, then he'd introduce a new assumption that wasn't part of the original design.for example, assuming a bounded executor queue with blocking submit(), even though my solution was based on Java's standard ExecutorService.
It felt like he kept modifying the underlying behavior just to see where the solution would break instead of discussing the design I had actually written. I don't mind deep follow-up questions at all, but it became hard to know what I was supposed to optimize for because the assumptions kept changing. Interviewer I got, He'll keep drilling into concurrency and may intentionally change the rules of the system. I felt like he wanted me to fail lol. Hopefully you get a different and fair interviewer.
Interview questions [1]
Question 1
How does ExecutorService limit concurrency? How would you make the visited set thread-safe?
I applied through a recruiter. I interviewed at MongoDB (Dublin, Dublin) in Mar 2026
Interview
Some behavioral questions and a rate limiter coding question with a staff engineer. They really wanted full proof code with no syntax errors and no interviewer guidance. Felt like the interviewer was not attentive.
Saw a fresh ad online, applied quickly and got a quick follow-up from recruiter. So far so good. Well, that's where it ends. After the recruiter call was scheduled, I got completely ghosted.