Noticeable technical debt (at least on the front-end side), not catching up with recent practices from the last 3-4 years.
Code quality is bothering at times, with lots of over-complicated stuff.
The "Senior I" role feels like a regular dev.
I'd push for more innovation in the front-end area before Hubspot gets siloed in its own ecosystem.
My interview process was much like the others described here. It started with a recruiter phone screener. In the call, the recruiter described the role, the tech stack, salary range, and benefits. The next stage was a coding exercise. You receive a
A very engaging and interactive interview, with lots of help and guidance along the way. This style brought out more in me as a candidate. The interviewers were very friendly and answered any questions I had. There was a lot of use of the whiteboard.
The typical interview process, with a positive twist. There was: * A recruiter interview * A "homework" assignment * A technical interview * Their version of "the loop" Overall, they tried to make the process (especially the technical inte
My interview process was much like the others described here. It started with a recruiter phone screener. In the call, the recruiter described the role, the tech stack, salary range, and benefits. The next stage was a coding exercise. You receive a
A very engaging and interactive interview, with lots of help and guidance along the way. This style brought out more in me as a candidate. The interviewers were very friendly and answered any questions I had. There was a lot of use of the whiteboard.
The typical interview process, with a positive twist. There was: * A recruiter interview * A "homework" assignment * A technical interview * Their version of "the loop" Overall, they tried to make the process (especially the technical inte