BookBub Software Engineer Interview Questions
& Process

The interview process started with an online coding challenge that took about an hour. After that, I had a second round where I met with two engineers to expand on the initial solution, which lasted about 2 to 2.5 hours. Then, I had a 30-minute meeting with HR, followed by a one-hour meeting with the hiring manager. I'm not sure why I was rejected after the final round, but it seems like a great company with great people, though there might not be much teamwork transparency.

BookBub reached out to me after a career fair. A recruiter contacted me the same day to set up a Google Hangouts interview with an engineer for the next week. During the interview, they asked about my resume and questions like 'what's the hardest bug you ever solved'. There were also one or two basic data structure questions. I didn't think the bug question went too well, but I guess it was okay because I got invited to the next round. The next stage was a coding challenge where I was given a task to complete in a few hours and email my code back. My code worked, but it was messy and inefficient, and they decided not to move forward with me after that. The entire process took about two weeks.

First, there was a take-home coding challenge that involved parsing JSON and CSV data. After that, I had a technical phone interview with two engineers. This interview was very practical, focusing on making modifications to the take-home challenge based on new requirements. It felt like a simplified task you might do during the internship, and using the internet for help was allowed. It concluded with some multi-threading questions. Then, I proceeded to the final round, which included two relaxed behavioral interviews (one with a recruiter, one with a senior engineer) and a technical interview. The technical part started with network questions and then moved to a design problem that was provided a couple of days in advance. Later that day, I was informed I did well and was asked for references. This process really seemed to assess how one would handle the daily tasks of the internship, as opposed to just theoretical data structure and algorithm questions. Plus, the team's passion for the company was evident.