Gogo Senior Software Engineer interview questions

I was referred by another employee. I had a phone interview with the recruiter the next day. A day later I had a phone interview with a manager. A couple of days later I had an in-person interview with a panel. I met the manager, his colleagues, and the SVP. A day later they made an offer.

Received a message from a Gogo recruiter on LinkedIn. I had a short phone screen with the recruiter that took about 30 minutes or so. Most of the questions asked were gauged around my current employment situation, compensation, and to get a feel for me as a person. I was asked to do a phone screen with the hiring manager a short time later. This phone screen lasted about 1 hour and the hiring manager dug a little deeper into my professional and personal background. We proceeded with an on-site interview where I met with 4 other individuals. The hiring manager, one of their peers, the hiring manager's boss and an individual in-charge of software acceptance testing. The interview did not have any technical questions. The questions asked were focused on my thought process for software design and architecture and how I go about solving problems. I was asked to talk about a few of my prior professional tasks that applied but was not asked any technical software questions (i.e. how to sort a deck of cards, etc.). It was obvious to me through the interview process that based on my 10-years of experience in the industry Gogo trusted I had the technical skills to do the job and the interview was mostly based around figuring out if I would be a good fit for the team. After my half-day on-site interview the recruiter reached out to me a few days later to offer me the position. I asked to have a follow-up meeting with another software engineer at Gogo (that was unable to meet me the day I came in for the interview). I met with that individual and the hiring manager over lunch one-day and was able to talk about "a day in the life of a software engineer at Gogo." It was very informative and what eventually lead me to accepting the job offer. I found out over the course of my follow-up conversations with the recruiter and hiring manager that they were building out the software engineering team and that explains why there was a lack of technical questions posed by other software engineers. Overall, Gogo is looking for technically sound "chameleon" software engineers that have an understanding of good software architecture. Looking for individuals that are problem solvers and capable of diving into a large multi-tier software system and understand the different software pieces that makes it all work (or not!).