My first step was an OA based on implementing a file system in JavaScript with four progressive levels. As it got deeper, the work increased in complexity, and the structure of the problem made it clear they were testing whether I could keep my approach clean while requirements became more demanding.
After that, I had a 30-minute recruiter behavioral round that asked questions like why HubSpot and also pushed for specific examples—especially times I’d had to give feedback and times I’d worked with someone from a different cultural or technical background. I tried to keep my stories organized and concrete.
> 1 year
Average Neutral Boston, MA
I went through a more intense path than the typical short screening flow. First there was a phone screen, then a technical phone screen, and then a lengthy take-home assessment. The on-site itself was about three hours long and involved problem solving with multiple employees, with additional technical questions layered into the time.
Even though the stages were clearly laid out, I ended up getting rejected after the initial technical screen—so the take-home and on-site didn’t translate into an eventual offer for me. I remember feeling like the process was heavier than it needed to be given that it ended earlier.
Reported
Average Negative
I had a recruiter call first, then an interview sequence that ended pretty abruptly. The first technical round was a JavaScript deep dive with an inte…
Unlock every Frontend Engineer interview experience
