By almost any measure, HubSpot is an excellent place to work.
This is all front-end specific since that's where I work.
HubSpot made some questionable decisions on how their JavaScript dependencies are bundled/published internally. This means normal JS tooling does not work.
If you develop for the front-end, you are forced to use VSCode and a HubSpot-specific plugin to get autocompletion, intellisense, debugging, etc.
thing?.nested?.someKey)I know I was harsh in the cons, but I really do think this is an amazing place to work. If I had to pick one thing to ask management for, it would be to provide remote teams with some more structure/guidance on how to better 'gel'. Newer teams especially suffer from feeling a little siloed and lonely.
I would never interview for this company again. Initially, I was disappointed when I received the rejection email. However, after going over the feedback, I was happy I didn't get through. It's a pure waste of time. All the questions you can find o
The interview was easy, and the interviewers were very friendly. It consisted of: * 1 coding interview * 2 system design interviews * 1 behavioral interview Most of these interviews just required discussions and asking questions; they were no
It started with the 3-hour take-home. This was actually pretty difficult and was a LeetCode question in disguise as a JSON manipulation problem, despite them saying they don't like LeetCode problems. I'd say it was equivalent to a LeetCode hard in te
I would never interview for this company again. Initially, I was disappointed when I received the rejection email. However, after going over the feedback, I was happy I didn't get through. It's a pure waste of time. All the questions you can find o
The interview was easy, and the interviewers were very friendly. It consisted of: * 1 coding interview * 2 system design interviews * 1 behavioral interview Most of these interviews just required discussions and asking questions; they were no
It started with the 3-hour take-home. This was actually pretty difficult and was a LeetCode question in disguise as a JSON manipulation problem, despite them saying they don't like LeetCode problems. I'd say it was equivalent to a LeetCode hard in te