I was approached by a recruiter via email about the position and began the interview experience from there. The process included a phone screen, followed by a Skype call, and then an on-site interview.
Most of the questions were high-level, focusing on topics such as leading a team, designing a product, and problems encountered, triaged, and solved. All interviewers were pleasant and knowledgeable. I even received constructive feedback on areas for improvement when I was informed I would not receive an offer, which was valuable in itself.
My biggest issue arose during one of the on-site interview sections. My interviewers appeared unprepared for our discussion. They started by posing a hypothetical scenario involving API connections. Although I attempted to engage by offering comments and answers, they soon admitted they were improvising. Consequently, the conversation became strained and resulted in an incredibly vague and poorly described situation.
When I was told that the company would not proceed with an offer, it was explained that this particular section of the interview was the primary reason for their decision. This explanation was particularly frustrating.
You have two systems that you need to connect. How do you do it?
The following metrics were computed from 1 interview experience for the HubSpot Senior Systems/Tools Engineer role in United States.
HubSpot's interview process for their Senior Systems/Tools Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for HubSpot's Senior Systems/Tools Engineer interview process in United States.