There's never a dull moment at work; there's always something new cooking around the corner, and we move quite fast. I love all the autonomy and support I get to try new things and take on large, vague projects. I'm constantly learning, and if something isn't working out or I've stopped learning, switching teams is easy and even encouraged. I've been on 5 teams and have tried out tech leadership as well as individual contributor roles. My peers support me, and I feel like they also care a lot about the team and our success. There's psychological safety to voice your opinions and try out new things, even if you're wrong and you fail. There are a few teams where this is not true, but you can easily move off or avoid them altogether by asking around.
There is a lot of emphasis placed on mental health and taking the time you need to live your life as well as work, which is wonderful. Primary and secondary parental leave are both now 4 months, which is incredible!
There exist teams where there isn't physiological safety, and they seem to operate contradictory to the HubSpot way. While they are far and few, I imagine if you're placed here as a new hire, you would have a very different experience at HubSpot, which is saddening.
Hire more female engineers! It's bizarre when I go months without interacting with a woman professionally.
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
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