Moz interview questions

Overall the interview process was good. I liked that they spent a lot of time and effort which shows they care about making a good hiring decision. They allowed for more than enough time for them and me to get a good feel about it. It may have been a bit excessive though. The entire process was 5 weeks from initial contact. I went through 2 phone screens and 2 in-person interviews. The first phone screen was with the recruiter and was pretty typical. The second phone screen was with a developer who gave me a coding problem which we did over collabedit.com. The first in-person interview was pretty much all day at their office, from 9am to 3pm. It was 6 1-hour sessions with different interviewers. Three of these were technical interviews and they were all pretty much the same. We could have saved a lot of time if instead they brought in all the developers they wanted me to interview with at the same time or something. Maybe the goal was to make it feel less intimidating by just having one or two developers at a time. But it seemed pretty redundant, especially when you're explaining your past work history over and over (every interviewer didn't ask, but over the whole process I probably went over it 4-5 times). At lunch time, a couple people took me out, which was nice. It's still an interview, but it felt like I could relax a little more. The second in-person interview was from 11am - 2pm and I interviewed with 3 people that day. The first one I went into a conference room and talked with a developer over Google video chat. It felt pretty awkward, I'm not sure if it was because of the video chat or because we just didn't connect well. Afterwards, I went out with the hiring manager for lunch and we talked about the position and my past experience. The last part was another technical interview with the director (or something, there seemed to be a lot of confusion about what peoples roles were). He asked me similar technical questions to the ones I'd been asked before. Pros: - Spent a lot of time getting to know me and letting me get to know the company. - They do a lot to try to make you feel comfortable in the interview process. They started off with a tour of the place, and lighter conversation. The lunches help make things feel a bit more casual even though it's still an interview. Also, if I had accepted every time someone asked if I wanted something to drink, I would have drowned :) - Treat you like a person and peer rather than an "are you worthy" type attitude I've seen occasionally at other places. - Always gave me time to ask questions and some interviewers made a point that they wanted to make sure I felt it was a good fit as well. Cons: - The job description in the ad did not match the role. I didn't really find out until I kept prying to understand the role better. Several people seemed to have different understandings of what the position was supposed to be. - Redundant technical interviews with questions that are irrelevant to the role. (I wrote more recursive functions in these interviews than I have in the past 3 years). I was asked a couple basic SQL questions, but for this specific role, I would highly recommend they dig deeper next time. - I got a strong impression they didn't really know what they wanted or needed. Having worked directly in the area that they're wanting to build, I don't think they really know what they're doing. And unfortunately, I don't think I sold myself well enough on how I can help them accomplish their goals. - Not really related to the interview, but it sounded like different teams blame each other a lot for problems, which is unfortunate.