Real, anonymous reports from people who interviewed for Software Engineer at MongoDB, newest first and distilled into what to expect across the loop.
After a recruiter call, I ended up going through a pretty grindy sequence that stretched across multiple stages. The recruiter touched base first, and then I had a technical screen through Karat where I was asked a couple of LeetCode-style questions—one round leaning into DSA and CS fundamentals.
My experience centered on live coding, and that was honestly the main reason I felt the process differed from what I usually like. I went into a live coding session and found the interviewer handled it in a way that made it easier to follow along—I felt like the person explained things as I progressed instead of just watching.
The interview process typically begins with a recruiter call, followed by a series of technical interviews that can include coding, system design, and behavioral assessments. Candidates noted that the structure felt organized but could also be demanding, with multiple rounds leading to a high-pressure environment.
Candidates faced various coding challenges, often in a live coding format, that emphasized data structures, algorithms, and problem-solving skills. The expectation for correctness and clarity during coding was high, with some rounds focusing on specific topics like multithreading or system design.
Behavioral interviews were common, focusing on past experiences and alignment with company values. Candidates reported that these rounds were often straightforward but could also shift unexpectedly into technical discussions, which some found challenging.
Communication throughout the process varied, with some candidates experiencing clear timelines and supportive recruiters, while others faced ghosting or lack of feedback after interviews. This inconsistency affected candidates' perceptions of the process.
The overall difficulty of the interviews was noted to be high, especially in technical rounds, which could lead to a feeling of being constantly evaluated under pressure. Candidates often felt that the intensity of the process was demanding and left little room for error.
Specific technical topics frequently emerged in interviews, including multithreading, system design, and performance issues related to MongoDB. Candidates noted that a mismatch between expected and actual topics could lead to confusion and frustration.
