HubSpot Software Engineer interview questions

They give you a brief tour of the office. The buildings are great, awesome perks. After that I had three, 45 minute interviews. There is more talking than actual coding if you carry the conversation. The first two interviews, you interviewed with one person, last one was with two people. Everyone was really nice but the guy in my second interview didn't seem like he wanted to be at work that day, kinda grumpy and over critical I thought. After the three interviews you meet with your recruiter quickly and you're done. They said they make a decision in a day but it took several for them to get back to me. Same thing happened to a friend of mine, waited for a while too.

A recruiter reached out to me and immediately setup a phone interview with a VP of Engineering. He mostly asked questions about my experience and things I've worked on. He dove into some technical details of past projects. The interview went well so I was told on the phone that I could skip the online quiz part of the process and come right in for an on-site interview. Being a full-stack engineer, I was also told that the on-site would consist of either backend or frontend questions and I had to choose one. I was also asked if there was any part of the stack that I didn't know as well, which for me was relational databases. This was really important because they ended up taking it easy on me when it came to any database questions on the interview. I would highly recommend being open and honest about your strengths and weaknesses. The on-site interview consisted of a quick chat and tour of the offices with the recruiter, followed by 3, one hour long technical interviews, each with 2 members of the engineering team, followed by an hour long interview with the VP, and finally, a brief wrap up with the recruiter. The technical interviews started with about 15 minutes of chatting about past projects, and then went into scripted technical questions that involved whiteboarding. The technical questions were somewhat challenging, but extremely practical. There were none of those, "I'll never have to do this in real life," questions. There was also some time left on the end of the interviews to ask questions. The interview with the VP was unscripted, but fairly technical as well. We talked in detail about past systems that I've implemented and he would propose scenarios, e.g. "Suppose the API you were using was rate limited..." and ask how I would handle them. After the interview, the recruiter kept up frequent communication and was very responsive to any questions I had. I received an offer exactly one week later and accepted!