MongoDB Interview Experiences

8 results

• 

  Failed the First-Round UnionIterator QuestionMongoDB · Software Engineer · Technical Screen · Sep 2026

  Rejected

  First round phone screen. I got asked an Iterator question, and I failed because I didn't practice enough. I'm sharing the question for everyone. Overall I thought the interview experience was pretty good. The interviewer was really nice and gave me hints, and I feel like their company culture is good too, and the work-life balance is good as well. Implement a UnionIterator class that takes two s…

• 

  Positive Crawler Feedback, Then Rejection the Next DayMongoDB · Software Engineer · Technical Screen · Aug 2026

  Rejected

  I have no idea why I failed this interview. I finished both the original question and the follow-up, and the interviewer said both my approach and code looked good. Then I was told the next day that I'd been rejected. Question: Implement: Single-threaded first → Follow-up = find the bottleneck + speed it up with concurrency (= LC 1242 Web Crawler Multithreaded) The interviewer explicitly said the…

• 

  MongoDB Account Executive Interview Experience: clear recruiter expectationsMongoDB · Account Executive · HR Screen · Jul 2026

  The recruiter call set clear expectations about the timing and what came next. The interviewers were nice and direct, and I felt they were helping me understand the process rather than simply describing the job. The conversations fit what I expected for the market and role, and the compensation discussion was consistent with other companies I had considered. I was pleasantly surprised by how atta…

• 

  MongoDB Software Engineer Interview Experience: live coding, database troubleshooting, and LinuxMongoDB · Software Engineer · HR Screen · Jul 2026

  After a recruiter conversation about my background and skills, I had a technical round with live coding and deeper questions about problem solving and ambiguity. The process later switched modes with a team-lead-style discussion about troubleshooting scenarios, including how I would diagnose a slow database. There were several in-depth technical interviews on databases, Linux, and other areas lis…

• 

  MongoDB Software Engineer interview: Karat screen and inconsistent next stepsMongoDB · Software Engineer · Technical Screen · Jul 2026

  Rejected

  I began with a recruiter conversation and then went straight to a Karat technical interview. The Karat portion had only a small number of questions, but it was clearly a serious gate. Mine focused on LeetCode-style problems, and I did not pass that stage. What disappointed me was that the process did not end immediately after Karat. Another technical round was still scheduled, which made the flow…

• 

  Phone Screen, Then a Five-Round Onsite With Code ReviewMongoDB · Software Engineer · Senior+ · Onsite · Jul 2026

  Offer

  I've just come out the other end of the MongoDB interview process, and I wanted to share how I got ready, since other people's write-ups helped me so much. I'm a backend engineer by trade, with time at a large tech company and at a startup. Over the course of this job hunt I had a handful of interviews in flight simultaneously, yet MongoDB topped my wish list, and that's where I landed an offer.…

• 

  Six Rounds Including a Code Review, Director Wanted More SeniorityMongoDB · Software Engineer · Senior+ · Onsite · Jul 2026

  In progress

  For DSA I just did LeetCode, steadily, over the past few months. For system design (both low-level and high-level) I went with an online design course without thinking twice, and I also watched a couple of YouTube channels on the topic. Here is how the loop went: Technical Screening: I had to build a rate limiter that lets through n requests within the last k seconds. We talked through the API an…

• 

  MongoDB Customer Success Engineer interview: customer-meeting presentationMongoDB · Customer Success Engineer · HR Screen · Jun 2026

  My process took a couple of months. It began with an HR screen, followed by a hiring-manager interview on the role and typical customer-success questions, then a peer interview covering databases and cloud-native infrastructure. The last stage was a presentation challenge framed as a customer meeting. I had a prep call before presenting to a fictitious customer panel, with interviewers playing di…