I applied through college or university and the process took 3 weeks - interviewed at MongoDB.
Interview Details –
Had an HR Interview where I discussed why I wanted to work with the company, which lasted around 45 minutes.
Then I had a Skype interview with an employee that worked remotely; it was really great talking to him. He was very nice, and I learned a lot from him, though he wasn't able to tell me a lot about the culture at the office since he visited less frequently.
The last part of the process was a phone interview. The person I talked to was a little awkward, but she was very nice and I enjoyed the conversation.
Interview Question –
I had a rather lengthy discussion during the Skype interview about how garbage collectors were implemented in various languages. I don't know if I would say it was a question perse, but it was difficult giving adequate explanations of each, discussing not only the implementation but also the pros and cons.
I also had a question about finding the largest prime divisor of a number, which I thought was difficult because the question itself was so easy, so it was kinda difficult to find good ways to optimize. Answer Question
Interviewed at MongoDB
Interview Details – Several phone interviews, was invited in and met 6 different people, all went very well. Last interview was with VP. Never heard from them again.
Interview Question – How many gas stations in the United States? Answer Question
I applied online and interviewed at MongoDB.
Interview Details – Applied online and got a call from the recruiter. Had an initial phone screen. I answered all the questions except the C++ ones. I didn't know they were big on C++ knowledge.
Interview Question – The questions on C++ were the unexpected ones. Interviewer asked me to write a very simple coding questions, but asked me to use vectors from the C++ standard library and use iterators for iterating through those elements. I couldn't answer as C++ isn't on my resume. Answer Question
I applied online and the process took 2 weeks - interviewed at MongoDB in July 2013.
Interview Details – recruiter call, technical interview with hiring manager, technical team group interview onsite, interview interview with VP. Reference check. Offer made
Interview Question – how various search algorithm O time change if it is done in parallel on multi cpu machine View Answer
Reason for Declining – better option available
I applied online and the process took 2 weeks - interviewed at MongoDB in April 2013.
Interview Details – One phone screen. One technical phone interview coding on google docs. How would you write DB write / access functions to make sure data is not modified by threads. Parse mathematical expression given as chars in array ['1', '+', '2,' '/', '4']. Four onsite interviews over the course of 4 hours asking a variety of questions. Write algorithm to find loop in graph, write C code to convert integer to string.
Interview Question – Write an algorithm to find a loop in a graph. The graph is unidirectional with any number of connections. The graph is not necessarily connected View Answers (2)
I applied online - interviewed at MongoDB in March 2013.
Interview Details –
The single biggest pain point was how long this took. And, every time I got a call from HR, it was to tell me that another call with someone else had been scheduled.
In total I fielded over 12 different onsite and offsite meetings over 3 months. There were several times when I was convinced that this is a serious waste of time.
After the technical phone screen, I went in for an in-person invterview that lasted 4 hours and there I met 4 people. That same day I received a call from one more person.
It took 3 months to receive an offer.
Interview Question –
We have a person who logs into a website using their Facebook credentials. Anything they post to that website can be seen by their friends and those friends' friends only.
How would you optimize the collection of this data? Answer Question
Negotiation Details – I didn't negotiate. I took the base salary, stock options and bonus structure as is. I thought it was pretty fair.
I applied through other source - interviewed at MongoDB in February 2013.
Interview Details – 3 challenges. Fizzbuzz. Find the height of a binary tree. Parsing parenthesis.
Interview Question – Given a set of open and close parenthesis, make sure the string is valid, such that each open parenthesis has a matching close parenthesis in the correct place. View Answer
I applied in-person and the process took 1 week - interviewed at MongoDB in September 2012.
Interview Details – Interviews were scheduled over one day. Process was really enjoyable. I was asked a couple of interesting coding questions to see how I think but the majority of the interview time focused on my experiences as CTO, why I was interested in working at 10gen, and what I wanted to do at the company.
Interview Question – When an interviewer disagreed about a technical choice that I had made for a website I was asked to defend my opinion and argue my point of view. View Answer
I applied through a recruiter and the process took 4+ weeks - interviewed at MongoDB in August 2012.
Interview Details –
TLDR: product & company seem like a classic example of a solution in search of a problem. Probably an OK place to be a pure developer, but not a good place for customer-facing roles. Interviewers didn't seem to understand the difference between a software engineer and a solution architect.
Details: I hadn't really been looking around, but one of their in-house recruiters reached out to me initially, and after checking around a bit I connected with him and we had an email/phone discussion. At that stage it sounded interesting enough that I subsequently invested an afternoon in meeting some of them in-person. It turned out to be a rather complete non-match from both our perspectives; I was not interested in receiving an offer and they were not interested in extending one.
The recruiter and the HR executive I met were both pleasant and personable--people I'd hire for my own company, in both cases--but the rest of the staff I spoke to seemed rather arrogant and insecure. Mean-spirited, as an earlier reviewer commented here. I had to bite my tongue when one manager said they were staffing up on customer-facing folks because they were "ready to take on Oracle." Most of their interview questions were more appropriate for core developers than solution architects: all about algorithms, nothing about scaling, implementation, or other real-world issues. Nor did anyone seem to care about actual customer-interaction skills.
To the recruiter's credit, he reconnected with me less than 48 hours later, and we agreed that it wasn't a match.
Interview Question – Not difficult, per se, but unexpected: one interviewer asked me to name several different sorting algorithms and rank them by their computational complexity. Unexpected because I've never had such a discussion with a customer, no matter how technical; the question would have been more appropriate for an engineer being hired into their kernel group but the interviewers didn't seem to know the difference. View Answer
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –