Management position. Interview 1: Phone Screen Recruiter asked basic questions about experience and salary requirements plus a few that were more specific such as "what is your leadership style?" Interview 2: Future Boss Next interview was in person with my would-be boss. Mostly management/process questions. Very general and open ended. If I mentioned one area of experience, for example user experience testing, a common follow up would be to ask "what would you have to change in your approach to get better at..." followed by a related subject, for example back end coding. An engineering lead was brought in briefly to ask one technical question: Given a number >= 10,000, write function in any language to find the greatest sum of five consecutive digits. I got about half way through before they stopped me, saying I did very well and they didn't need to see any more. When it was my turn for questions, the answers were very thorough. Interview 3: Technical / Situational The next interview was with two of the engineering leads that would be reporting to me, plus the boss. I was told up-front by the recruiter that it would be mostly technical but a large portion of it ended up being situational. My answer to the "warm up" technical question was something they hadn't seen before. The boss tried to stop me, but the engineering leads asked me to continue so I did. We ended up spending the entire technical portion of the interview on it. The question was to write a function to find "happy numbers". One of the engineers disagreed on whether my solution would work, so I ended up posting the solution to GitHub the next day to prove it. The situational questions sounded like real situations they were actively dealing with or had recently dealt with... if we were about to miss a deadline and could lose a sale as a result, how do you handle that? If a business owner tries to dictate technical details of a solution and the engineers disagree, how would you come to a resolution? Interview 4: VP #1 The next interview was with a VP over the phone (it was supposed to be in person, but scheduling was difficult). Despite being on the phone, it was very detailed. He was VERY familiar with my resume, and had obviously gone beyond that and Googled me (he noted details from my personal website, LinkedIn, and what must have been notes from the previous 3 interviews). Virtually all questions were open ended yet very specific to my background. For example, "I see you mention SOA on your LinkedIn, tell me about that." He would keep probing until I was giving very detailed answers. I don't remember what the original question was, but at one point I found myself describing the role of dependency inversion in unit testing when I realized I was talking to a VP, not an engineer, so I stopped and said "I don't meet many VPs that can understand what I'm saying" and he said "it's fine, keep going" which I thought was cool. Interview 5: VP #2 + Team Lunch The final interview was with another VP. He started by asking me what I wanted to know about CareerBuilder. I had plenty of questions, so that part went well and took up most of the interview. I think he was glad to see I had dome my homework. At one point he asked what I thought the key to developing new leaders was, I answered "luck," and we had a good laugh before getting into a more nuanced response. Following that, I had lunch with the team I'd be leading. Everyone was in high spirits and there was plenty of good nerd-humor to go around. I got a few questions and asked a few questions, but most of the conversation was social. Offer Got an offer over the phone the next day.