TubeMogul Interview Questions
& Process

I had a really good experience interviewing with professional people. The whole thing took about two weeks from when the recruiter first reached out to the onsite. The first technical interview was on a computer where I had to code and design a solution on their test servers. The interviewer was really chill and patient. After that, I was invited for an onsite. I had a bit of trouble finding parking and the entrance, but someone in a BMW offered to help and walked me in, turns out he was the CEO! Once inside, they offered drinks and snacks before I met with a few people for 1-1 interviews. There were three rounds, and the questions were relevant and tough, including tricky scenarios and how to solve them. Everyone was professional and friendly, making the three-hour process comfortable. Overall, a very positive experience.

I got referred by someone who works here. The recruiter reached out and set up a screening interview. After that, I had a technical phone interview with the Director of Engineering. It was a 30-minute interview where I was asked about Java, Spring, and my past projects. I answered everything, and he told me about his team. I didn't hear back for a week, so I emailed the recruiter. He said the position was filled, but the interviewer gave good feedback. So, the recruiter offered me a job on a different team and asked me to come in for 4 technical interviews at their office. At the onsite, four engineers from an engineering team interviewed me. The first round was with a software engineer and one of his colleagues, which was unexpected. He asked about a project on my resume, then asked me to reverse a singly linked list and write an SQL query. I used a different approach for the query that he didn't expect, and we debated it a bit before I convinced him. He then asked how I'd write the tables for the query in Java, with follow-up questions. This interview went over by 15 minutes. The second interview started late because the first one ran long. The interviewer immediately went to the whiteboard with a vague problem: sort a lot of unsorted messages. I made an assumption to start, which he agreed with, but then he just kept confusing me with a lot of discussion. Right after that, the third interviewer came and asked if I had any questions, otherwise, we'd solve a problem. No break given. He asked me to design an elevator system. The last round was with the director, who asked system design questions. He had me draw the architecture of a project from my resume and then asked me to scale it, covering topics like load balancers, sharding, caching, NoSQL vs SQL, and replication. I think I did well. He finished by asking 4-5 behavioral questions, and he was friendly.

First, there was a 20 minute call with the recruiter to go over my sales background and overall experience. After that, I had a 2 hour onsite interview with an Account Executive, the Director of Sales, and a Sales Manager. If that went well, I was given a take home assignment. This involved finding a prospect, writing an email to them, and creating a 3-4 slide powerpoint presentation to pitch TubeMogul. The presentation was a mock call/webinar with the Director of Sales and Sales Manager, lasting about 20 minutes, and they asked questions like a real prospect would.

First, a Technical Recruiter called me for about 30 minutes to screen me. They asked general questions about my background and if I would fit into the company culture. The next day, the Director called me for about 40 minutes and asked technical questions to see how much I knew. Then, I went to their office for a 3-hour interview. The Project Manager, two Developers, and the Director interviewed me one by one. I even got to meet the President, which was a surprise and an honor, and they asked me a couple of questions too. The developers tested my web development skills with questions about PHP, CSS, and Javascript. Everyone was really nice, polite, and welcoming. It's a growing start-up, so don't expect formal wear like suits and ties. The dress code is somewhere between casual and business-casual, but people are still expected to act professionally. Overall, I had a really good experience with the whole process.