Chaotic growth with some significant inexperience in specific leadership
Pros
- Really amazing team. I loved working with my peers, and the folks that get hired tend to be some of the smartest folks I've met. - Making a difference for users. Bubble users are building some really cool things, for some really cool reasons. The Success team gets to interact with those users closely, on a daily basis, and it's really fun to watch them grow and evolve.
Cons
TLDR: Bubble is in a growth phase. As with any startup, there are friction points, and there are benefits. Bubble's main problem is a classic -- people were promoted to a job they're not necessarily to handle, and have to now manage with questionable guidance. Workload is intense, even for a startup. - Leadership was an issue on the Success team while I worked there, and the structure hasn't changed. The team is left mostly to its own devices by the co-founders, which means there's little to no oversight in the day-to-day functionality. Meetings with team management tended to be unnecessarily stressful, and would periodically consist of being berated by management because someone had been working on a project with minimal guidance and had failed to read minds. Favoritism tends to be shown to male coworkers when it comes to project work, technological challenges, and promotional opportunities. This has been discussed with HR, which lead to a temporary improvement and then a rapid backslide. - Onboarding is chaotic at best. This was something that the team has been pushing to improve for a long time, but has been largely disregarded by management. Complexity of product is not an excuse for poor planning. - Creating procedures and documentation is generally an uphill battle. Somehow, being "entrepreneurial" -- whatever that means -- is more important than making sure the team knows what they should be doing and what being successful looks like on the team. - Workload is intense. Since support is offered to all users, and a number of features and aspects don't have user-facing documentation, be prepared to face a very high ticket volume. - No real career growth opportunities on the team. There's no structure for acknowledging individual contribution, very little opportunity to switch teams (since you're generally needed to cover volume, and can't be spared off of the box), and just the very beginnings of a promotion structure. - Compensation for the team -- while I was part of it -- was much lower than comparable jobs. The real comparison point for the job that you will be asked to do should be a support engineer; instead, be prepared to get paid like a standard Support Associate, but be expected to learn much more complex software and keep in mind the aforementioned ticket volume.