I went through a pretty classic HubSpot SWE flow that started with an online assessment. For me, it was a CodeSignal-style test, and I also saw that there was an option to skip an OA if there was a recent prior score from another company—either way, the early technical gate was clearly the first filter. After that, I had a short recruiter chat and then a longer technical sequence.
My technical portion ended up being split into coding and systems design: one hour in a LeetCode-ish style format and one hour on systems design. In my process, once I passed the initial recruiter stage, there was also a later technical deep dive that leaned on a project I’d worked on in the prior couple of years, which helped it feel less generic. After the deep dive, I had a final behavioral round.
11 months ago
Average Neutral Cambridge, MA
After applying, I went through an online assessment (CodeSignal). A recruiter call followed, and then I had two back-to-back virtual interviews. One was an HTTP-oriented technical discussion (I was told it could be HTTP or a LeetCode-style problem), and the other was system design.
The system design round stood out because they didn’t really “probe” what I wanted to build. They pasted the requirements up front and expected me to jump straight into designing from there. It felt like they were aiming for a very polished, almost perfect structure and flow. The overall difficulty was more average than brutal, but the system design bar felt strict.
Reported
I went through a virtual onsite that felt tightly packed: two system design rounds and one coding round. Before that, I’d completed the OA as part of …
Unlock every Backend Engineer interview experience
