MongoDB Curriculum Engineer interview questions

I did an introductory call and then an in-person visit that involved several interviews. It was mostly the usual stuff, although I have to say this was the longest in-person interview session I've ever done - it dragged on all day. They bought me lunch from a local deli, which was nice, but it was still a long day.

Spoke with the first interviewer for 30 minutes over the phone. The conversation was friendly, but a bit one-sided, as I only was able to ask him about one minute of questions during the entire phone call. He then asked me to email him questions I had about the job, and I did, but he took 9 days to respond to them. What is even more concerning is that one of the questions I asked via email was "What is the most important thing you feel is necessary to be a good manager" and he replied "responsiveness". After reading that answer, I unfortunately had to take everything else he said with a grain of salt. The following week, I did a one-hour technical interview with a second interviewer where I typed code into a text editor while the interviewer watched and asked me questions. The technical interview seemed more like a Software Engineering interview, as I was required to build fairly complex programs from scratch in front of the interviewer, which seemed a bit inappropriate for a Curriculum Developer interview and seemed a bit too academic as well. The company should probably modify the interview process where code samples with typos/errors could be presented to the job candidate and then the candidate could try to find the typos/errors. Or, the candidate could tell the interviewer what the output of a certain algorithm would be. Those interested in the job should also keep the following in mind: 1. The company is going to promote a new manager by September 2016, so the current manager will most likely "not" be your boss for long. 2. The department is dominated by former college professors and researchers, so you will need to be comfortable working inside a very "academic" culture. 3. According to the interviewer, you are expected to work 50-60 hours per week in this role.