HubSpot is an incredible company, and I am still excited to come into work every day several years into my tenure. I think you'd be hard-pressed to find a better tech company in the area, especially as an engineer. Business-wise, stock and metrics continue to improve. Growth is difficult to sustain and not easy, but I'm bullish that we will continue to find ways. The company is not perfect, but the best thing about the culture is that it is willing to admit faults and improve where things are not great.
Naturally, as the company has grown, the only constant has been change, which is fine. But HubSpot, like most growing startups/scaleups, is not great at change management.
There is good transparency, but that does not necessarily equate to good communication.
There is thrash at times because the org structure does not support the goals that leadership sets for the company (which seem directionally correct, but execution is lacking).
The company is very young and lacks diversity in many areas (race, women in leadership, etc.), though there is a genuine effort to improve here.
Too much autonomy means silos, especially with respect to large initiatives like One HubSpot and trying freemium go-to-markets.
Get inputs and thoughts all the way down to the IC level in helping set some direction, guardrails, and the right organizational structures and managers in place before sailing the ships on these huge decisions.
Departments don't talk to each other, and that has to change. We'll skin less knees in the process.
Very quick and straightforward interviewing process. It started with a phone call to chat about the company and the position, then an online 1-hour coding test, and finally half a day in-house. The online test included two questions: one very easy a
The interview process consists of three parts: 1. **Industry-level coding assessment:** This round had four different levels, and you could only move to the next level after clearing the current one. 2. **Behavioral round:** This round featured b
Spoke with the hiring manager over the phone for a technical screen. Asked basic computer science questions (data structures, algorithms, etc.) and a brainteaser. Was brought in for a face-to-face with members of the engineering team to spec out a
Very quick and straightforward interviewing process. It started with a phone call to chat about the company and the position, then an online 1-hour coding test, and finally half a day in-house. The online test included two questions: one very easy a
The interview process consists of three parts: 1. **Industry-level coding assessment:** This round had four different levels, and you could only move to the next level after clearing the current one. 2. **Behavioral round:** This round featured b
Spoke with the hiring manager over the phone for a technical screen. Asked basic computer science questions (data structures, algorithms, etc.) and a brainteaser. Was brought in for a face-to-face with members of the engineering team to spec out a