MongoDB logo

MongoDB Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 1,462 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
64.5% Positive experience

Which role are you interviewing for?

30 roles · 1,462 reports

Candidate interview experiences

First-hand accounts from people who interviewed at MongoDB.

Showing 4 of 1,462
MongoDB logo
MongoDB

Customer Success Manager

Sales · nearly a year ago

Mid Difficult Negative experience Decline offer 2 rounds
Interview process
Recruiter call Presentation
Interview formats
Presentation

Recruiter reached out back in October. It was a start/stop process with various interviews. The recruiter got fired and one of the interviewers left. No one explained why. Hiring freeze then no freeze. Red flags everywhere. The final round was a presentation, which is a lot of effort for an interview, expecting product knowledge only from an interview. Declined offer because the process is indicative of the company.

Confirmed questions1 question
  • What's your approach to dealing with a difficult customer?
MongoDB logo
MongoDB

Strategic Account Director

Sales · nearly a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Really bad experience. It felt like I dodged a bullet. The interviewer started by saying he was in gym clothes because he didn’t feel like changing after his workout. He then spent about 15 minutes talking about himself without much connection to MongoDB or the job, and he came off as arrogant and unprofessional. When we finally talked about the role, it was clear my experience was a good match and I felt I answered the questions well. I'm also familiar with MongoDB’s products from past work. I was then told about the next steps and that I'd get materials to prep. After the call, I never heard back. I sent a follow-up email and LinkedIn message, but they were ignored. Recruiting is usually a candidate's first impression of a company’s culture, and this didn’t reflect well on MongoDB.

Confirmed questions1 question
  • What prompted your application for this role?
MongoDB logo
MongoDB

Product Designer

Design · nearly a year ago

Staff Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical

A recruiter reached out about a Staff Product Designer role focusing on Design Systems. I had a 20-minute initial phone call covering basic intro and role details, confirming the next step would be with the Hiring Manager. The whole process is managed through a portal with a clear workflow and some preparation resources. Unfortunately, after the recruiter call, I received no further communication regarding my status. I tried reaching out via the portal, but the recruiter ghosted me. I can still see in the portal that my stage is 'Hiring Manager Interview', which has already occurred, but there are no results yet.

Confirmed questions2 questions
  • Can you share an instance where you managed stakeholder conflict?
  • What has been your experience with design systems?
MongoDB logo
MongoDB

Software Engineer

Engineering · nearly a year ago

Senior Difficult Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Technical Coding System Design Technical

The process began with a recruiter phone interview, followed by a technical screen. Then there were several more technical rounds where I was asked about non-concurrent programming, concurrent programming, algorithms, and system design. I didn't get to the behavioral or final interviews, but the process was clearly explained, and I even received feedback afterwards.

Confirmed questions2 questions
  • Design an expiring queue that handles concurrency.
  • Given an array of numbers, a target sum, and K, find K elements in the array that add up to the target sum.

MongoDB Interview Questions

Quoted word for word from MongoDB interview reports.

Given an array of numbers, a target sum, and K, find K elements in the array that add up to the target sum.

Read reports

Implement Inverted search including functions to insert a document, search for a term, delete a document, and perform an AND search between two terms.

Read reports

What are the steps to set up a DNS server, and how would you diagnose a server that fails to start using systemctl?

Read reports

Could you explain the internal workings of the set method in a hashmap?

Read reports

Could you write a program that, starting from the number one, outputs 'fizz' if the number is divisible by three, and 'buzz' if it's divisible by five?

Read report

Can you solve a 2D dynamic programming problem, specifically finding the biggest square of equivalent strings in an array of strings?

Read report

What is the time and space complexity of the chosen data structure, and how could it be made more efficient?

Read report

What are the key metrics for measuring the success of an analyst relations program?

Read report

How would I investigate a database performance issue? Which steps would I follow and which tools would I use?

Read report

Formats, difficulty and experience

Across all 1,462 MongoDB interview reports.

Interview formats

Behavioral 38.5%
Technical 28.4%
Presentation 13.7%
Coding 8.5%
Case 4.3%

Interview difficulty

Easy 11.8%
Average 55.5%
Difficult 32.8%

Candidate experience

Positive 64.5%
Neutral 12.3%
Negative 23.2%

Reports by job function

Engineering 555
Sales 517
Operations 97
HR 71
Marketing 52
Analytics 38