Getting an Interview
Getting an Interview
Interviews for Top Jobs at MongoDB
- Software Engineer (10)
- Intern (8)
- Software Engineering (7)
- Consulting Engineer (2)
- Software Engineering Intern (2)
- Engineer (1)
- Event Coordinator (1)
- Senior Marketing Manager (1)
- Development Intern (1)
- Technical Support Engineer (1)
- Software Engineering Internship (1)
- Intern Developer (1)
- Manager DevOps (1)
- Solutions Architect (Customer-facing) (1)
- New/Recent Grad - Software Engineering (1)
- Database Kernel Engineer (1)
- Junior Software Engineer (1)
- Software Engineer Intern (1)
- Managing Editor (1)
- Technical Architect (1)
- Technical Services Engineer (1)
- Senior Engineer (1)
- Systems Engineer (1)
5 people found this helpful
Solutions Architect (Customer-facing) Interview
I applied through a recruiter. The process took 4+ weeks – interviewed at MongoDB in April 2012.
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.
- 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