Pros: - Remote-first, which is exactly what I wanted. - I use and love the product, and the fact that we get an enterprise-level account for personal use is fantastic. I feel very invested in making a good product as a customer. - WLB is fantastic. I am encouraged to take time off, and I don't feel bad about doing it. A four-week sabbatical every five years is huge. The product team also gets two weeks of rest a year, one week during the first week of July and one week during the last week of December. - A lot of growth opportunities. Teams are kept small (5-6 max) so that there are many chances to grow in skills and lead to help grow your career. If you're looking to advance, this is the place for you. - The company actually tries to embody its values. For example, upper management was transparent about ways they fell short in particular areas and are taking employee feedback seriously to make a change. - Pay is good for the company size and market (at least in Product Eng). - Internal tooling is great. They built their own CI/CD so that devs can focus on writing code rather than fixing a DevOps system. And they have great UIs.

Cons: Work is challenging and can feel like a treadmill increasing in speed. If you're not ready for it, it can be tough. But there are a lot of things that are changing to help that, like the weeks of rest, unlimited PTO, and more. Homogeneous tech stack (can be both a pro and a con). All backend runs on Java 8/11, Dropwizard framework, and the same CI/CD. This is great if you want to move teams, but it's hard to pioneer new technology. No cost of living raises or annual bonuses. You can get stock refreshers if you perform well, but I personally would prefer an annual bonus determined by company and individual goals.

Pros: Great engineering ecosystem. Very easy to get code into production. Very good standard of engineers (I think below par engineers that got through the interview process simply would not handle the work and would leave). Self-organized teams (although this is both an asset and a liability at HubSpot).

Cons: Compensation was so-so. Self-organized teams have meant some teams set a higher bar for their service quality. So you could be getting paged very often on a strict team and not at all on a lenient team. Eng Management was hands-off, which was good, but they weren't policing the fact that the team was missing input from Product. Engineers were, in effect, the product owner/manager. On-call is completely unacceptable, especially as remuneration is considered part of your base compensation. You're on-call 1 in 3-5 weeks (in some cases, even every 2). And if your team has strict monitoring, expect to be getting calls. So at one end, you've engineers on-call 1 in 5 weeks who might never get called, and at the other end, engineers on-call 1 in 3 weeks getting called round the clock. And both are compensated the same. The "culture," although having nice parts, is force-fed at such a rate that you eventually vomit and reject it. (We don't all live/work in the US, so pushing agendas that are US-born in Ireland is very wrong). Young engineers with little experience in other companies. This has led to a lot of belief that the way HubSpot does things is the way the world works. This should not be the case.

Pros: A place that cares about its employees.

Cons: The compensation is not that competitive in the market.